Re: IANA Considerations [Re: New ID-Checklist to replace ID-nits (fwd)]

[Paul Hoffman / VPNC <paul.hoffman at vpnc.org>]

At 8:15 AM -0700 6/4/04, David Meyer wrote:
> .LP
> .MH 1 "IANA Considerations"
> .LP
> .in 3
>
> This document creates no new requirements on IANA namespaces [RFC2434].
>
> ...
>
> .LP
> .MH 2 "Informative References"
> .LP
> .in 3
>
> .nf
>
> ...
>
> [RFC2434]       Narten, T., and H. Alvestrand, "Guidelines for
>                 Writing an IANA Considerations Section in RFCs",
>                 BCP 26, RFC 2434, October 1998.
>
> ...
> .fi

We don't need the gratuitous reference added to every document. Just 
saying "This document creates no new requirements on IANA namespaces" 
or even "This document has no impact on any IANA namespace" is 
sufficient to get people who read the earlier drafts to say "yup" or 
"wait, what about that TBD in section 3.4?".

--Paul Hoffman, Director
--VPN Consortium