Internet-Draft submission

idnits 2.14.01 

/a/www/www6s/staging/draft-fujimoto-urn-onem2m-00.txt:

  Showing Errors (**), Flaws (~~), Warnings (==), and Comments (--).
  Errors MUST be fixed before draft submission.  Flaws SHOULD be fixed before draft submission.

  Checking boilerplate required by RFC 5378 and the IETF Trust (see
  http://trustee.ietf.org/license-info):
  ----------------------------------------------------------------------------

     No issues found here.

  Checking nits according to http://www.ietf.org/id-info/1id-guidelines.txt:
  ----------------------------------------------------------------------------

  ** The document seems to lack a 1id_guidelines paragraph about 6 months
     document validity. 

     1id_guidelines, paragraph 2:
        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."

  ** The document seems to lack a 1id_guidelines paragraph about the list of
     current Internet-Drafts. 

     1id_guidelines, paragraph 3:
        The list of current Internet-Drafts can be accessed at
        http://www.ietf.org/1id-abstracts.html

  ** The document seems to lack a 1id_guidelines paragraph about the list of
     Shadow Directories. 

     1id_guidelines, paragraph 4:
        The list of Internet-Draft Shadow Directories can be accessed at
        http://www.ietf.org/shadow.html

  == No 'Intended status' indicated for this document; assuming Proposed
     Standard


  Running in submission checking mode -- *not* checking nits according to
  http://www.ietf.org/id-info/checklist .
  ----------------------------------------------------------------------------


     Summary: 3 errors (**), 0 flaws (~~), 1 warning (==), 0 comments (--).

Network Working Group

Internet Draft
S.Fujimoto
Document: draft-fujimoto-urn-onem2m-00.txt
FUJITSU
Expires: December 2016
P.Niblett

IBM



October 2016


A Uniform Resource Name (URN) Namespace
for the oneM2M Partnership Project (oneM2M)


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 memo provides information for the Internet community. It does not specify an Internet standard of any king. Distribution of this memo is unlimited.

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), its areas, and its working groups.  Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts can be accessed at        http://www.ietf.org/1id-abstracts.html. The list of Internet-Draft Shadow Directories can be accessed at       http://www.ietf.org/shadow.html.

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.

Copyright Notice

Copyright (c) 2016 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
(http://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
2. URN Specification for the oneM2M Namespace Identifier (NID)	2
3. Examples	5
4. Namespace Considerations	6
5. Community Considerations	6
6. Security Considerations	67. IANA Considerations	6
8. References	8
9. Author's Addresses	8


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:

	1m2m

Registration Information:

   registration version number: 1
   registration date:           (TBD)

   Declared registrant of the namespace:

      Registering organization
           Name:    oneM2M Partnership Project

         Address: ETSI
                  650, route des Lucioles
                  06921 Sophia-Antipolis Cedex
                  France

      Designated contact
         Role:    Technical expert
         Email:   miguelangel.reinaortega@etsi.org




   Declaration of syntactic structure:

      The Namespace Specific String (NSS) of all URNs that use the "1m2m" NID will have the following structure:

            urn:1m2m:{onem2m-urn}

      where the "onem2m-urn" is a US-ASCII string that conforms to the NSS(Namespace Specific String) Syntax described in RFC 2141 [RFC2141] and defines a specific resource type.

   Relevant ancillary documentation:

      oneM2M provides information on registration for each URN. More      information about oneM2M and the registration activities and procedures to be followed are available at:

      http://www.onem2m.org/urn
   Identifier uniqueness considerations:

      oneM2M will manage resources using the "1m2m" NID and will be the authority for managing the "onem2m-urn" strings. In the associated procedures, oneM2M will ensure the uniqueness of the strings themselves or shall permit secondary responsibility for management of well-defined sub-trees.