idnits 2.17.00 (12 Aug 2021) /tmp/idnits26104/draft-leiba-urnbis-ietf-namespace-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The draft header indicates that this document updates RFC2648, but the abstract doesn't seem to directly say this. It does mention RFC2648 though, so this could be OK. -- The draft header indicates that this document updates RFC3553, but the abstract doesn't seem to directly say this. It does mention RFC3553 though, so this could be OK. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC2648, updated by this document, for RFC5378 checks: 1997-05-14) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (January 7, 2013) is 3420 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'RFCXXXX' is mentioned on line 86, but not defined ** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126) Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group B. Leiba 3 Internet-Draft Huawei Technologies 4 Updates: 2648,3553 (if approved) January 7, 2013 5 Intended status: Informational 6 Expires: July 11, 2013 8 Registration of Second-Level URI Namespaces Under "ietf" 9 draft-leiba-urnbis-ietf-namespace-01 11 Abstract 13 RFC 2648 defines the "ietf" URN namespace, and defines a number of 14 sub-namespaces. RFC 3553 defines an additional sub-namespace, 15 "params", and creates a registry to document allocations under that. 16 But there is no registry that lists, in one place, all sub-namespaces 17 of "ietf". This document creates and populates such a registry. 19 Status of this Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on July 11, 2013. 36 Copyright Notice 38 Copyright (c) 2013 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 1. Introduction 53 "A URN Namespace for IETF Documents" [RFC2648] defines the "ietf" URN 54 namespace, and defines a number of sub-namespaces. "An IETF URN Sub- 55 namespace for Registered Protocol Parameters" [RFC3553] defines an 56 additional sub-namespace, "params", and creates a registry to 57 document allocations under that. But there is no registry that 58 lists, in one place, all sub-namespaces of "ietf". This document 59 creates and populates such a registry, and updates RFC 2648 and RFC 60 3553 to refer readers of those documents to this registry. 62 2. IANA Considerations 64 There is currently a top-level registry group called "IETF Protocol 65 Parameter Identifiers", which contains one registry, "IETF URN Sub- 66 namespace for Registered Protocol Parameters". IANA is asked to take 67 the following three actions: 69 Action 1: Rename the group "IETF Protocol Parameter Identifiers", 70 giving it the new name "Uniform Resource Name (URN) Namespace for 71 IETF Use". The existing registry in that group will remain, and its 72 name will be unchanged. 74 Action 2: Add a new registry to the renamed group. The new registry 75 will be called "IETF URN Sub-namespaces", and new registrations will 76 use the IETF Review policy [RFC5226], which provides for IETF 77 consensus in order to add a new URN namespace under "ietf". The new 78 registry will appear first in the group, to provide a human-friendly, 79 top-down resolution of the namespace hierarchy. 81 Action 3: Populate the new registry as follows: 83 IETF URN Sub-namespaces 85 Registration Procedures: IETF Review 86 Reference: [RFCXXXX] 88 Note: This is the Official Registry for sub-namespaces of the 'IETF' 89 URN Namespace. 91 Sub-namespace | Reference | IANA Registry Reference 92 --------------+-----------+----------------------------------------- 93 rfc | [RFC2648] | none 94 fyi | [RFC2648] | none 95 std | [RFC2648] | none 96 bcp | [RFC2648] | none 97 id | [RFC2648] | none 98 mtg | [RFC2648] | none 99 params | [RFC3553] | [http://www.iana.org/assignments/params] 100 --------------+-----------+----------------------------------------- 102 [[anchor1: IANA and RFC Editor: Please replace "XXXX", above, with 103 this RFC number, and remove this note.]] 105 3. Security Considerations 107 This is a procedural document, and is entirely unrelated to security. 109 4. References 111 4.1. Normative References 113 [RFC2648] Moats, R., "A URN Namespace for IETF Documents", RFC 2648, 114 August 1999. 116 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an 117 IANA Considerations Section in RFCs", BCP 26, RFC 5226, 118 May 2008. 120 4.2. Informative References 122 [RFC3553] Mealling, M., Masinter, L., Hardie, T., and G. Klyne, "An 123 IETF URN Sub-namespace for Registered Protocol 124 Parameters", BCP 73, RFC 3553, June 2003. 126 Author's Address 128 Barry Leiba 129 Huawei Technologies 131 Phone: +1 646 827 0648 132 Email: barryleiba@computer.org 133 URI: http://internetmessagingtechnology.org/