Network Working Group M. Jethanandani Internet-Draft Intended status: Informational M. Angel Reina Ortega Expires: December 10, 2018 ETSI June 08, 2018 URN Namespace for ETSI Documents draft-mahesh-etsi-urn-03 Abstract This document describes the Namespace Identifier (NID) 'etsi' for Uniform Resource Names (URNs) used to identify resources published by European Telecommunications Standards Institute (http://etsi.org). ETSI specifies and manages resources that utilize this URN identification model. Management activities for these and other resources types are handled by the manager of the ETSI Protocol Naming and Numbering Service (PNNS). Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on December 10, 2018. Copyright Notice Copyright (c) 2018 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must Jethanandani & Angel ReiExpiresgDecember 10, 2018 [Page 1] Internet-Draft Namespace for ETSI June 2018 include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. 1. Introduction ETSI is a nonprofit international industry standards organization, that produces globally acceptable standards for Information & Communication Technologies including fixed, mobile, radio, broadcast, internet, aeronautical and other areas. As part of these specifications efforts, there is a need to identify identifiers in a managed namespace that are unique and persistent. To ensure that this namespace's uniqueness is absolute, a registration of a specific Uniform Resource Names (URNs) [RFC8141] Namespace Identifier (NID) for use by ETSI is being specified in this document, in full conformance with the NID registration process specified in the document. 1.1. Terminology +---------+-------------------------------------------------+ | Acronym | Meaning | +---------+-------------------------------------------------+ | ETSI | European Telecommunications Standards Institute | | | | | NID | Namespace Identifier | | | | | NSS | Namespace Specific String | | | | | PNNS | ETSI Protocol Name and Numbering Service | | | | | RDS | Resolution Discovery System | | | | | URN | Uniform Resource Name | +---------+-------------------------------------------------+ 2. URN Specification for ETSI Namespace Identifier: etsi Registration information: registration version number: 1 registration date: 2018-05-25 Jethanandani & Angel ReiExpiresgDecember 10, 2018 [Page 2] Internet-Draft Namespace for ETSI June 2018 Declared registrant of the namespace: Registering organization Name: European Telecommunications Standards Institute (ETSI) Address: 650, Route des Lucioles, Sophia Antipolis 06560, France Designated contact: Role: ETSI Protocol Naming and Numbering Service (PNNS) Email: pnns@etsi.org Purpose: To begin with, the URN requested in this document will be used by ETSI for allocation of namespaces to be used by YANG modules, that are developed by the organization. These namespaces are globally unique. The URN will be used in public networks by devices used to configure and manage resources in the network. It is these devices that will enforce the uniqueness of the namespaces by using the namespace and the XPath associated with the managed node in the network, when accessing a resource. Declaration of syntactic structure: The syntax of namespace specific strings for the 'etsi' namespace is in Uniform Resource Names (URNs) [RFC8141]. Relevant ancillary documentation: ETSI publishes information regarding the registered resources in the ETSI URN Namespace (EUN) registry, where it describes the , how the namespaces will be allocated and how experimental namespaces can be used within the allocated URN. (https://portal.etsi.org/PNNS/GenericAllocation/ ETSIURNNamespace.aspx). Identifier uniqueness considerations: ETSI will manage resource classes using the "etsi" NID and will be the authority for managing resources and associated subsequent Jethanandani & Angel ReiExpiresgDecember 10, 2018 [Page 3] Internet-Draft Namespace for ETSI June 2018 strings. ETSI will guarantee the uniqueness of the strings themselves, or it may permit secondary responsibility for certain defined resources. ETSI may allow for use of experimental type values for testing purposes only. Note that using experimental types may create collision as multiple users may use the same values for different resources and specific strings. Identifier persistence considerations: ETSI will update the ETSI URN Namespace (EUN) registry to document the registered resources that will use the "etsi" NID. Process of identifier assignment: Assignment of a URN from the ETSI namespace will be documented as part of the ETSI URN Namespace (EUN) registry. Security and Privacy: If an namespace is URN-equivalent to another namespace used by the device, as per the rules specified in Section 3.1 of URNs [RFC8141], Section 6.1 of URI Generic Syntax [RFC3986], and the lexical rules specified in this document, the request is rejected. The YANG modules that will use the namespace assigned by this URN define a schema for data that is designed to be accessed via a network management protocol such as NETCONF [RFC6241] or RESTCONF [RFC8040]. The lowest NETCONF layer is the secure transport layer, and the mandatory-to-implement secure transport is Secure Shell (SSH) [RFC6242]. The lowest RESTCONF layer is HTTPS, and the mandatory-to- implement secure transport is TLS [RFC5246]. Interoperability: There are no known interoperability issues at this time. Process of identifier resolution: The namespace is not listed with an Resolution Discovery System (RDS). Therefore this process is not relevant. Rules for Lexical Equivalence: The entire URN is case-insensitive. Conformance with URN Syntax: Jethanandani & Angel ReiExpiresgDecember 10, 2018 [Page 4] Internet-Draft Namespace for ETSI June 2018 No special considerations Validation mechanism: None specified. URN assignment will be handled by procedures implemented in support of ETSI activities. Scope: Global 3. Examples The following are examples of URNs that ETSI is looking to assign: urn:etsi:yang:etsi-services urn:etsi:yang:etsi-interfaces 4. Security Considerations There are no additional security considerations other than those described above, and are normally associated with the use and resolution of URNs in general, which are described in Function Requirements for URN [RFC1737], Uniform Resource Names (URNs) [RFC8141]. 5. IANA Considerations This document adds a new entry ("etsi") in the urn-namespace registry. This is the defining document. When published, the entry can be found in the "Uniform Resource Names (URN) Namespaces" registry available from the IANA site (http://www.iana.org) and any associated mirrors. 6. References 6.1. Normative References [RFC1737] Sollins, K. and L. Masinter, "Functional Requirements for Uniform Resource Names", RFC 1737, DOI 10.17487/RFC1737, December 1994, . [RFC8141] Saint-Andre, P. and J. Klensin, "Uniform Resource Names (URNs)", RFC 8141, DOI 10.17487/RFC8141, April 2017, . Jethanandani & Angel ReiExpiresgDecember 10, 2018 [Page 5] Internet-Draft Namespace for ETSI June 2018 6.2. Informative References [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, DOI 10.17487/RFC3986, January 2005, . [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security (TLS) Protocol Version 1.2", RFC 5246, DOI 10.17487/RFC5246, August 2008, . [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., and A. Bierman, Ed., "Network Configuration Protocol (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, . [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, . [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, . Authors' Addresses Mahesh Jethanandani USA Email: mjethanandani@gmail.com Miguel Angel Reina Ortega ETSI 650, Route des Lucioles Sophia Antipolis 06560 France Email: MiguelAngel.ReinaOrtega@etsi.org Jethanandani & Angel ReiExpiresgDecember 10, 2018 [Page 6]