On 1/17/14, 3:43 PM, "Michael Behringer (mbehring)" <[email protected]>
wrote:

>RFC2026#section-4.2.2:
>
>    4.2.2  Informational
>      An "Informational" specification is published for the general
>      information of the Internet community, and does not represent an
>      Internet community consensus or recommendation.  The Informational
>      designation is intended to provide for the timely publication of a
>      very broad range of responsible informational documents from many
>      sources, subject only to editorial considerations and to
>verification
>      that there has been adequate coordination with the standards process
>      (see section 4.2.3).
You make a good point, and those familiar with IETF may well interpret it
that way. However, we have plenty of Informational drafts that go through
a WG and IETF LC, are evaluated by the IESG and do represent IETF
consensus, and that is the path this document is currently on.
Additionally, what I’ve found in practice with those who are consumers of
IETF drafts but not active participants and thus not familiar with the
nuances of our document classifications is that to them, an RFC is an RFC.
Therefore, the boilerplate note that accompanies an individual draft (see
5742) provides the necessary disclaimer to make it clear that IETF doesn’t
endorse something, even if it is documented as “this is a thing that
consenting adults may do on their network if they choose” instead of “this
is a thing that you SHOULD do on your network”.

Thanks
Wes


This E-mail and any of its attachments may contain Time Warner Cable 
proprietary information, which is privileged, confidential, or subject to 
copyright belonging to Time Warner Cable. This E-mail is intended solely for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient of this E-mail, you are hereby notified that any 
dissemination, distribution, copying, or action taken in relation to the 
contents of and attachments to this E-mail is strictly prohibited and may be 
unlawful. If you have received this E-mail in error, please notify the sender 
immediately and permanently delete the original and any copy of this E-mail and 
any printout.
_______________________________________________
OPSEC mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsec

Reply via email to