Re: Node requirements: draft-ietf-6man-node-req-bis-03.txt

[Brian E Carpenter <brian.e.carpenter at gmail.com>]

>  - proper status of this document (info vs. BCP) and whether this
>    document can update any existing RFC

There's a standards-track beast defined in section 3.2 of RFC2026 as an
"Applicability Statement":

"  An Applicability Statement specifies how, and under what
   circumstances, one or more TSs [technical specifications] may be applied to support a particular
   Internet capability.
   ...
   An AS also specifies the circumstances in which the use
   of a particular TS is required, recommended, or elective..."

I think we can choose, if we want, to make the present document
an "Applicability Statement" Proposed Standard or BCP that describes
the functionality of a full-spec IPv6 node, and therefore elevates
MAY to SHOULD or MUST if we want to.

Personally, I think that's a good idea, rather than issuing an informational
document that leaves wiggle room on basics such as ND.

    Brian