RFC Errata


Errata Search
 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Verified (1)

RFC 6410, "Reducing the Standards Track to Two Maturity Levels", October 2011

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: gen

Errata ID: 3095
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Russ Housley
Date Reported: 2012-01-23
Verifier Name: Barry Leiba
Date Verified: 2012-05-08

Section 2.2 says: 

   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.

It should say:

   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 of a new RFC. Reclassification of an existing RFC is allowed, but reclassification in conjunction with publication of a new RFC is also allowed.

Status: Reported (1)

RFC 6410, "Reducing the Standards Track to Two Maturity Levels", October 2011

Source of RFC: IETF - NON WORKING GROUP
Area Assignment: gen

Errata ID: 8083
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: John Klensin
Date Reported: 2024-08-17

Throughout the document, when it says: 

Updates: 2026

It should say:

Updates: 2026, 5657

Notes:

RFC 5657 was addressed to the requirement for an implementation report for specifications progressing to Draft Standard. RFC 6410 not only eliminates Draft Standards but quite explicitly eliminates the requirement for implementation reports. It even goes on to say, in Section 3.2, that the advice in RFC 5657 "can be helpful to conduct interoperability testing". In spite of there being no other discussion of 5657 in 6410, that constitutes an update to 5657 that changes its status and the interpretation of every normative statement in it

Cf errata report 8082.

Report New Errata



Advanced Search