errata logo graphic

Found 2 records.

Status: Verified (1)

RFC3406, "Uniform Resource Names (URN) Namespace Definition Mechanisms", October 2002

Source of RFC: urn (app)

Errata ID: 1444

Status: Verified
Type: Editorial

Reported By: Frank Ellermann
Date Reported: 2008-06-14
Verifier Name: Alexey Melnikov
Date Verified: 2010-04-02

Section 4.3 says:

   Registrations may be revised by updating the RFC through standard
   IETF RFC update processes (see [RFC2606] for a discussion of IETF
   process).

It should say:

   Registrations may be revised by updating the RFC through standard
   IETF RFC update processes (see [RFC2026] for a discussion of IETF
   process).

Notes:

The references (section 7) list RFC 2026, not RFC 2606, as expected.


Status: Rejected (1)

RFC3406, "Uniform Resource Names (URN) Namespace Definition Mechanisms", October 2002

Source of RFC: urn (app)

Errata ID: 2915

Status: Rejected
Type: Editorial

Reported By: Mykyta Yevstifeyev
Date Reported: 2011-08-04
Rejected by: Pete Resnick
Date Rejected: 2011-08-04

Section Header says:

BCP: 66

It should say:

BCP: 33

Notes:

RFC 3406 obsoletes RFC 2611, which was BCP 33. Correspondingly, RFC 3406 should be BCP 33 as well. (See also http://www.rfc-editor.org/errata_search.php?rfc=4395; this is the same situation.)

If this erratum report is approved, BCP number 66 should be retired, as BCP 115 (see link above).
--VERIFIER NOTES--
This is likely correct. However, this is because the "RFC has not been processed in accordance with the rules governing the proposed change to the RFC metadata." (See IESG statement on changes to metadata in errata.) Making the suggested change would potentially invalidate references to BCP 66. The IESG and RFC Editor should decide best course of action.


Report New Errata