RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

RFC 2026, "The Internet Standards Process -- Revision 3", October 1996

Note: This RFC has been updated by RFC 3667, RFC 3668, RFC 3932, RFC 3978, RFC 3979, RFC 5378, RFC 5657, RFC 5742, RFC 6410, RFC 7100, RFC 7127, RFC 7475, RFC 8179, RFC 8789, RFC 9282

Source of RFC: poised95 (gen)
See Also: RFC 2026 w/ inline errata

Errata ID: 524
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: Bob Harvey
Date Reported: 2002-12-30

Section 2.1 says:

   Some RFCs standardize the results of community deliberations about
   statements of principle or conclusions about what is the best way to
   perform some operations or IETF process function.  These RFCs form
   the specification has been adopted as a BCP, it is given the
   additional label "BCPxxx", but it keeps its RFC number and its place
   in the RFC series. (see section 5)

It should say:

   Some RFCs standardize the results of community deliberations about
   statements of principle or conclusions about what is the best way to
   to perform some operations or IETF process function.  These RFCs form
   the 'BCP' (Best Current Practice) subseries of the RFC series.  When 
   a specification has been adopted as a BCP, it is given the 
   additional label "BCPxxx", but it keeps its RFC number and its place
   in the RFC series. (see section 5)

Notes:

The following words are missing:

'BCP' (Best Current Practice) subseries of the RFC Series. When a

Report New Errata



Advanced Search