RFC 6410 errata

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



At least one person was confused by some of the text in RFC 6410.  The authors of the document all agree that the proposed errata provides improved text.  If no one raises concerns with this text in the next few weeks, then this RFC errata will change state from "reported" to "approved."

Russ


>>> The following errata report has been submitted for RFC6410,
>>> "Reducing the Standards Track to Two Maturity Levels".
>>> 
>>> --------------------------------------
>>> You may review the report below and at:
>>> http://www.rfc-editor.org/errata_search.php?rfc=6410&eid=3095
>>> 
>>> --------------------------------------
>>> Type: Editorial
>>> Reported by: Russ Housley <housley@xxxxxxxxxxxx>
>>> 
>>> Section: 2.2
>>> 
>>> Original Text
>>> -------------
>>> After review and consideration of significant errata, the IESG will
>>> perform an IETF-wide Last Call of at least four weeks on the
>>> requested reclassification.  If there is consensus for
>>> reclassification, the RFC will be reclassified without publication of
>>> a new RFC.
>>> 
>>> 
>>> Corrected Text
>>> --------------
>>> After review and consideration of significant errata, the IESG will
>>> perform an IETF-wide Last Call of at least four weeks on the
>>> requested reclassification.  If there is consensus for
>>> reclassification, the RFC will be reclassified with or without
>>> publication of a new RFC.
>>> 
>>> Notes
>>> -----
>>> Some people seem to have interpreted this text in a more restrictive manner than intended by the authors.  Advancement from Proposed Standard to Internet Standard does not require the publication an new RFC.  Reclassification of an existing RFC is allowed, but reclassification in conjunction with publication of a new RFC is also allowed.
>>> 
>>> Instructions:
>>> -------------
>>> This errata is currently posted as "Reported". If necessary, please
>>> use "Reply All" to discuss whether it should be verified or
>>> rejected. When a decision is reached, the verifying party (IESG)
>>> can log in to change the status and edit the report, if necessary. 
>>> 
>>> --------------------------------------
>>> RFC6410 (draft-housley-two-maturity-levels-09)
>>> --------------------------------------
>>> Title               : Reducing the Standards Track to Two Maturity Levels
>>> Publication Date    : October 2011
>>> Author(s)           : R. Housley, D. Crocker, E. Burger
>>> Category            : BEST CURRENT PRACTICE
>>> Source              : IETF - NON WORKING GROUP
>>> Area                : N/A
>>> Stream              : IETF
>>> Verifying Party     : IESG
>>> 
> 




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]