idnits 2.17.1 draft-fujimoto-urn-onem2m-00.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: ---------------------------------------------------------------------------- == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 2) being 309 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 2 pages 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 (October 2016) is 2743 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 3406 (Obsoleted by RFC 8141) ** Obsolete normative reference: RFC 2141 (Obsoleted by RFC 8141) Summary: 2 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group 4 Internet-Draft 5 Intended status: Proposed standard 6 S.Fujimoto 7 Document: draft-fujimoto-urn-onem2m-00.txt 8 FUJITSU 9 Expires: December 2016 10 P.Niblett 12 IBM 14 October 2016 16 A Uniform Resource Name (URN) Namespace 17 for the oneM2M Partnership Project (oneM2M) 19 Abstract 21 This document describes the Namespace Identifier (NID) for Uniform 22 Resource Namespace (URN) resources published by the oneM2M Partnership 23 Project (oneM2M). oneM2M defines and manages resources that utilize 24 this URN name model. Management activities for these and other 25 resource types are provided by the oneM2M Secretariat. 27 Status of this Memo 29 This memo provides information for the Internet community. It does not 30 specify an Internet standard of any king. Distribution of this memo is 31 unlimited. 33 This Internet-Draft is submitted in full conformance with the 34 provisions of BCP 78 and BCP 79. 36 Internet-Drafts are working documents of the Internet Engineering Task 37 Force (IETF), its areas, and its working groups. Note that other groups 38 may also distribute working documents as Internet-Drafts. 40 The list of current Internet-Drafts can be accessed at 41 http://www.ietf.org/1id-abstracts.html. 43 The list of Internet-Draft Shadow Directories can be accessed at 44 http://www.ietf.org/shadow.html. 46 Internet-Drafts are draft documents valid for a maximum of six months 47 and may be updated, replaced, or obsoleted by other documents at any 48 time. It is inappropriate to use Internet-Drafts as reference material 49 or to cite them other than as "work in progress." 51 Copyright Notice 53 Copyright (c) 2016 IETF Trust and the persons identified as the 54 document authors. All rights reserved. 56 This document is subject to BCP 78 and the IETF Trust's Legal 57 Provisions Relating to IETF Documents 58 (http://trustee.ietf.org/license-info) in effect on the date of 59 publication of this document. Please review these documents 60 carefully, as they describe your rights and restrictions with 61 respect to this document. Code Components extracted from this document 62 must include Simplified BSD License text as described in Section 4.e of 63 the rust Legal Provisions and are provided without warranty as described 64 in the Simplified BSD License. 66 Table of Contents 68 1. Introduction 2 69 2. URN Specification for the oneM2M Namespace Identifier (NID) 2 70 3. Examples 5 71 4. Namespace Considerations 6 72 5. Community Considerations 6 73 6. Security Considerations 6 74 7. IANA Considerations 6 75 8. References 8 76 9. Author's Addresses 8 78 1. Introduction 80 oneM2M is the global standards initiative that covers requirements, 81 architecture, API specifications, security solutions and 82 interoperability for Machine-to-Machine(M2M) and IoT technologies. 83 This activity is supported by a membership composed of network 84 operators, equipment vendors, and other suppliers to the M2M/IoT market. 86 Some of the technologies being developed by oneM2M need URN namespaces 87 that are managed so that they are unique and persistent. To assure that 88 the uniqueness is absolute, the registration of a specific NID for use 89 by oneM2m was deemed appropriate. Therefore, a full and complete 90 registration will follow the namespace specification process as defined 91 in RFC 3406 [RFC3406]. 93 2. URN Specification for the oneM2M Namespace Identifier (NID) 95 Namespace ID: 97 1m2m 99 Registration Information: 101 registration version number: 1 102 registration date: (TBD) 104 Declared registrant of the namespace: 106 Registering organization 107 Name: oneM2M Partnership Project 109 Address: ETSI 110 650, route des Lucioles 111 06921 Sophia-Antipolis Cedex 112 France 114 Designated contact 115 Role: Technical expert 116 Email: miguelangel.reinaortega@etsi.org 118 Declaration of syntactic structure: 120 The Namespace Specific String (NSS) of all URNs that use the "1m2m" 121 NID will have the following structure: 123 urn:1m2m:{onem2m-urn} 125 where the "onem2m-urn" is a US-ASCII string that conforms to the 126 NSS(Namespace Specific String) Syntax described in RFC 2141 [RFC2141] 127 and defines a specific resource type. 129 Relevant ancillary documentation: 131 oneM2M provides information on registration for each URN. More 132 information about oneM2M and the registration activities and procedures 133 to be followed are available at: 135 http://www.onem2m.org/urn 136 Identifier uniqueness considerations: 138 oneM2M will manage resources using the "1m2m" NID and will be the 139 authority for managing the "onem2m-urn" strings. In the associated 140 procedures, oneM2M will ensure the uniqueness of the strings themselves 141 or shall permit secondary responsibility for management of well-defined 142 sub-trees. 144 oneM2M may permit use of experimental type values that will not be 145 registered. As a consequence, multiple users may end up using the 146 same value for separate uses. Unregistered type values will only be 147 allowed in sub-namespaces clearly marked as experimental, to 148 help implementers avoid "leaking" experimental values into real use. 150 Identifier persistence considerations: 152 oneM2M will provide clear documentation of the registered uses of 153 the "1m2m" NID. This will be structured such that each "onem2m-urn", if 154 needed, will have a separate description and registration table. 156 The registration tables and information will be published and 157 maintained by oneM2M on its web site. 159 Process of identifier assignment: 161 oneM2M will provide procedures for registration of each type of 162 resource that it maintains. Each such resource may have three types of 163 registration activities: 165 1. Registered values associated with oneM2M specifications or 166 services 168 2. Registration of values or sub-trees to other entities 170 3. Name models for use in experimental purposes 172 New Namespace Identifier (NID) labels 174 The Entries in the registration table will be the following: 176 onem2m-urn: the registered value; 177 Description: description of the registered value; 178 Reference: oneM2M Technical Specification that defines the 179 value; 180 Contact: person requesting the URN assignment. 182 Process for identifier resolution: 184 The namespace is not listed with a Resolution Discovery System 185 (RDS), as this is not relevant. 187 Rules for Lexical Equivalence: 189 No special considerations; the rules for lexical equivalence of 190 RFC 2141 [RFC2141] apply. 192 Conformance with URN Syntax: 194 No special considerations. 196 Validation mechanism: 198 None specified. URN assignment will be handled by procedures 199 supported and maintained by oneM2M. 201 Scope: 203 Global 205 3. Examples 207 The following examples are representative URNs that could be assigned by 208 oneM2M. They are not actual strings that are assigned. 210 urn:1m2m:pro 212 Defines the "onem2m-urn" to be used for "pro(tocol)" WG. 214 urn:1m2m:model:sensor-a 216 Defines the URN associated with the information model for some 217 types of sensor devices identified by the name "sensor-a". 219 4. Namespace Considerations 221 The oneM2M Partnership Project is developing technical specifications 222 and reports to ensure M2M(Machine-to-Machine) devices can successfully 223 communicate on a global scale. 225 For proper operation, descriptions of the needed information must exist 226 for the URNs and be available in a unique, reliable, and persistent 227 manner. 229 As oneM2M covers multiple technical areas, the possibility of binding to 230 various other namespace repositories has been deemed impractical. Each 231 object or description, as defined in oneM2M, could possibly be related 232 to multiple different other namespaces, so further conflicts of 233 association could occur. Thus the intent is to utilize the oneM2M 234 Secretariat as the naming authority for oneM2M-defined URNs and its 235 descriptions. 237 5. Community Considerations 239 The objects and descriptions produced by oneM2M are generally available 240 for use by other organizations. The oneM2M will provide access and 241 support for name requests by these organizations. This support can be 242 enabled in a timely and responsive fashion as new objects and 243 descriptions are produced. 245 6. Security Considerations 247 There are no security considerations other than those normally 248 associated with the use and resolution of URNs in general. 250 7. IANA Considerations 252 This section registers a new URN NID with the registration provided in 253 Section 2. 255 "onem2m-urn" strings are identified by label managed by oneM2M. Thus, 256 creating a new label does not require any IANA action. 258 8. References 260 Normative 262 [RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, 263 "Uniform Resource Names (URN) Namespace Definition 264 Mechanisms", BCP 66, RFC 3406, October 2002. 266 [RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997. 268 9. Author's Addresses 270 Shingo Fujimoto 271 FUJITSU LABORATORIES LTD. 272 Kamikodanaka 4-1-1, Nakaharaku, Kawasaki 273 JAPAN 274 Email: shingo_fujimoto@jp.fujitsu.com 276 Peter Niblett 277 UK Head Office 278 IBM United Kingdom Limited 279 PO Box 41, North Harbour 280 Portsmouth 281 Hampshire, PO6 3AU 282 Email: peter_niblett@uk.ibm.com 284 URN namespace for oneM2M