Brian E Carpenter wrote:

On 2011-06-07 11:57, Fred Baker wrote:
On Jun 6, 2011, at 4:38 PM, Brian E Carpenter wrote:

[RFC3056]  Carpenter, B. and K. Moore, "Connection of IPv6 Domains
           via IPv4 Clouds", RFC 3056, February 2001.

[RFC3068]  Huitema, C., "An Anycast Prefix for 6to4 Relay Routers",
           RFC 3068, June 2001.
I believe these 2 references need to be Normative, as they are required to 
understand this document.
True, but this is an informational document, so why would any references be 
normative?
This is something we spoke about in the working group, and you answered me the 
same way. I think he's not saying (and I was not saying then) that the 
references are normative for the Internet. They're saying that, unlike an 
informative reference (which may give you a deeper understanding but for most 
of the document are optional reading), you can't understand this document if 
you don't understand those two.

Correct, but (process weanie hat on) I don't see anything in the discussion of 
rules
for references in RFC 2026 that requires any such consideration in 
non-standards track
documents. I don't want to change this unless directed by the IESG.
This is not covered by RFC 2026, it is covered by the IESG statement on Normative/Informative references <http://www.ietf.org/iesg/statement/normative-informative.html>, which reads:

Within an RFC, references to other documents fall into two general categories: "normative" and "informative". Normative references specify documents that must be read to understand or implement the technology in the new RFC, or whose technology must be present for the technology in the new RFC to work. An informative reference is not normative; rather, it only provides additional information. For example, an informative reference might provide background or historical information. Informative references are not required to implement the technology in the RFC.

[...]

Note 3: The normative/informative distinction is relevant in any document that amounts to a technical specification, even if its intended status is Experimental or Informational.

_______________________________________________
Gen-art mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/gen-art

Reply via email to