idnits 2.17.1 draft-mahesh-etsi-urn-05.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 17, 2018) is 1987 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 VMware 4 Intended status: Informational M. Angel Reina Ortega 5 Expires: May 21, 2019 ETSI 6 November 17, 2018 8 URN Namespace for ETSI Documents 9 draft-mahesh-etsi-urn-05 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 Telecommunications Standards Institute (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 Protocol 19 Naming and Numbering Service (PNNS). 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 May 21, 2019. 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 Table of Contents 55 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 56 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. URN Specification for ETSI . . . . . . . . . . . . . . . . . 3 58 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 5 59 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 60 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 61 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 62 6.1. Normative References . . . . . . . . . . . . . . . . . . 5 63 6.2. Informative References . . . . . . . . . . . . . . . . . 6 64 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 66 1. Introduction 68 ETSI is a nonprofit international industry standards organization, 69 that produces globally acceptable standards for Information & 70 Communication Technologies including fixed, mobile, radio, broadcast, 71 internet, aeronautical and other areas. 73 As part of these specifications efforts, there is a need to identify 74 identifiers in a managed namespace that are unique and persistent. 75 To ensure that this namespace's uniqueness is absolute, a 76 registration of a specific Uniform Resource Names (URNs) [RFC8141] 77 Namespace Identifier (NID) for use by ETSI is being specified in this 78 document, in full conformance with the NID registration process 79 specified in the document. 81 1.1. Terminology 82 +---------+-------------------------------------------------+ 83 | Acronym | Meaning | 84 +---------+-------------------------------------------------+ 85 | ETSI | European Telecommunications Standards Institute | 86 | | | 87 | EUN | ETSI URN Namespace | 88 | | | 89 | NID | Namespace Identifier | 90 | | | 91 | NSS | Namespace Specific String | 92 | | | 93 | PNNS | Protocol Name and Numbering Service | 94 | | | 95 | RDS | Resolution Discovery System | 96 | | | 97 | URI | Uniform Resouce Identifier | 98 | | | 99 | URN | Uniform Resource Name | 100 +---------+-------------------------------------------------+ 102 2. URN Specification for ETSI 104 Namespace Identifier: 106 etsi 108 Version: 110 1 112 Date: 114 2018-10-22 116 Registrant: 118 ETSI Protocol Naming and Numbering Service (PNNS) 120 European Telecommunications Standards Institute (ETSI) 122 650, Route des Lucioles, Sophia Antipolis 06560, France 124 pnns@etsi.org 126 Purpose: 128 The Namespace Identifier (NID) 'etsi' for Uniform Resource Names 129 (URNs) will be used to identify resources published by ETSI. These 130 might include published standards or protocols that it defines and 131 which make use of URNs. These namespaces are globally unique. The 132 URN namespace will be used in public networks by clients to configure 133 and manage resources in the network. It is the servers that will 134 enforce the uniqueness of the namespaces by using the namespace and 135 the XPath associated with the managed node in the network, when 136 accessing a resource. 138 Syntax: 140 The syntax of namespace specific strings for the 'etsi' namespace 141 is in Uniform Resource Names (URNs) [RFC8141]. 143 The entire URN is case-insensitive. 145 Assignment: 147 ETSI will maintain the list of registered subtrees that use the 148 "etsi" NID at https://portal.etsi.org/PNNS/GenericAllocation/ 149 ETSIURNNamespace.aspx, in the ETSI URN Namespace (EUN) registry. 150 It will describe the , how the namespaces will be allocated, 151 and how experimental namespaces can be used within the allocated 152 URN. 154 ETSI will manage resource classes using the "etsi" NID and will be 155 the authority for managing resources and associated subsequent 156 strings. ETSI will guarantee the uniqueness of the strings 157 themselves, by validating it against the existing content of the 158 registry. It may also permit secondary responsibility for certain 159 defined resources. Once a subtree assignment is made, it cannot 160 be deleted or reassigned. 162 ETSI may allow for use of experimental type values in specific 163 subtrees, for testing purposes only. Note that using experimental 164 types may create collision as multiple users may use the same 165 values for different resources and specific strings. All 166 experimentation must follow the guidance set forth in A Uniform 167 Resource Name (URN) Namespace for Examples [RFC6963]. 169 Interoperability: 171 There are no known interoperability issues at this time. 173 Resolution: 175 It is not foreseen that URNs within this namespace will undergo 176 resolution. 178 Documentation: 180 Documentation can be found at 181 https://portal.etsi.org/PNNS/GenericAllocation/ 182 ETSIURNNamespace.aspx. 184 3. Examples 186 The following are examples of URNs that ETSI is looking to assign: 188 urn:etsi:yang:etsi-nfv 190 urn:etsi:yang:etsi-nfv-vnf 192 urn:etsi:yang:etsi-nfv-pnf 194 Although all of these examples are related to network management with 195 YANG [RFC7950], URNs related to other kinds of resources might be 196 assigned in the future, in which case a "sub-identifier" other than 197 "yang" might be created. 199 4. Security Considerations 201 There are no additional security considerations that are normally 202 associated with the use and resolution of URNs in general, which are 203 described in Function Requirements for URN [RFC1737], Uniform 204 Resource Names (URNs) [RFC8141]. 206 5. IANA Considerations 208 IANA is requested to register the formal URN namespace "etsi" using 209 the template given above in Section 2. 211 6. References 213 6.1. Normative References 215 [RFC1737] Sollins, K. and L. Masinter, "Functional Requirements for 216 Uniform Resource Names", RFC 1737, DOI 10.17487/RFC1737, 217 December 1994, . 219 [RFC6963] Saint-Andre, P., "A Uniform Resource Name (URN) Namespace 220 for Examples", BCP 183, RFC 6963, DOI 10.17487/RFC6963, 221 May 2013, . 223 [RFC8141] Saint-Andre, P. and J. Klensin, "Uniform Resource Names 224 (URNs)", RFC 8141, DOI 10.17487/RFC8141, April 2017, 225 . 227 6.2. Informative References 229 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 230 RFC 7950, DOI 10.17487/RFC7950, August 2016, 231 . 233 Authors' Addresses 235 Mahesh Jethanandani 236 VMware 237 USA 239 Email: mjethanandani@gmail.com 241 Miguel Angel Reina Ortega 242 ETSI 243 650, Route des Lucioles 244 Sophia Antipolis 06560 245 France 247 Email: MiguelAngel.ReinaOrtega@etsi.org