idnits 2.17.1 draft-ieee-urn-03.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (November 16, 2016) is 2689 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 3406 (Obsoleted by RFC 8141) ** Obsolete normative reference: RFC 2141 (Obsoleted by RFC 8141) Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group A. Thomas 3 Internet-Draft IEEE 4 Intended status: Informational 5 Expires: April 16, 2017 November 16, 2016 7 URN Namespace for IEEE 8 draft-ieee-urn-03 10 Abstract 12 This document describes the Namespace Identifier (NID) 'ieee' for 13 Uniform Resource Names (URNs) used to identify resources published by 14 the Institute of Electrical and Electronics Engineers (IEEE). IEEE 15 specifies and manages resources that utilize this URN identification 16 model. Management activities for these and other resources types are 17 handled by the manager of the IEEE Registration Authority. 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 March 26, 2017. 36 Copyright Notice 38 Copyright (c) 2016 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 The Institute of Electrical and Electronic Engineers (IEEE) is an 54 organization whose objectives include the educational and technical 55 advancement of electrical and electronic engineering, 56 telecommunications, computer engineering and allied disciplines. 57 Within IEEE, standardization activities are organized into sponsors, 58 such as the LAN/MAN Stadnards Commitee, and then working groups 59 such as 802.1 and 802.3. See http://standards.ieee.org. 61 As part of these specifications efforts, there is a need to identify 62 identifiers in a managed namespace that are unique and persistent. 63 To ensure that this namespace's uniqueness is absolute, a 64 registration of a specific Unified Resource Name (URN) URN Syntax 65 [RFC2141] Namespace Identifier (NID) for use by IEEE is being 66 specified in this document, in full conformance with the NID 67 registration process specified in URN Namespace Definition Mechanism 68 [RFC3406]. 70 1.1. Terminology 72 +---------+---------------------------------------------------+ 73 | Acronym | Meaning | 74 +---------+---------------------------------------------------+ 75 | IEEE | Institute of Electrical and Electronics Engineers | 76 | | | 77 | NID | Namespace Identifier | 78 | | | 79 | URN | Uniform Resource Name | 80 +---------+---------------------------------------------------+ 82 2. URN Specification for IEEE 84 Namespace ID: 86 ieee 88 Registration information: 90 registration version number: 1 91 registration date: 2016-09-26 92 (Note to RFC Editor: Please update the registration date when this 93 request gets accepted and remove this instruction) 95 Declared registrant of the namespace: 97 Registering organization: 99 Name: Institute of Electrical and Electronics Engineers 101 Address: 445 Hoes Lane 102 Piscataway, NJ 08854 103 USA 105 Designated contact: Angela Thomas 107 Role: Manager, IEEE Registration Authority 109 Email: ieee-registration-authority@ieee.org 111 Declaration of syntactic structure: 113 The Namespace Specific String (NSS) of all URNs that use the 114 IEEE NID will have the following structure: 116 urn:ieee:{IEEEresource}:{ResourceSpecificString} 118 where the "IEEEresource" is a US-ASCII string that conforms to the 119 URN syntax requirements [RFC2141] and defines a specific class of 120 resource type. Each resource type has a specific labeling scheme 121 that is covered by "ResourceSpecificString", which also conforms 122 to the naming requirements of [RFC2141]. 124 IEEE maintains a registration authority, the IEEE Registration 125 Authority (IEEE RA), that will manage the assignment of 126 "IEEEresource" and the specific registration values assigned 127 for each resource class. 129 Relevant ancillary documentation: 131 The IEEE Registration Authority (IEEE RA) provides information on 132 the registered resources and the registrations for each. More 133 information about this registry and the procedures to be followed 134 are available at: 136 http://standards.ieee.org/develop/regauth/tut/ieeeurn.pdf 138 Identifier uniqueness considerations: 140 The IEEE RA will manage resources using the IEEE NID and will be 141 the authority for managing the resources and subsequent strings 142 associated. In the associated procedures, IEEE RA will ensure the 143 uniqueness of the strings themselves or shall permit secondary 144 responsibility for management of well-defined sub-trees. 146 Identifier persistence considerations: 148 IEEE will update documentation of the registered uses of the IEEE 149 NID as needed. This will be structured such that each 150 "IEEEresource" will have a separate description and registration 151 table. 153 The registration tables and information are published and 154 maintained by the IEEE RA on its web site. 156 Process of identifier assignment: 158 IEEE RA will provide procedures for registration of each type of 159 resource that it maintains. 161 Process of identifier resolution: 163 The namespace is not listed with an RDS; this is not relevant. 165 Rules for Lexical Equivalence: 167 The strings used as values of "IEEEresource" and 168 "ResourceSpecificString" are case-insensitive. 170 Conformance with URN Syntax: 172 No special considerations. 174 Validation mechanism: 176 None specified. URN assignment will be handled by procedures 177 implemented in support of IEEE activities. 179 Scope: 181 Global 183 3. Examples 185 The following examples are representative URNs that could be assigned 186 by IEEE RA. While support for YANG [RFC6020],[RFC7950] was a driver 187 for the creation of the namespace, the following are not necessarily 188 the strings that would be assigned. 190 urn:ieee:std:802.5:yang 192 urn:ieee:foobar 194 4. Security Considerations 196 There are no additional security considerations other than those 197 normally associated with the use and resolution of URNs in general, 198 which are described in Functional Requirements for URN [RFC1737], URN 199 Syntax [RFC2141], and URN Namespace Definition Mechanism [RFC3406]. 201 5. IANA Considerations 203 This document adds a new entry ("ieee") in the urn-namespace 204 registry. This is the defining document. When published, the entry 205 can be found in the "Uniform Resource Names (URN) Namespaces" 206 registry available from the IANA site (http://www.iana.org) and any 207 associated mirrors. 209 6. References 211 6.1. Normative References 213 [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, 214 "Uniform Resource Names (URN) Namespace Definition 215 Mechanisms", BCP 66, RFC 3406, DOI 10.17487/RFC3406, 216 October 2002, . 218 [RFC2141] Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141, 219 May 1997, . 221 6.2. Informative References 223 [RFC1737] Sollins, K. and L. Masinter, "Functional Requirements for 224 Uniform Resource Names", RFC 1737, DOI 10.17487/RFC1737, 225 December 1994, . 227 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 228 the Network Configuration Protocol (NETCONF)", RFC 6020, 229 DOI 10.17487/RFC6020, October 2010, 230 . 232 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 233 RFC 7950, DOI 10.17487/RFC7950, August 2016, 234 . 236 Acknowledgements 238 The IEEE Registration Authority Committee (RAC) is the oversight 239 committee for the IEEE Registration Authority. The content of this 240 document has been coordinated with the RAC. The technical contact 241 from the RAC was: 243 Glenn Parsons 244 Email: glenn.parsons@ericsson.com 246 Authors' Addresses 248 Angela Thomas 249 IEEE Registration Authority 250 445 Hoes Lane 251 Piscataway, NJ 08854 252 USA 254 Phone: +1 732 465 6481 255 Email: a.n.thomas@ieee.org