idnits 2.17.1 draft-mahesh-etsi-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 (June 08, 2018) is 2146 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- -- Obsolete informational reference (is this intentional?): RFC 5246 (Obsoleted by RFC 8446) Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). 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: December 10, 2018 ETSI 6 June 08, 2018 8 URN Namespace for ETSI Documents 9 draft-mahesh-etsi-urn-03 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 December 10, 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, aeronautical 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 Uniform Resource Names (URNs) [RFC8141] 64 Namespace Identifier (NID) for use by ETSI is being specified in this 65 document, in full conformance with the NID registration process 66 specified in the document. 68 1.1. Terminology 70 +---------+-------------------------------------------------+ 71 | Acronym | Meaning | 72 +---------+-------------------------------------------------+ 73 | ETSI | European Telecommunications Standards Institute | 74 | | | 75 | NID | Namespace Identifier | 76 | | | 77 | NSS | Namespace Specific String | 78 | | | 79 | PNNS | ETSI Protocol Name and Numbering Service | 80 | | | 81 | RDS | Resolution Discovery System | 82 | | | 83 | URN | Uniform Resource Name | 84 +---------+-------------------------------------------------+ 86 2. URN Specification for ETSI 88 Namespace Identifier: 90 etsi 92 Registration information: 94 registration version number: 1 96 registration date: 2018-05-25 98 Declared registrant of the namespace: 100 Registering organization 102 Name: European Telecommunications Standards Institute (ETSI) 104 Address: 650, Route des Lucioles, Sophia Antipolis 06560, 105 France 107 Designated contact: 109 Role: ETSI Protocol Naming and Numbering Service (PNNS) 111 Email: pnns@etsi.org 113 Purpose: 115 To begin with, the URN requested in this document will be used by 116 ETSI for allocation of namespaces to be used by YANG modules, that 117 are developed by the organization. These namespaces are globally 118 unique. The URN will be used in public networks by devices used to 119 configure and manage resources in the network. It is these devices 120 that will enforce the uniqueness of the namespaces by using the 121 namespace and the XPath associated with the managed node in the 122 network, when accessing a resource. 124 Declaration of syntactic structure: 126 The syntax of namespace specific strings for the 'etsi' namespace 127 is in Uniform Resource Names (URNs) [RFC8141]. 129 Relevant ancillary documentation: 131 ETSI publishes information regarding the registered resources in 132 the ETSI URN Namespace (EUN) registry, where it describes the 133 , how the namespaces will be allocated and how experimental 134 namespaces can be used within the allocated URN. 135 (https://portal.etsi.org/PNNS/GenericAllocation/ 136 ETSIURNNamespace.aspx). 138 Identifier uniqueness considerations: 140 ETSI will manage resource classes using the "etsi" NID and will be 141 the authority for managing resources and associated subsequent 142 strings. ETSI will guarantee the uniqueness of the strings 143 themselves, or it may permit secondary responsibility for certain 144 defined resources. 146 ETSI may allow for use of experimental type values for testing 147 purposes only. Note that using experimental types may create 148 collision as multiple users may use the same values for different 149 resources and specific strings. 151 Identifier persistence considerations: 153 ETSI will update the ETSI URN Namespace (EUN) registry to document 154 the registered resources that will use the "etsi" NID. 156 Process of identifier assignment: 158 Assignment of a URN from the ETSI namespace will be documented as 159 part of the ETSI URN Namespace (EUN) registry. 161 Security and Privacy: 163 If an namespace is URN-equivalent to another namespace used by the 164 device, as per the rules specified in Section 3.1 of URNs [RFC8141], 165 Section 6.1 of URI Generic Syntax [RFC3986], and the lexical rules 166 specified in this document, the request is rejected. 168 The YANG modules that will use the namespace assigned by this URN 169 define a schema for data that is designed to be accessed via a 170 network management protocol such as NETCONF [RFC6241] or RESTCONF 171 [RFC8040]. The lowest NETCONF layer is the secure transport layer, 172 and the mandatory-to-implement secure transport is Secure Shell (SSH) 173 [RFC6242]. The lowest RESTCONF layer is HTTPS, and the mandatory-to- 174 implement secure transport is TLS [RFC5246]. 176 Interoperability: 178 There are no known interoperability issues at this time. 180 Process of identifier resolution: 182 The namespace is not listed with an Resolution Discovery System 183 (RDS). Therefore this process is not relevant. 185 Rules for Lexical Equivalence: 187 The entire URN is case-insensitive. 189 Conformance with URN Syntax: 191 No special considerations 193 Validation mechanism: 195 None specified. URN assignment will be handled by procedures 196 implemented in support of ETSI activities. 198 Scope: 200 Global 202 3. Examples 204 The following are examples of URNs that ETSI is looking to assign: 206 urn:etsi:yang:etsi-services 208 urn:etsi:yang:etsi-interfaces 210 4. Security Considerations 212 There are no additional security considerations other than those 213 described above, and are normally associated with the use and 214 resolution of URNs in general, which are described in Function 215 Requirements for URN [RFC1737], Uniform Resource Names (URNs) 216 [RFC8141]. 218 5. IANA Considerations 220 This document adds a new entry ("etsi") in the urn-namespace 221 registry. This is the defining document. When published, the entry 222 can be found in the "Uniform Resource Names (URN) Namespaces" 223 registry available from the IANA site (http://www.iana.org) and any 224 associated mirrors. 226 6. References 228 6.1. Normative References 230 [RFC1737] Sollins, K. and L. Masinter, "Functional Requirements for 231 Uniform Resource Names", RFC 1737, DOI 10.17487/RFC1737, 232 December 1994, . 234 [RFC8141] Saint-Andre, P. and J. Klensin, "Uniform Resource Names 235 (URNs)", RFC 8141, DOI 10.17487/RFC8141, April 2017, 236 . 238 6.2. Informative References 240 [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform 241 Resource Identifier (URI): Generic Syntax", STD 66, 242 RFC 3986, DOI 10.17487/RFC3986, January 2005, 243 . 245 [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security 246 (TLS) Protocol Version 1.2", RFC 5246, 247 DOI 10.17487/RFC5246, August 2008, 248 . 250 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 251 and A. Bierman, Ed., "Network Configuration Protocol 252 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 253 . 255 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure 256 Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 257 . 259 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 260 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 261 . 263 Authors' Addresses 265 Mahesh Jethanandani 266 USA 268 Email: mjethanandani@gmail.com 270 Miguel Angel Reina Ortega 271 ETSI 272 650, Route des Lucioles 273 Sophia Antipolis 06560 274 France 276 Email: MiguelAngel.ReinaOrtega@etsi.org