[rfc-i] Proposed change to RFC references

Tony Hansen tony at att.com
Tue Aug 18 14:13:54 PDT 2015


I support this change.

    Tony Hansen

On 8/17/15 3:01 PM, Heather Flanagan (RFC Series Editor) wrote:
>
> Hello all,
>
> The RFC Editor supports the goal of a more secure and trusted
> Internet. In support of that ideal, the RFC Editor is proposing to
> change how we reference RFCs to use an HTTPS URI. This will not impact
> existing, published RFCs. All pages will continue to be available over
> HTTP as well.
>
> As an example of the proposed change, a reference would change as follow
> s:
>
> OLD
>    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
>               Requirement Levels", BCP 14, RFC 2119, March 1997,
>               <http://www.rfc-editor.org/info/rfc2119>.
>
> NEW
>
>    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
>               Requirement Levels", BCP 14, RFC 2119, March 1997,
>               <https://www.rfc-editor.org/info/rfc2119>.
>
> Please direct any questions or discussion to the rfc-interest mailing
> list <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: OpenPGP digital signature
URL: <http://www.rfc-editor.org/pipermail/rfc-interest/attachments/20150818/47223682/attachment-0001.asc>


More information about the rfc-interest mailing list