RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 2 records.

Status: Verified (1)

RFC 1818, "Best Current Practices", August 1995

Source of RFC: Legacy
Area Assignment: gen

Errata ID: 6923
Status: Verified
Type: Editorial
Publication Format(s) : TEXT

Reported By: Robin Geuze
Date Reported: 2022-04-05
Verifier Name: RFC Editor
Date Verified: 2022-04-05

Section Discussion says:

This document creates a new subseries of RFCs, entitled Best Current Practices BCPs).

It should say:

This document creates a new subseries of RFCs, entitled Best Current Practices (BCPs).

Notes:

The opening parentheses was clearly forgotten by accident.

Status: Reported (1)

RFC 1818, "Best Current Practices", August 1995

Source of RFC: Legacy
Area Assignment: gen

Errata ID: 3755
Status: Reported
Type: Editorial
Publication Format(s) : TEXT

Reported By: Dale Worley
Date Reported: 2013-10-16

Section header says:

[Existing header does not contain "Updates".]

It should say:

Updates: 1796

Notes:

RFC 1796 defines the "status" datum of RFCs. The "category" datum is similar, except that "Draft Standard", "Proposed Standard", and "Internet Standard" statuses are merged in the "Standards Track" category.

RFC 1818 introduces the "Best Current Practice" status/category, but its metadata does not state that it updates RFC 1796 and consequently RFC 1796's metadata does not state that it is updated by RFC 1818.

This lack of pointers shows up in rfc-index.txt, making it difficult to track down the current list of categories/statuses.

Report New Errata



Advanced Search