| < draft-leiba-urnbis-ietf-namespace-00.txt | draft-leiba-urnbis-ietf-namespace-01.txt > | |||
|---|---|---|---|---|
| Network Working Group B. Leiba | Network Working Group B. Leiba | |||
| Internet-Draft Huawei Technologies | Internet-Draft Huawei Technologies | |||
| Updates: 2648,3553 (if approved) January 2, 2013 | Updates: 2648,3553 (if approved) January 7, 2013 | |||
| Intended status: Informational | Intended status: Informational | |||
| Expires: July 6, 2013 | Expires: July 11, 2013 | |||
| Registration of Second-Level URI Namespaces Under "ietf" | Registration of Second-Level URI Namespaces Under "ietf" | |||
| draft-leiba-urnbis-ietf-namespace-00 | draft-leiba-urnbis-ietf-namespace-01 | |||
| Abstract | Abstract | |||
| RFC 2648 defines the "ietf" URN namespace, and defines a number of | RFC 2648 defines the "ietf" URN namespace, and defines a number of | |||
| sub-namespaces. RFC 3553 defines an additional sub-namespace, | sub-namespaces. RFC 3553 defines an additional sub-namespace, | |||
| "params", and creates a registry to document allocations under that. | "params", and creates a registry to document allocations under that. | |||
| But there is no registry that lists, in one place, all sub-namespaces | But there is no registry that lists, in one place, all sub-namespaces | |||
| of "ietf". This document creates and populates such a registry. | of "ietf". This document creates and populates such a registry. | |||
| Status of this Memo | Status of this Memo | |||
| skipping to change at page 1, line 35 ¶ | skipping to change at page 1, line 35 ¶ | |||
| 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 6, 2013. | This Internet-Draft will expire on July 11, 2013. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2013 IETF Trust and the persons identified as the | Copyright (c) 2013 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 | |||
| skipping to change at page 2, line 32 ¶ | skipping to change at page 2, line 32 ¶ | |||
| the following three actions: | the following three actions: | |||
| Action 1: Rename the group "IETF Protocol Parameter Identifiers", | Action 1: Rename the group "IETF Protocol Parameter Identifiers", | |||
| giving it the new name "Uniform Resource Name (URN) Namespace for | giving it the new name "Uniform Resource Name (URN) Namespace for | |||
| IETF Use". The existing registry in that group will remain, and its | IETF Use". The existing registry in that group will remain, and its | |||
| name will be unchanged. | name will be unchanged. | |||
| Action 2: Add a new registry to the renamed group. The new registry | Action 2: Add a new registry to the renamed group. The new registry | |||
| will be called "IETF URN Sub-namespaces", and new registrations will | will be called "IETF URN Sub-namespaces", and new registrations will | |||
| use the IETF Review policy [RFC5226], which provides for IETF | use the IETF Review policy [RFC5226], which provides for IETF | |||
| consensus in order to add a new URN namespace under "ietf". | consensus in order to add a new URN namespace under "ietf". The new | |||
| registry will appear first in the group, to provide a human-friendly, | ||||
| top-down resolution of the namespace hierarchy. | ||||
| Action 3: Populate the new registry as follows: | Action 3: Populate the new registry as follows: | |||
| IETF URN Sub-namespaces | IETF URN Sub-namespaces | |||
| Registration Procedures: IETF Review | Registration Procedures: IETF Review | |||
| Reference: [RFCXXXX] | Reference: [RFCXXXX] | |||
| Note: This is the Official Registry for sub-namespaces of the 'IETF' | Note: This is the Official Registry for sub-namespaces of the 'IETF' | |||
| URN Namespace. | URN Namespace. | |||
| End of changes. 5 change blocks. | ||||
| 5 lines changed or deleted | 7 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||