[rfc-i] Updating one paragraph of RFC 2026 to reflect current practice

Paul Hoffman paul.hoffman at vpnc.org
Thu May 28 19:19:03 PDT 2015


This is short and to the point. If the community agrees, we can probably get this done easily.

--Paul Hoffman

> Begin forwarded message:
> 
> From: internet-drafts at ietf.org
> Subject: New Version Notification for draft-hoffman-id-references-00.txt
> Date: May 28, 2015 at 7:15:50 PM PDT
> To: "Paul E. Hoffman" <paul.hoffman at vpnc.org>, "Paul Hoffman" <paul.hoffman at vpnc.org>
> 
> 
> A new version of I-D, draft-hoffman-id-references-00.txt
> has been successfully submitted by Paul Hoffman and posted to the
> IETF repository.
> 
> Name:		draft-hoffman-id-references
> Revision:	00
> Title:		Referencing Internet-Drafts in RFCs
> Document date:	2015-05-28
> Group:		Individual Submission
> Pages:		4
> URL:            https://www.ietf.org/internet-drafts/draft-hoffman-id-references-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-hoffman-id-references/
> Htmlized:       https://tools.ietf.org/html/draft-hoffman-id-references-00
> 
> 
> Abstract:
>   RFC 2026 places restrictions on how Internet-Drafts can be referred
>   to in RFCs.  Over time, the way that the IETF community uses
>   sometimes make RFCs inaccurate (because many drafts that are referred
>   to are not actually "works in progress", and also make references to
>   Internet-Drafts nearly useless to RFC readers.  This document updates
>   the one part of RFC 2026, and the one part of RFC 7322, that covers
>   referencing Internet-Drafts.



More information about the rfc-interest mailing list