draft-ietf-urnbis-rfc3406bis-urn-ns-reg-08.txt   draft-ietf-urnbis-rfc3406bis-urn-ns-reg-09.txt 
URNBIS P. Saint-Andre URNBIS P. Saint-Andre
Internet-Draft January 24, 2014 Internet-Draft &yet
Obsoletes: 3406 (if approved) Obsoletes: 3406 (if approved) February 12, 2014
Intended status: BCP Intended status: Best Current Practice
Expires: July 28, 2014 Expires: August 16, 2014
Uniform Resource Name (URN) Namespace Definition Mechanisms Uniform Resource Name (URN) Namespace Definition Mechanisms
draft-ietf-urnbis-rfc3406bis-urn-ns-reg-08 draft-ietf-urnbis-rfc3406bis-urn-ns-reg-09
Abstract Abstract
This document supplements the Uniform Resource Name (URN) syntax This document supplements the Uniform Resource Name (URN) syntax
specification by defining the concept of a URN namespace, as well as specification by defining the concept of a URN namespace, as well as
mechanisms for defining and registering such namespaces. This mechanisms for defining and registering such namespaces. This
document obsoletes RFC 3406. document obsoletes RFC 3406.
Status of this Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 28, 2014. This Internet-Draft will expire on August 16, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. What is a URN Namespace? . . . . . . . . . . . . . . . . . . . 4 3. What is a URN Namespace? . . . . . . . . . . . . . . . . . . 3
4. URN Namespace Types . . . . . . . . . . . . . . . . . . . . . 5 4. URN Namespace Types . . . . . . . . . . . . . . . . . . . . . 5
4.1. Formal Namespaces . . . . . . . . . . . . . . . . . . . . 5 4.1. Formal Namespaces . . . . . . . . . . . . . . . . . . . . 5
4.2. Informal Namespaces . . . . . . . . . . . . . . . . . . . 6 4.2. Informal Namespaces . . . . . . . . . . . . . . . . . . . 6
5. Defining a URN Namespace . . . . . . . . . . . . . . . . . . . 6 5. Defining a URN Namespace . . . . . . . . . . . . . . . . . . 7
5.1. Purpose . . . . . . . . . . . . . . . . . . . . . . . . . 7 5.1. Purpose . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.2. Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 7 5.2. Syntax . . . . . . . . . . . . . . . . . . . . . . . . . 8
5.3. Assignment . . . . . . . . . . . . . . . . . . . . . . . . 8 5.3. Assignment . . . . . . . . . . . . . . . . . . . . . . . 8
5.4. Security . . . . . . . . . . . . . . . . . . . . . . . . . 9 5.4. Security and Privacy . . . . . . . . . . . . . . . . . . 9
5.5. Resolution . . . . . . . . . . . . . . . . . . . . . . . . 9 5.5. Resolution . . . . . . . . . . . . . . . . . . . . . . . 9
6. Registration Template . . . . . . . . . . . . . . . . . . . . 9 6. Registration Template . . . . . . . . . . . . . . . . . . . . 10
6.1. Namespace ID . . . . . . . . . . . . . . . . . . . . . . . 9 6.1. Namespace ID . . . . . . . . . . . . . . . . . . . . . . 10
6.2. Version . . . . . . . . . . . . . . . . . . . . . . . . . 10 6.2. Version . . . . . . . . . . . . . . . . . . . . . . . . . 10
6.3. Date . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 6.3. Date . . . . . . . . . . . . . . . . . . . . . . . . . . 10
6.4. Registrant . . . . . . . . . . . . . . . . . . . . . . . . 10 6.4. Registrant . . . . . . . . . . . . . . . . . . . . . . . 10
6.5. Purpose . . . . . . . . . . . . . . . . . . . . . . . . . 10 6.5. Purpose . . . . . . . . . . . . . . . . . . . . . . . . . 10
6.6. Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . 10 6.6. Syntax . . . . . . . . . . . . . . . . . . . . . . . . . 10
6.7. Assignment . . . . . . . . . . . . . . . . . . . . . . . . 10 6.7. Assignment . . . . . . . . . . . . . . . . . . . . . . . 10
6.8. Resolution . . . . . . . . . . . . . . . . . . . . . . . . 10 6.8. Resolution . . . . . . . . . . . . . . . . . . . . . . . 10
6.9. Documentation . . . . . . . . . . . . . . . . . . . . . . 10 6.9. Documentation . . . . . . . . . . . . . . . . . . . . . . 11
7. Registering a URN Namespace . . . . . . . . . . . . . . . . . 10 7. Registering a URN Namespace . . . . . . . . . . . . . . . . . 11
7.1. Formal Namespaces . . . . . . . . . . . . . . . . . . . . 10 7.1. Formal Namespaces . . . . . . . . . . . . . . . . . . . . 11
7.2. Informal Namespaces . . . . . . . . . . . . . . . . . . . 11 7.2. Informal Namespaces . . . . . . . . . . . . . . . . . . . 11
8. Guidelines for Designated Experts . . . . . . . . . . . . . . 11 8. Guidelines for Designated Experts . . . . . . . . . . . . . . 12
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
10. Security Considerations . . . . . . . . . . . . . . . . . . . 12 10. Security and Privacy Considerations . . . . . . . . . . . . . 12
11. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 12
11.1. Normative References . . . . . . . . . . . . . . . . . . . 12 11.1. Normative References . . . . . . . . . . . . . . . . . . 12
11.2. Informative References . . . . . . . . . . . . . . . . . . 12 11.2. Informative References . . . . . . . . . . . . . . . . . 13
Appendix A. Changes from RFC 3406 . . . . . . . . . . . . . . . . 13 Appendix A. Changes from RFC 3406 . . . . . . . . . . . . . . . 14
Appendix B. Contributors . . . . . . . . . . . . . . . . . . . . 13 Appendix B. Contributors . . . . . . . . . . . . . . . . . . . . 14
Appendix C. Acknowledgements . . . . . . . . . . . . . . . . . . 13 Appendix C. Acknowledgements . . . . . . . . . . . . . . . . . . 14
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 14 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
A Uniform Resource Name (URN) [I-D.ietf-urnbis-rfc2141bis-urn] is a A Uniform Resource Name (URN) [I-D.ietf-urnbis-rfc2141bis-urn] is a
Uniform Resource Identifier (URI) [RFC3986] that is intended to serve Uniform Resource Identifier (URI) [RFC3986] that is intended to serve
as a persistent, location-independent resource identifier. This as a persistent, location-independent resource identifier. This
document supplements the Uniform Resource Name (URN) syntax document supplements the Uniform Resource Name (URN) syntax
specification [I-D.ietf-urnbis-rfc2141bis-urn] by defining: specification [I-D.ietf-urnbis-rfc2141bis-urn] by defining:
1. The concept of a URN namespace. 1. The concept of a URN namespace.
skipping to change at page 5, line 24 skipping to change at page 5, line 16
There are two types of URN namespace: formal and informal. These are There are two types of URN namespace: formal and informal. These are
distinguished by the expected level of service, the information distinguished by the expected level of service, the information
needed to define the namespace, and the procedures for registration. needed to define the namespace, and the procedures for registration.
Because the majority of the namespaces registered so far have been Because the majority of the namespaces registered so far have been
formal, this document concentrates on formal namespaces. formal, this document concentrates on formal namespaces.
Note: [RFC3406] defined a third type of "experimental namespaces", Note: [RFC3406] defined a third type of "experimental namespaces",
denoted by prefixing the namespace identifier with the string "X-". denoted by prefixing the namespace identifier with the string "X-".
Consistent with [RFC6648], this specification removes the Consistent with [RFC6648], this specification removes the
experimental category. experimental category. Because experimental namespaces were never
registered, removing the experimental category has no impact on the
existing registries or future registration procedures.
4.1. Formal Namespaces 4.1. Formal Namespaces
A formal namespace provides benefit to some subset of users on the A formal namespace provides benefit to some subset of users on the
Internet (e.g., it would not make sense for a formal namespace to be Internet (e.g., it would not make sense for a formal namespace to be
used only by a community or network that is not connected to the used only by a community or network that is not connected to the
Internet). For example, it would be inappropriate for a NID to Internet). For example, it would be inappropriate for a NID to
effectively force someone to use a proprietary network or service not effectively force someone to use a proprietary network or service not
open to the general Internet user. The intent is that, while the open to the general Internet user. The intent is that, while the
community of those who might actively use the names assigned within community of those who might actively use the names assigned within
skipping to change at page 6, line 19 skipping to change at page 6, line 12
those names are no longer members or customers of that those names are no longer members or customers of that
organization. With regard to URN resolution [RFC2276], this does organization. With regard to URN resolution [RFC2276], this does
not mean that there needs to be resolution of such names, only not mean that there needs to be resolution of such names, only
that the names will not resolve to false or stale information. that the names will not resolve to false or stale information.
A formal namespace establishes a particular NID, subject to the A formal namespace establishes a particular NID, subject to the
following constraints (above and beyond the syntax rules specified in following constraints (above and beyond the syntax rules specified in
[I-D.ietf-urnbis-rfc2141bis-urn]): [I-D.ietf-urnbis-rfc2141bis-urn]):
1. It MUST NOT be an already-registered NID. 1. It MUST NOT be an already-registered NID.
2. It MUST NOT start with "urn-" (which is reserved for informal 2. It MUST NOT start with "urn-" (which is reserved for informal
namespaces). namespaces).
3. It MUST be more than two characters long. 3. It MUST be more than two characters long.
4. It MUST NOT start with "XY-", where "XY" is any combination of
4. It MUST NOT start with "aa-", where "aa" is any combination of
two ASCII letters. two ASCII letters.
5. It MUST NOT start with the string "xn--", which is reserved for
potential representation of DNS A-labels in the future [RFC5890].
All two-letter combinations, and all two-letter combinations followed All two-letter combinations, and all two-letter combinations followed
by "-" and any sequence of valid NID characters, are reserved for by "-" and any sequence of valid NID characters, are reserved for
potential use as countrycode-based NIDs for eventual national potential use as countrycode-based NIDs for eventual national
registrations of URN namespaces. The definition and scoping of rules registrations of URN namespaces. The definition and scoping of rules
for allocation of responsibility for such countrycode-based for allocation of responsibility for such countrycode-based
namespaces is beyond the scope of this document. namespaces is beyond the scope of this document.
4.2. Informal Namespaces 4.2. Informal Namespaces
Informal namespaces are full-fledged URN namespaces, with all the Informal namespaces are full-fledged URN namespaces, with all the
associated rights and responsibilities. Informal namespaces differ associated rights and responsibilities. Informal namespaces differ
from formal namespaces in the process for assigning a NID: for an from formal namespaces in the process for assigning a NID: for an
informal namespace, IANA will assign an NID consisting of the string informal namespace, the registrant does not designate the NID;
'urn-' followed by one or more digits (e.g., "urn-7"). Thus the instead, IANA assigns a NID consisting of the string 'urn-' followed
syntax of an informal namespace is: by one or more digits (e.g., "urn-7") where the digits consist of the
next available number in the sequence of positive integers assigned
to informal namespaces. Thus the syntax of an informal namespace is:
"urn-" <number> "urn-" <number>
The only restrictions on <number> are that it (1) consist strictly of The only restrictions on <number> are that it (1) consist strictly of
ASCII digits and (2) not cause the NID to exceed the length ASCII digits and (2) not cause the NID to exceed the length
limitations defined in the URN syntax specification limitations defined in the URN syntax specification
[I-D.ietf-urnbis-rfc2141bis-urn]. [I-D.ietf-urnbis-rfc2141bis-urn].
5. Defining a URN Namespace 5. Defining a URN Namespace
skipping to change at page 9, line 13 skipping to change at page 9, line 22
identifers from existing assignment authorities. identifers from existing assignment authorities.
2. Methods for ensuring that URNs within the namespace are unique. 2. Methods for ensuring that URNs within the namespace are unique.
For example, identifiers might be assigned sequentially or in For example, identifiers might be assigned sequentially or in
accordance with some well-defined process by a single authority, accordance with some well-defined process by a single authority,
assignment might be partitioned among delegated authorities that assignment might be partitioned among delegated authorities that
are individually responsible for respecting uniqueness rules, or are individually responsible for respecting uniqueness rules, or
URNs might be created independently following an algorithm that URNs might be created independently following an algorithm that
itself guarantees uniqueness. itself guarantees uniqueness.
5.4. Security 5.4. Security and Privacy
The "Security" section of the template describes any potential The "Security" section of the template describes any potential issues
security-related issues with regard to assignment, use, and related to security and privacy with regard to assignment, use, and
resolution of identifiers within the namespace. Examples of such resolution of identifiers within the namespace. Examples of such
issues include the consequences of producing false negatives and issues include the consequences of producing false negatives and
false positives during comparison for equivalence (see also false positives during comparison for equivalence (see also
[RFC6943]), leakage of private information when identifiers are [RFC6943]), leakage of private information when identifiers are
communicated on the public Internet, the potential for directory communicated on the public Internet, the potential for directory
harvesting, and various issues discussed in the guidelines for harvesting, and various issues discussed in the guidelines for
security considerations in RFCs [RFC3552]. security considerations in RFCs [RFC3552] and the privacy
considerations for Internet protocols [RFC6973].
5.5. Resolution 5.5. Resolution
The "Resolution" section specifies the rules for resolution of URNs The "Resolution" section specifies the rules for resolution of URNs
assigned within the namespace. If such URNs are intended to be assigned within the namespace. If such URNs are intended to be
resolvable, the namespace needs to be registered in a Resolution resolvable, the namespace needs to be registered in a Resolution
Discovery System (RDS, see [RFC2276]) such as DDDS. Resolution then Discovery System (RDS, see [RFC2276]) such as DDDS. Resolution then
proceeds according to standard URI resolution processes, as well as proceeds according to standard URI resolution processes, as well as
the mechanisms of the RDS. This section ought to lists the the mechanisms of the RDS. This section ought to lists the
requirements for becoming a recognized resolver of URNs in the requirements for becoming a recognized resolver of URNs in the
skipping to change at page 10, line 42 skipping to change at page 11, line 7
6.7. Assignment 6.7. Assignment
Described under Section 5.3 of this document. Described under Section 5.3 of this document.
6.8. Resolution 6.8. Resolution
Described under Section 5.5 of this document. Described under Section 5.5 of this document.
6.9. Documentation 6.9. Documentation
A pointer to an Internet-Draft, RFC, non-IETF specification, or other A pointer to an RFC, a specification published by another standards
published document that provides further information about the development organization, or another stable document that provides
namespace. further information about the namespace.
7. Registering a URN Namespace 7. Registering a URN Namespace
7.1. Formal Namespaces 7.1. Formal Namespaces
The registration policy for formal namespaces is Expert Review as The registration policy for formal namespaces is Expert Review as
defined in the "IANA Considerations" document [RFC5226]. The key defined in the "IANA Considerations" document [RFC5226]. The key
steps for registration of a formal namespace are: steps for registration of a formal namespace are:
1. Fill out the namespace registration template (see Section 6). 1. Fill out the namespace registration template (see Section 6).
skipping to change at page 11, line 9 skipping to change at page 11, line 22
7.1. Formal Namespaces 7.1. Formal Namespaces
The registration policy for formal namespaces is Expert Review as The registration policy for formal namespaces is Expert Review as
defined in the "IANA Considerations" document [RFC5226]. The key defined in the "IANA Considerations" document [RFC5226]. The key
steps for registration of a formal namespace are: steps for registration of a formal namespace are:
1. Fill out the namespace registration template (see Section 6). 1. Fill out the namespace registration template (see Section 6).
This can be done as part of an Internet-Draft or a specification This can be done as part of an Internet-Draft or a specification
in another series, although that is not necessary. in another series, although that is not necessary.
2. Send the completed template to the urn-nid@ietf.org discussion 2. Send the completed template to the urn-nid@ietf.org discussion
list for technical review. list for review.
3. If necessary to address comments received, repeat steps 1 and 2. 3. If necessary to address comments received, repeat steps 1 and 2.
4. If the designated experts approve the request, the IANA will 4. If the designated experts approve the request, the IANA will
register the requested NID. register the requested NID.
A formal namespace registration can be revised by updating the A formal namespace registration can be revised by updating the
registration template, following the same steps outlined above for registration template, following the same steps outlined above for
new registrations. new registrations. A revised registration should making special note
of any relevant changes in the underlying technologies or namespace
management processes.
7.2. Informal Namespaces 7.2. Informal Namespaces
The registration policy for informal namespaces is First Come First The registration policy for informal namespaces is First Come First
Served [RFC5226]. The key steps for registration of an informal Served [RFC5226]. The key steps for registration of an informal
namespace are: namespace are:
1. Write a completed namespace definition template (see Section 6). 1. Write a completed namespace definition template (see Section 6).
2. Send it to the urn-nid@ietf.org discussion list for feedback. 2. Send it to the urn-nid@ietf.org discussion list for feedback.
3. Once the review period has expired, send the final template to 3. Once the review period has expired, send the final template to
IANA (via the iana@iana.org email address). IANA (via the iana@iana.org email address).
An informal namespace registration can be revised by updating the An informal namespace registration can be revised by updating the
registration template, following the same steps outlined above for registration template, following the same steps outlined above for
new registrations. new registrations.
8. Guidelines for Designated Experts 8. Guidelines for Designated Experts
Experience to date with NID registration requests has shown that Experience to date with NID registration requests has shown that
skipping to change at page 11, line 42 skipping to change at page 12, line 13
new registrations. new registrations.
8. Guidelines for Designated Experts 8. Guidelines for Designated Experts
Experience to date with NID registration requests has shown that Experience to date with NID registration requests has shown that
registrants sometimes do not initially understand some of the registrants sometimes do not initially understand some of the
subtleties of URN namespaces, and that defining the namespace in the subtleties of URN namespaces, and that defining the namespace in the
form of a specification enables the registrants to clearly formulate form of a specification enables the registrants to clearly formulate
their "contract" with the intended user community. Therefore, their "contract" with the intended user community. Therefore,
although the registration policy for formal namespaces is Expert although the registration policy for formal namespaces is Expert
Review and a specification is not required, the designated experts Review and a stable specification is not strictly required, the
for NID registration requests are encouraged to prefer that a designated experts for NID registration requests ought to encourage
specification exist documenting the namespace definition. applicants to provide a stable specification documenting the
namespace definition.
Naming can be difficult and contentious; the designated experts and
applicants are strongly encouraged to work together in a spirit of
good faith and mutual understanding to achieve rough consensus on
progressing registrations through the process. They are also
encouraged to bring additional expertise into the discussion if that
would be helpful in adding perspective or otherwise resolving issues.
9. IANA Considerations 9. IANA Considerations
This document outlines the processes for registering URN namespaces, This document outlines the processes for registering URN namespaces,
and has implications for the IANA in terms of registries to be and has implications for the IANA in terms of registries to be
maintained. In all cases, the IANA ought to assign the appropriate maintained. In all cases, the IANA ought to assign the appropriate
NID (formal or informal) once the procedures outlined in this NID (formal or informal) once the procedures outlined in this
document have been completed. document have been completed.
10. Security Considerations 10. Security and Privacy Considerations
This document largely focuses on providing mechanisms for the This document largely focuses on providing mechanisms for the
declaration of public information. Nominally, these declarations declaration of public information. Nominally, these declarations
will be of relatively low security profile, however there is always will be of relatively low security profile, however there is always
the danger of "spoofing" and providing misinformation. Information the danger of "spoofing" and providing misinformation. Information
in these declarations ought to be taken as advisory. in these declarations ought to be taken as advisory.
The definition of a URN namespace needs to account for potential The definition of a URN namespace needs to account for potential
security issues related to assignment, use, and resolution of security and privacy issues related to assignment, use, and
identifiers within the namespace. resolution of identifiers within the namespace.
11. References 11. References
11.1. Normative References 11.1. Normative References
[I-D.ietf-urnbis-rfc2141bis-urn] [I-D.ietf-urnbis-rfc2141bis-urn]
Saint-Andre, P., Ed., "Uniform Resource Name (URN) Saint-Andre, P., Ed., "Uniform Resource Name (URN)
Syntax", draft-ietf-urnbis-rfc2141bis-urn-07 (work in Syntax", draft-ietf-urnbis-rfc2141bis-urn-07 (work in
progress), January 2014. progress), January 2014.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, Resource Identifier (URI): Generic Syntax", STD 66, RFC
RFC 3986, January 2005. 3986, January 2005.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
11.2. Informative References 11.2. Informative References
[RFC2276] Sollins, K., "Architectural Principles of Uniform Resource [RFC2276] Sollins, K., "Architectural Principles of Uniform Resource
Name Resolution", RFC 2276, January 1998. Name Resolution", RFC 2276, January 1998.
[RFC2611] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, [RFC2611] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom,
"URN Namespace Definition Mechanisms", BCP 33, RFC 2611, "URN Namespace Definition Mechanisms", BCP 33, RFC 2611,
June 1999. June 1999.
[RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom,
"Uniform Resource Names (URN) Namespace Definition "Uniform Resource Names (URN) Namespace Definition
Mechanisms", BCP 66, RFC 3406, October 2002. Mechanisms", BCP 66, RFC 3406, October 2002.
[RFC3552] Rescorla, E. and B. Korver, "Guidelines for Writing RFC [RFC3552] Rescorla, E. and B. Korver, "Guidelines for Writing RFC
Text on Security Considerations", BCP 72, RFC 3552, Text on Security Considerations", BCP 72, RFC 3552, July
July 2003. 2003.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008. Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC5890] Klensin, J., "Internationalized Domain Names for
Applications (IDNA): Definitions and Document Framework",
RFC 5890, August 2010.
[RFC6648] Saint-Andre, P., Crocker, D., and M. Nottingham, [RFC6648] Saint-Andre, P., Crocker, D., and M. Nottingham,
"Deprecating the "X-" Prefix and Similar Constructs in "Deprecating the "X-" Prefix and Similar Constructs in
Application Protocols", BCP 178, RFC 6648, June 2012. Application Protocols", BCP 178, RFC 6648, June 2012.
[RFC6943] Thaler, D., "Issues in Identifier Comparison for Security [RFC6943] Thaler, D., "Issues in Identifier Comparison for Security
Purposes", RFC 6943, May 2013. Purposes", RFC 6943, May 2013.
[RFC6963] Saint-Andre, P., "A Uniform Resource Name (URN) Namespace [RFC6963] Saint-Andre, P., "A Uniform Resource Name (URN) Namespace
for Examples", BCP 183, RFC 6963, May 2013. for Examples", BCP 183, RFC 6963, May 2013.
[RFC6973] Cooper, A., Tschofenig, H., Aboba, B., Peterson, J.,
Morris, J., Hansen, M., and R. Smith, "Privacy
Considerations for Internet Protocols", RFC 6973, July
2013.
Appendix A. Changes from RFC 3406 Appendix A. Changes from RFC 3406
This document makes the following substantive changes from [RFC3406]: This document makes the following substantive changes from [RFC3406]:
1. Relaxes the registration policy for formal namespaces from "IETF 1. Relaxes the registration policy for formal namespaces from "IETF
Review" to "Expert Review" [RFC5226]. Review" to "Expert Review" [RFC5226].
2. Removes the category of experimental namespaces, consistent with 2. Removes the category of experimental namespaces, consistent with
[RFC6648]. [RFC6648].
3. Simplifies the registration template. 3. Simplifies the registration template.
In addition, some of the text has been updated to be consistent with In addition, some of the text has been updated to be consistent with
the definition of Uniform Resource Identifiers (URIs) [RFC3986] and the definition of Uniform Resource Identifiers (URIs) [RFC3986] and
the processes for registering information with the IANA [RFC5226], as the processes for registering information with the IANA [RFC5226], as
well as more modern guidance with regard to security issues [RFC3552] well as more modern guidance with regard to security issues [RFC3552]
and identifier comparison [RFC6943]. and identifier comparison [RFC6943].
Appendix B. Contributors Appendix B. Contributors
skipping to change at page 14, line 9 skipping to change at page 14, line 42
Faltstrom. Their work is gratefully acknowledged. Faltstrom. Their work is gratefully acknowledged.
Appendix C. Acknowledgements Appendix C. Acknowledgements
Thanks to Marc Blanchet, Juha Hakala, Paul Jones, John Klensin, and Thanks to Marc Blanchet, Juha Hakala, Paul Jones, John Klensin, and
Barry Leiba for their input. Barry Leiba for their input.
Author's Address Author's Address
Peter Saint-Andre Peter Saint-Andre
&yet
Email: ietf@stpeter.im Email: ietf@stpeter.im
 End of changes. 31 change blocks. 
66 lines changed or deleted 104 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/