An IETF URN Sub-namespace for Registered Protocol Parameters (RFC3553)
Original Publication Date: 2003-Jun-01
Included in the Prior Art Database: 2003-Jun-27
Internet Society Requests For Comment (RFCs)
M. Mealling: AUTHOR [+4]
AbstractThis 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.
Network Working Group M. Mealling
Request for Comments: 3553 VeriSign
BCP: 73 L. Masinter
Category: Best Current Practice Adobe Systems
Nine by Nine
An IETF URN Sub-namespace for Registered Protocol Parameters
Status of this Memo
This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
Copyright (C) The Internet Society (2003). All Rights Reserved.
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
From time to time IETF standards require the registration of various
protocol elements in well known central repository. The Internet
Assigned Numbers Authority maintains this central repository and
takes direction from the IETF on what, how and when to add items to
it. The IANA maintains lists of items such as all assigned port
numbers, MIME media types, enterprise numbers, etc.
Over time there has developed a need to be able to reference these
elements as URIs in various schema. In the past this was done in a
very ad hoc way that easily led to interoperability problems. This
document creates a new sub-delegation below the "ietf" URN
namespace  called 'params' which acts as a standardized mechanism
for naming the items registered for IETF standards. Any assignments
below that are specified in an RFC according to the IETF consensus
process and which include the template found in Section 4.
Mealling, et. al. Best Current Practice [Page 1]
RFC 3553 IANA URN Namespace June 2003
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL"...