ReinaOrtega, et al. Expires Sep 27, 2022 [Page 1] Internet-Draft Namespace for oneM2M Nov 2021 Network Working Group P. Niblett Internet-Draft IBM United Kingdom Limited Intended status: Informational A. Kraft Expires: May 9, 2022 Deutsche Telekom AG M.A. Reina Ortega, Ed. European Telecommunication Standards Institute Nov 05, 2021 A Uniform Resource Name (URN) Namespace for the oneM2M Partnership Project (oneM2M) draft-reinaortega-urn-onem2m-00 Abstract This document describes the Namespace Identifier (NID) 'onem2m' for Uniform Resource Names (URNs) used to identify resources published by the oneM2M Partnership Project (www.oneM2M.org). oneM2M specifies and manages resources that utilize this URN identification model. Management activities for these and other resource types are handled by the oneM2M Secretariat. 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 Sep 27, 2022. Copyright Notice Copyright (c) 2022 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 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. Table of Contents 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . 2 1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 2 2. URN Specification for the oneM2M Namespace Identifier (NID) . 2 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Security considerations . . . . . . . . . . . . . . . . . . . 6 5. IANA considerations . . . . . . . . . . . . . . . . . . . . . 6 6. References. . . . . . . . . . . . . . . . . . . . . . . . . . 6 6.1 Normative References . . . . . . . . . . . . . . . . . . . 6 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 1. Introduction oneM2M is the global standards initiative that covers requirements, architecture, API specifications, security solutions and interoperability for Machine-to-Machine(M2M) and IoT technologies. This activity is supported by a membership composed of network operators, equipment vendors, and other suppliers to the M2M/IoT market. Some of the technologies being developed by oneM2M 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 oneM2M 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 | | | | | RDS | Resolution Discovery System | | | | | URI | Uniform Resouce Identifier | | | | | URN | Uniform Resource Name | +---------+-------------------------------------------------+ 2. URN Specification for the oneM2M Namespace Identifier (NID) Namespace Identifier: onem2m Version: 1 Date: 2022-02-21 Registrant: Name: oneM2M Partnership Project Address: ETSI 650, route des Lucioles 06921 Sophia-Antipolis Cedex France Designated contact Role: oneM2M Secretariat Email: onem2m_contact@list.onem2m.org Purpose: The Namespace Identifier (NID) 'onem2m' for Uniform Resource Names (URNs) will be used to identify resources published by the oneM2M Partnership Project. These might include published standards or protocols that it defines and which make use of URNs. These namespaces are globally unique. The URN namespace will be used in public networks by clients to configure and manage resources in the network. It is the servers 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. Syntax: The syntax of namespace specific strings for the 'onem2m' namespace is in Uniform Resource Names (URNs) [RFC8141]. The entire URN is case-insensitive. Assignment: oneM2M will maintain the list of registered subtrees that use the 'onem2m' NID at https://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace, in the oneM2M URN Namespace registry. It will describe the , how the namespaces will be allocated, and how experimental namespaces can be used within the allocated URN. oneM2M will manage resource classes using the 'onem2m' NID and will be the authority for managing resources and associated subsequent strings. oneM2M will guarantee the uniqueness of the strings themselves, by validating it against the existing content of the registry. It may also permit secondary responsibility for certain defined resources. Once a subtree assignment is made, it cannot be deleted or reassigned. oneM2M may allow for use of experimental type values in specific subtrees, 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. All experimentation must follow the guidance set forth in A Uniform Resource Name (URN) Namespace for Examples [RFC6963]. Interoperability: There are no known interoperability issues at this time. Resolution: It is not foreseen that URNs within this namespace will undergo resolution. Documentation: Documentation can be found at https://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace. 3. Examples The following examples are representative URNs that could be assigned by oneM2M. They are not actual strings that are assigned. urn:onem2m:sds Defines the "onem2m-urn" to be used for oneM2M SDS WG. urn:onem2m:model:sensor-a Defines the URN associated with the information model for some types of sensor devices identified by the name "sensor-a". 4. Security considerations There are no additional security considerations that 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 IANA is requested to register the formal URN namespace "onem2m" using the template given above in Section 2. 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, . [RFC6963] Saint-Andre, P., "A Uniform Resource Name (URN) Namespace for Examples", BCP 183, RFC 6963, DOI 10.17487/RFC6963, May 2013, . [RFC8141] Saint-Andre, P. and J. Klensin, "Uniform Resource Names (URNs)", RFC 8141, DOI 10.17487/RFC8141, April 2017, . Authors' Addresses Peter Niblett IBM United Kingdom Limited PO Box 41, North Harbour Portsmouth , Hampshire PO6 3AU United Kingdom Email: peter_niblett@uk.ibm.com Andreas Kraft Deutsche Telekom AG Holzhauser Straße 4-8 13509 Berlin Germany Email: a.kraft@telekom.de Miguel Angel Reina Ortega (editor) European Telecommunication Standards Institute 650 Route des lucioles Sophia Antipolis 06921 France Phone: 0033492944349 Email: miguelangel.reinaortega@etsi.org