idnits 2.17.1 draft-fujimoto-urn-onem2m-01.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 (March 12, 2018) is 2227 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 2141 (Obsoleted by RFC 8141) ** Obsolete normative reference: RFC 3406 (Obsoleted by RFC 8141) Summary: 2 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 S. Fujimoto, Ed. 3 Internet-Draft Fujitsu Laboratories LTD 4 Intended status: Standards Track P. Niblett 5 Expires: September 13, 2018 IBM United Kingdom Limited 6 S. Reina Ortega, Ed. 7 European Telecommunication Standards Institute 8 March 12, 2018 10 A Uniform Resource Name (URN) Namespace for the oneM2M Partnership 11 Project (oneM2M) 12 draft-fujimoto-urn-onem2m-01 14 Abstract 16 This document describes the Namespace Identifier (NID) for Uniform 17 Resource Namespace (URN) resources published by the oneM2M 18 Partnership Project (oneM2M). oneM2M defines and manages resources 19 that utilize this URN name model. Management activities for these 20 and other resource types are provided by the oneM2M Secretariat. 22 Status of This Memo 24 This Internet-Draft is submitted in full conformance with the 25 provisions of BCP 78 and BCP 79. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF). Note that other groups may also distribute 29 working documents as Internet-Drafts. The list of current Internet- 30 Drafts is at https://datatracker.ietf.org/drafts/current/. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 This Internet-Draft will expire on September 13, 2018. 39 Copyright Notice 41 Copyright (c) 2018 IETF Trust and the persons identified as the 42 document authors. All rights reserved. 44 This document is subject to BCP 78 and the IETF Trust's Legal 45 Provisions Relating to IETF Documents 46 (https://trustee.ietf.org/license-info) in effect on the date of 47 publication of this document. Please review these documents 48 carefully, as they describe your rights and restrictions with respect 49 to this document. Code Components extracted from this document must 50 include Simplified BSD License text as described in Section 4.e of 51 the Trust Legal Provisions and are provided without warranty as 52 described in the Simplified BSD License. 54 Table of Contents 56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 57 2. URN Specification for the oneM2M Namespace Identifier (NID) . 2 58 3. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 5 59 4. Namespace considerations . . . . . . . . . . . . . . . . . . 5 60 5. Comunity considerations . . . . . . . . . . . . . . . . . . . 5 61 6. Security Considerations . . . . . . . . . . . . . . . . . . . 6 62 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 63 8. Normative References . . . . . . . . . . . . . . . . . . . . 6 64 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6 66 1. Introduction 68 oneM2M is the global standards initiative that covers requirements, 69 architecture, API specifications, security solutions and 70 interoperability for Machine-to-Machine(M2M) and IoT technologies. 71 This activity is supported by a membership composed of network 72 operators, equipment vendors, and other suppliers to the M2M/IoT 73 market. 75 Some of the technologies being developed by oneM2M need URN 76 namespaces that are managed so that they are unique and persistent. 77 To assure that the uniqueness is absolute, the registration of a 78 specific NID for use by oneM2m was deemed appropriate. Therefore, a 79 full and complete registration will follow the namespace 80 specification process as defined in RFC 3406 [RFC3406]. 82 2. URN Specification for the oneM2M Namespace Identifier (NID) 84 Namespace ID: 86 1m2m 88 Registration Information: 90 registration version number: 1 91 registration date: (TBD) 93 Declared registrant of the namespace: 95 Registering organization 96 Name: 98 oneM2M Partnership Project 100 Address: 102 ETSI 103 650, route des Lucioles 104 06921 Sophia-Antipolis Cedex 105 France 107 Designated contact 109 Role: Technical expert 110 Email: miguelangel.reinaortega@etsi.org 112 Declaration of syntactic structure 114 The Namespace Specific String (NSS) of all URNs that use the 115 "1m2m" NID will have the following structure: 117 urn:1m2m:{onem2m-urn} 119 where the "onem2m-urn" is a US-ASCII string that conforms to the 120 NSS(Namespace Specific String) Syntax described in RFC 2141 121 [RFC2141] and defines a specific resource type. 123 Relevant ancillary documentation 125 oneM2M provides information on registration for each URN. More 126 information about oneM2M and the registration activities and 127 procedures to be followed are available at: 129 http://www.onem2m.org/urn 131 Identifier uniqueness considerations 133 oneM2M will manage resources using the "1m2m" NID and will be the 134 authority for managing the "onem2m-urn" strings. In the 135 associated procedures, oneM2M will ensure the uniqueness of the 136 strings themselves or shall permit secondary responsibility for 137 management of well-defined sub-trees. 138 oneM2M may permit use of experimental type values that will not be 139 registered. As a consequence, multiple users may end up using the 140 same value for separate uses. Unregistered type values will only 141 be allowed in sub-namespaces clearly marked as experimental, to 142 help implementers avoid "leaking" experimental values into real 143 use. 145 Identifier persistence considerations 147 oneM2M will provide clear documentation of the registered uses of 148 the "1m2m" NID. This will be structured such that each "onem2m- 149 urn", if needed, will have a separate description and registration 150 table. 151 The registration tables and information will be published and 152 maintained by oneM2M on its web site. 154 Process of identifier assignment 156 oneM2M will provide procedures for registration of each type of 157 resource that it maintains. Each such resource may have three 158 types of registration activities: 160 1. Registered values associated with oneM2M specifications or 161 services 162 2. Registration of values or sub-trees to other entities 163 3. Name models for use in experimental purposes 165 New Namespace Identifier (NID) labels 167 The Entries in the registration table will be the following: 168 onem2m-urn: the registered value; Description: description of the 169 registered value; Reference: oneM2M Technical Specification that 170 defines the value; Contact: person requesting the URN assignment. 172 Process for identifier resolution 174 The namespace is not listed with a Resolution Discovery System 175 (RDS), as this is not relevant. 177 Rules for Lexical Equivalence 179 No special considerations; the rules for lexical equivalence of 180 RFC 2141 [RFC2141] apply. 182 Conformance with URN Syntax 184 No special considerations. 186 Validation mechanism 188 None specified. URN assignment will be handled by procedures 189 supported and maintained by oneM2M. 191 Scope 193 Global 195 3. Examples 197 The following examples are representative URNs that could be assigned 198 by oneM2M. They are not actual strings that are assigned. 200 urn:1m2m:pro 202 Defines the "onem2m-urn" to be used for "pro(tocol)" WG. 204 urn:1m2m:model:sensor-a 206 Defines the URN associated with the information model for some 207 types of sensor devices identified by the name "sensor-a". 209 4. Namespace considerations 211 The oneM2M Partnership Project is developing technical specifications 212 and reports to ensure M2M(Machine-to-Machine) devices can 213 successfully communicate on a global scale. 215 For proper operation, descriptions of the needed information must 216 exist for the URNs and be available in a unique, reliable, and 217 persistent manner. 219 As oneM2M covers multiple technical areas, the possibility of binding 220 to various other namespace repositories has been deemed impractical. 221 Each object or description, as defined in oneM2M, could possibly be 222 related to multiple different other namespaces, so further conflicts 223 of association could occur. Thus the intent is to utilize the oneM2M 224 Secretariat as the naming authority for oneM2M-defined URNs and its 225 descriptions. 227 5. Comunity considerations 229 The objects and descriptions produced by oneM2M are generally 230 available for use by other organizations. The oneM2M will provide 231 access and support for name requests by these organizations. This 232 support can be enabled in a timely and responsive fashion as new 233 objects and descriptions are produced. 235 6. Security Considerations 237 There are no security considerations other than those normally 238 associated with the use and resolution of URNs in general. 240 7. IANA Considerations 242 This section registers a new URN NID with the registration provided 243 in Section 2. 245 "onem2m-urn" strings are identified by label managed by oneM2M. 246 Thus, creating a new label does not require any IANA action. 248 8. Normative References 250 [RFC2141] Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141, 251 May 1997, . 253 [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, 254 "Uniform Resource Names (URN) Namespace Definition 255 Mechanisms", RFC 3406, DOI 10.17487/RFC3406, October 2002, 256 . 258 Authors' Addresses 260 Shingo Fujimoto (editor) 261 Fujitsu Laboratories LTD 262 Kamikodanaka 4-1-1 263 Nakaharaku, Kawasaki 264 JAPAN 266 Email: shingo_fujimoto@jp.fujitsu.com 268 Peter Niblett 269 IBM United Kingdom Limited 270 PO Box 41, North Harbour 271 Portsmouth , Hampshire PO6 3AU 272 United Kingdom 274 Email: peter_niblett@uk.ibm.com 275 Miguel Angel Reina Ortega (editor) 276 European Telecommunication Standards Institute 277 650 Route des lucioles 278 Sophia Antipolis 06921 279 FRANCE 281 Phone: 0033492944349 282 Email: miguelangel.reinaortega@etsi.org