idnits 2.17.1 draft-mahesh-etsi-urn-00.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 (May 19, 2018) is 2159 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 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 M. Jethanandani 3 Internet-Draft 4 Intended status: Informational M. Angel Reina Ortega 5 Expires: November 20, 2018 ETSI 6 May 19, 2018 8 URN Namespace for ETSI Documents 9 draft-mahesh-etsi-urn-00 11 Abstract 13 This document describes the Namespace Identifier (NID) 'etsi' for 14 Uniform Resource Names (URNs) used to identify resources published by 15 European Telecommuncations Standards Instititue (http://etsi.org). 16 ETSI specifies and manages resources that utilize this URN 17 identification model. Management activities for these and other 18 resources types are handled by the manager of the ETSI Assigned Names 19 and Numbers (EANN) registry. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at https://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on November 20, 2018. 38 Copyright Notice 40 Copyright (c) 2018 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (https://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 1. Introduction 55 ETSI is a nonprofit international industry standards organization, 56 that produces globally acceptable standards for Information & 57 Communication Technologies including fixed, mobile, radio, broadcast, 58 internet, aeornautical and other areas. 60 As part of these specifications efforts, there is a need to identify 61 identifiers in a managed namespace that are unique and persistent. 62 To ensure that this namespace's uniqueness is absolute, a 63 registration of a specific Unified Resource Name (URN) Uniform 64 Resource Names (URNs) [RFC8141] Namespace Identifier (NID) for use by 65 ETSI is being specified in this document, in full conformance with 66 the NID registration process specified in the document. 68 1.1. Terminology 70 +---------+--------------------------------------------------+ 71 | Acronym | Meaning | 72 +---------+--------------------------------------------------+ 73 | EANN | ETSI Assigned Names and Numbers | 74 | | | 75 | ETSI | European Telecommunications Standards Instititue | 76 | | | 77 | NID | Namespace Identifier | 78 | | | 79 | NSS | Namespace Specific String | 80 | | | 81 | RDS | Resolution Discovery System | 82 | | | 83 | URN | Uniform Resource Name | 84 +---------+--------------------------------------------------+ 86 2. URN Specification for ETSI 88 Namespace ID: 90 etsi 92 Registration information: 94 registration version number: 1 96 registration date: 2018-05-01 98 Declared registrant of the namespace: 100 Registering organization 102 Name: ETSI 104 Address: 650, Route des Lucioles, Sophia Antipoles 06560, 105 France 107 Designated contact: 109 Role: ETSI Protocol Naming and Numbering Service 111 Email: pnns@etsi.org 113 Declaration of syntactic structure: 115 The syntax of namespace specific strings for the 'etsi' namespace 116 is in Uniform Resource Names (URNs) [RFC8141]. 118 Relevant ancillary documentation: 120 ETSI publishes information regarding the registered resources in 121 the ETSI URN Namespace (EUN) registry 122 (https://portal.etsi.org/PNNS/GenericAllocation/ 123 ETSIURNNamespace.aspx). 125 Identifier uniqueness considerations: 127 ETSI will manage resource classes using the "etsi" NID and will be 128 the authority for managing resources and associated subsequent 129 strings. ETSI is expected to guarantee the uniqueness of the 130 strings themselves, or it may permit secondary responsibility for 131 certain defined resources. 133 ETSI could allow for use of experimental type values for testing 134 purposes only. Note that using experimental types may create 135 collision as multiple users may use the same values for different 136 resources and specific strings. 138 Identifier persistence considerations: 140 ETSI will update the ETSI Assigned Names and Numbers (EANN) 141 registry to document the registered resources that will use the 142 "etsi" NID. 144 Process of identifier assignment: 146 Assignment of a URN from the ETSI namespace will be documented as 147 part of the ETSI Assigned Names and Numbers (EANN) registry. 149 Process of identifier resolution: 151 The namespace is not listed with an Resolution Discovery System 152 (RDS). Therefore this process is not relevant. 154 Rules for Lexical Equivalence: 156 The entire URN is case-insensitive. 158 Conformance with URN Syntax: 160 No special considerations 162 Validation mechanism: 164 None specified. URN assignment will be handled by procedures 165 implemented in support of ETSI activities. 167 Scope: 169 Global 171 3. Examples 173 The following are examples of URNs that ETSI is looking to assign: 175 urn:etsi:yang:etsi-services 177 urn:etsi:yang:etsi-interfaces 179 4. Security Considerations 181 There are no additional security considerations other than those 182 normally associated with the use and resolution of URNs in general, 183 which are described in Function Requirements for URN [RFC1737], 184 Uniform Resource Names (URNs) [RFC8141]. 186 5. IANA Considerations 188 This document adds a new entry ("etsi") in the urn-namespace 189 registry. This is the defining document. When published, the entry 190 can be found in the "Uniform Resource Names (URN) Namespaces" 191 registry available from the IANA site (http://www.iana.org) and any 192 associated mirrors. 194 6. Normative References 196 [RFC1737] Sollins, K. and L. Masinter, "Functional Requirements for 197 Uniform Resource Names", RFC 1737, DOI 10.17487/RFC1737, 198 December 1994, . 200 [RFC8141] Saint-Andre, P. and J. Klensin, "Uniform Resource Names 201 (URNs)", RFC 8141, DOI 10.17487/RFC8141, April 2017, 202 . 204 Authors' Addresses 206 Mahesh Jethanandani 207 USA 209 Email: mjethanandani@gmail.com 211 Miguel Angel Reina Ortega 212 ETSI 213 650, Route des Lucioles 214 Sophia Antipoles 06560 215 France 217 Email: MiguelAngel.ReinaOrtega@etsi.org