(Sorry for not responding sooner)
>>>>> On Tue, 9 Mar 2004 20:10:13 -0500 (EST),
>>>>> Suresh Krishnan <[EMAIL PROTECTED]> said:
> Don't if it is concrete or not but Section 4.2.4 of RFC2026 states
> Note: Standards track specifications normally must not depend on
> other standards track specifications which are at a lower maturity
> level or on non standards track specifications other than referenced
> specifications from other standards bodies. (See Section 7.)
> Since PS is lower than DS on the maturity level, a DS spec cannot have a
> normative reference to a PS spec.
Thanks for the pointer. My understanding from this and the I-D Pekka
provided (thanks) is:
- PS is at a lower maturity level than DS is (Sections 4.1.1 and 4.1.2
of RFC2026).
- so, a DS spec must not "depend on" a PS spec (Section 4.2.4 of
RFC2026)
- draft-ymbk-downref-01 clarifies what the dependency means in terms
of the reference category. It says in abstract that:
IETF procedures generally require that a standards track RFC may not
have a normative reference to a document at a lower standards level.
(it seems to me that this draft rather concentrates on exceptions to
this rule than the original rule itself, but I guess it's enough for
now)
The draft use the term "standards level", but it obviously means the
maturity level.
As a conclusion, it should be wise not to have a normative reference
to a PS document from rfc2462bis, even though there may be exceptions.
This means we should not have a normative reference from rfc2462bis to
RFC3315 (PS) or to node requirements document (will be info).
Through the discussions so far, (my understanding of) the consensus is
that it is okay to use the documents as an informative reference
(which document should be used is a separate question).
JINMEI, Tatuya
Communication Platform Lab.
Corporate R&D Center, Toshiba Corp.
[EMAIL PROTECTED]
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[EMAIL PROTECTED]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
