Because would not someone retrieving an RFC want to know it really came from
the IETF, especially when it says
The protocol MUST provide provisions for lawful intercept and
MUST post a notification when traitorous speech is detected.
;-)
And, don’t we need to eat our own dog food?
On Nov 5, 2013, at 8:35 PM, David Morris <dwm(_at_)xpasc(_dot_)com> wrote:
I don't see reason to use https for delivery of public documents such
as RFCs and Internet Drafts. All that would really accomplish is
reduce caching opportunities.
On Tue, 5 Nov 2013, Tim Bray wrote:
Wouldn?t it be a good idea for everything at *.ietf.org to be served by
HTTPS, and only by HTTPS?
smime.p7s
Description: S/MIME cryptographic signature