<?xml version="1.0"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc subcompact="yes"?>
<rfc category="info" ipr="trust200902" docName="draft-reinaortega-urn-onem2m">
<front>
    <title abbrev="Namespace for oneM2M">
        A Uniform Resource Name (URN) Namespace for the oneM2M Partnership Project (oneM2M)
    </title>
    <author initials="PN" surname="Niblett" fullname="Peter Niblett" >
        <organization>IBM United Kingdom Limited</organization>
        <address>
            <postal>
                <street>PO Box 41, North Harbour</street>
                <city>Portsmouth </city>
                <region>Hampshire</region>
                <code>PO6 3AU</code>
                <country>United Kingdom</country>
            </postal>
            <phone></phone>
            <email>peter_niblett@uk.ibm.com</email>
        </address>
    </author>
	<author initials="AKR" surname="Kraft" fullname="Andreas Kraft">
        <organization>Deutsche Telekom AG</organization>
        <address>
            <postal>
                <street>Holzhauser Straße 4-8</street>
                <city>Berlin</city>
                <region></region>
                <code>13509</code>
                <country>GERMANY</country>
            </postal>
            <phone></phone>
            <email>a.kraft@telekom.de</email>
        </address>
    </author>
	<author initials="MRO" surname="Reina Ortega" fullname="Miguel Angel Reina Ortega" role="editor">
        <organization>European Telecommunication Standards Institute</organization>
        <address>
            <postal>
                <street>650 Route des lucioles</street>
                <city>Sophia Antipolis</city>
                <region></region>
                <code>06921</code>
                <country>FRANCE</country>
            </postal>
            <phone>0033492944349</phone>
            <email>miguelangel.reinaortega@etsi.org</email>
        </address>
    </author>
    <date/>
    <area>Internet Area</area>
    <workgroup>Network Working Group</workgroup>
    <keyword>Draft</keyword>
    <abstract>
        <t>
            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.
        </t>
    </abstract>
</front>
<middle>
    <section title="Introduction">
        <t>
            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.
		</t>
		<t>
			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 <xref target="RFC8141">Uniform Resource 
			Names (URNs)</xref> 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.
        </t>
		<section title="Terminology">
        <texttable>
          <ttcol>Acronym</ttcol>

          <ttcol>Meaning</ttcol>

          <c>ETSI</c>

          <c>European Telecommunications Standards Institute</c>

          <c>NID</c>

          <c>Namespace Identifier</c>

          <c>NSS</c>

          <c>Namespace Specific String</c>

          <c>RDS</c>

          <c>Resolution Discovery System</c>

          <c>URI</c>

          <c>Uniform Resouce Identifier</c>

          <c>URN</c>

          <c>Uniform Resource Name</c>
        </texttable>
      </section>
    </section>
    </section>
	
	    <section title="URN Specification for the oneM2M Namespace Identifier (NID)">
      <t>Namespace Identifier:</t>

      <t><list>
          <t>onem2m</t>
        </list></t>

      <t>Version:</t>

      <t><list>
          <t>1</t>
        </list></t>

      <t>Date:</t>

      <t><list>
          <t>2022-02-21</t>
        </list></t>

      <t>Registrant:</t>

      <t><list>
          <t>Name:</t>

         <t>oneM2M Partnership Project</t>

      <t>Address:</t>

         <t>ETSI</t>
         <t>650, route des Lucioles</t>
         <t>06921 Sophia-Antipolis Cedex</t>
         <t>France</t>

      <t>Designated contact</t>

         <t>Role: oneM2M Secretariat</t>
         <t>Email: onem2m_contact@list.onem2m.org</t>
        </list></t>

      <t>Purpose:</t>

      <t>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.</t>

      <t>Syntax:</t>

      <t><list>
          <t>The syntax of namespace specific strings for the 'onem2m' namespace
			is &lt;NSS&gt; in <xref target="RFC8141">Uniform Resource Names
			(URNs)</xref>.</t>
        </list></t>

      <t>The entire URN is case-insensitive.</t>

      <t>Assignment:</t>

      <t><list>
          <t>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 &lt;NSS&gt;, how the namespaces will be allocated,
			and how experimental namespaces can be used within the allocated
			URN.</t>

          <t>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.</t>

          <t>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 <xref target="RFC6963">A
          Uniform Resource Name (URN) Namespace for Examples</xref>.</t>
        </list></t>

      <t>Interoperability:</t>

      <t>There are no known interoperability issues at this time.</t>

      <t>Resolution:</t>

      <t><list>
          <t>It is not foreseen that URNs within this namespace will undergo
          resolution.</t>
        </list></t>

      <t>Documentation:</t>

      <t><list>
          <t>Documentation can be found at
			https://wiki.onem2m.org/index.php?title=OneM2M_URN_Namespace.</t>
        </list></t>
    </section>
	
	<section title="Examples">
      <t>The following examples are representative URNs that could be assigned
		by oneM2M.  They are not actual strings that are assigned.</t>

      <t><list>
          <t>urn:onem2m:sds</t>

          <t>Defines the "onem2m-urn" to be used for oneM2M SDS WG.</t>

          <t>urn:onem2m:model:sensor-a</t>
		  
		  <t>Defines the URN associated with the information model for some
         types of sensor devices identified by the name "sensor-a".</t>
        </list></t>

    </section>

    <section title="Security considerations">
        <t>
			There are no additional security considerations that are normally
			associated with the use and resolution of URNs in general, which are
			described in <xref target="RFC1737">Function Requirements for
			URN</xref>, <xref target="RFC8141">Uniform Resource Names (URNs)
			</xref>.
        </t>
    </section>
	<section anchor="IANA" title="IANA Considerations">
        <t>
			IANA is requested to register the formal URN namespace "onem2m"
			using the template given above in Section 2.
        </t>
    </section>
	
</middle>
<back>
    <references title="Normative References">
      <?rfc include='reference.RFC.1737'?>

      <?rfc include='reference.RFC.6963'?>

      <?rfc include='reference.RFC.8141'?>

      <?rfc ?>
    </references>
</back>
</rfc>
