RFC 3553: An IETF URN Sub-namespace for Registered Protocol Parameters
In plain English — editorial summary, not part of the RFC
This document describes a new sub-delegation for the 'ietf' URN namespace for registered protocol items. The 'ietf' URN namespace is defined in RFC 2648 as a root for persistent URIs that refer to IETF- defined resources. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC3553
- Published
- June 2003
- Authors
- M. Mealling; L. Masinter; T. Hardie; G. Klyne
- Status
- BEST CURRENT PRACTICE
- Stream
- Legacy
- Area
- —
- Pages
- 8
- Also known as
- BCP73
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2224NFS URL SchemeCurrent
October 1997
- RFC 1808Relative Uniform Resource LocatorsObsoleted
June 1995
- RFC 3492Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in Applications (IDNA)Updated
March 2003
- RFC 3731Extensible Provisioning Protocol (EPP) Domain Name MappingObsoleted
March 2004
- RFC 3732Extensible Provisioning Protocol (EPP) Host MappingObsoleted
March 2004
- RFC 3733Extensible Provisioning Protocol (EPP) Contact MappingObsoleted
March 2004
- RFC 3739Internet X.509 Public Key Infrastructure: Qualified Certificates ProfileCurrent
March 2004
- RFC 3259A Message Bus for Local CoordinationCurrent
May 2002
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?