Network Working Group S. Fujimoto, Ed.
Internet-Draft Fujitsu Laboratories LTD
Intended status: Standards Track P. Niblett
Expires: September 14, 2018 IBM United Kingdom Limited
S. Reina Ortega, Ed.
European Telecommunication Standards Institute
March 13, 2018

A Uniform Resource Name (URN) Namespace for the oneM2M Partnership Project (oneM2M)
draft-id-fujimoto-urn-onem2m-01

Abstract

This document describes the Namespace Identifier (NID) for Uniform Resource Namespace (URN) resources published by the oneM2M Partnership Project (oneM2M). oneM2M defines and manages resources that utilize this URN name model. Management activities for these and other resource types are provided 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 September 14, 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 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

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 URN namespaces that are managed so that they are unique and persistent. To assure that the uniqueness is absolute, the registration of a specific NID for use by oneM2m was deemed appropriate. Therefore, a full and complete registration will follow the namespace specification process as defined in RFC 3406 [RFC3406].

2. URN Specification for the oneM2M Namespace Identifier (NID)

Namespace ID:

Registration Information:

Declared registrant of the namespace:

Declaration of syntactic structure

Relevant ancillary documentation

Identifier uniqueness considerations

Identifier persistence considerations

Process of identifier assignment

New Namespace Identifier (NID) labels

Process for identifier resolution

Rules for Lexical Equivalence

Conformance with URN Syntax

Validation mechanism

Scope

3. Examples

The following examples are representative URNs that could be assigned by oneM2M. They are not actual strings that are assigned.

4. Namespace considerations

The oneM2M Partnership Project is developing technical specifications and reports to ensure M2M(Machine-to-Machine) devices can successfully communicate on a global scale.

For proper operation, descriptions of the needed information must exist for the URNs and be available in a unique, reliable, and persistent manner.

As oneM2M covers multiple technical areas, the possibility of binding to various other namespace repositories has been deemed impractical. Each object or description, as defined in oneM2M, could possibly be related to multiple different other namespaces, so further conflicts of association could occur. Thus the intent is to utilize the oneM2M Secretariat as the naming authority for oneM2M-defined URNs and its descriptions.

5. Comunity considerations

The objects and descriptions produced by oneM2M are generally available for use by other organizations. The oneM2M will provide access and support for name requests by these organizations. This support can be enabled in a timely and responsive fashion as new objects and descriptions are produced.

6. Security Considerations

There are no security considerations other than those normally associated with the use and resolution of URNs in general.

7. IANA Considerations

This section registers a new URN NID with the registration provided in Section 2.

"onem2m-urn" strings are identified by label managed by oneM2M. Thus, creating a new label does not require any IANA action.

8. Normative References

[RFC2141] Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141, May 1997.
[RFC3406] Daigle, L., van Gulik, D., Iannella, R. and P. Faltstrom, "Uniform Resource Names (URN) Namespace Definition Mechanisms", RFC 3406, DOI 10.17487/RFC3406, October 2002.

Authors' Addresses

Shingo Fujimoto (editor) Fujitsu Laboratories LTD Kamikodanaka 4-1-1 Nakaharaku, Kawasaki JAPAN EMail: shingo_fujimoto@jp.fujitsu.com
Peter Niblett IBM United Kingdom Limited PO Box 41, North Harbour Portsmouth , Hampshire PO6 3AU United Kingdom EMail: peter_niblett@uk.ibm.com
Miguel Angel Reina Ortega (editor) European Telecommunication Standards Institute 650 Route des lucioles Sophia Antipolis, 06921 FRANCE Phone: 0033492944349 EMail: miguelangel.reinaortega@etsi.org