FW: BCP0097 RFC 4897 on Handling Normative References to Standards-Track Documents

It might be not so difficult to publish 2616bis as Standard even if
normative
references are Proposed or Draft (including, for example, 2617bis).

        BCP 97        
        RFC 4897

        Title:      Handling Normative References to Standards-Track 
                    Documents 
        Author:     J. Klensin, S. Hartman
        Status:     Best Current Practice
        Date:       June 2007
        Mailbox:    john-ietf@jck.com, 
                    hartmans-ietf@mit.edu
        Pages:      6
        Characters: 13023
        

        I-D Tag:    draft-klensin-norm-ref-04.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4897.txt 

The Internet Engineering Task Force (IETF) and Request for Comments
(RFC) Editor have a long-standing rule that a document at a given
maturity level cannot be published until all of the documents that it
references as normative are at that maturity level or higher.  This
rule has sometimes resulted in very long publication delays for
documents and some claims that it was a major obstruction to
advancing documents in maturity level.  The IETF agreed on a way to
bypass this rule with RFC 3967.  This document describes a simpler
procedure for downward references to Standards-Track and Best Current
Practice (BCP) documents, namely "note and move on".  The procedure
in RFC 3967 still applies for downward references to other classes of
documents.  In both cases, annotations should be added to such
References.  This document specifies an Internet Best Current Practices 
for the Internet Community, and requests discussion and suggestions for
improvements.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  Distribution of this memo is unlimited.

Received on Monday, 18 June 2007 05:06:08 UTC