RFC 8254: Uniform Resource Name (URN) Namespace Registration Transition
In plain English — editorial summary, not part of the RFC
The original registration procedure for formal Uniform Resource Name (URN) namespaces required IETF Consensus. That requirement discouraged some registrations and increased the risk for problems that could occur as a result. The requirements have now been changed by RFC 8141, which adopts a different model, focusing on encouraging registration and publication of information for all appropriate namespaces. This document clarifies the status of relevant older RFCs and confirms and documents advice to IANA about selected existing registrations. This document also obsoletes RFCs 3044 and 3187 and moves them to Historic status. These RFCs describe the ISSN and ISBN namespaces, which are now outdated because the descriptions reside in registration templates.
Document record
- Document ID
- RFC8254
- Published
- October 2017
- Authors
- J. Klensin; J. Hakala
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 9
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 3044 (2001)
- RFC 3187 (2001)
- RFC 8254 (2017)
Read the full history of Uniform Resource Name (URN) Namespace Registration Transition →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8255Multiple Language Content TypeCurrent
October 2017
- RFC 8251Updates to the Opus Audio CodecCurrent
October 2017
- RFC 8259The JavaScript Object Notation (JSON) Data Interchange FormatCurrent
December 2017
- RFC 8262Content-ID Header Field in the Session Initiation Protocol (SIP)Current
October 2017
- RFC 8264PRECIS Framework: Preparation, Enforcement, and Comparison of Internationalized Strings in Application ProtocolsCurrent
October 2017
- RFC 8265Preparation, Enforcement, and Comparison of Internationalized Strings Representing Usernames and PasswordsCurrent
October 2017
- RFC 8266Preparation, Enforcement, and Comparison of Internationalized Strings Representing NicknamesCurrent
October 2017
- RFC 8226Secure Telephone Identity Credentials: CertificatesUpdated
February 2018
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?