One document matched: draft-mahesh-mef-urn-00.xml

<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="no"?>
<?rfc tocompact="no"?>
<?rfc tocdepth="6"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<rfc category="std" docName="draft-mahesh-mef-urn-00" ipr="trust200902">
  <front>
    <title abbrev="Namespace for MEF">URN Namespace for MEF Documents</title>

    <author fullname="Mahesh Jethanandani" initials="M.J."
            surname="Jethanandani">
      <organization>Cisco Systems, Inc</organization>

      <address>
        <postal>
          <street>180 W. Tasman Drive</street>

          <city>San Jose</city>

          <region>CA</region>

          <code>95134</code>

          <country>USA</country>
        </postal>

        <phone>408.526.8763</phone>

        <facsimile/>

        <email>mjethanandani@gmail.com</email>

        <uri/>
      </address>
    </author>

    <date day="17" month="October" year="2015"/>

    <abstract>
      <t>This document describes the Namespace Identifier (NID) 'mef' for
      Uniform Resource Names (URNs) used to identify resources published by
      MEF Forum (MEF). MEF specifies and manages resources that utilize this
      URN identification model. Management activities for these and other
      resources types are handled by the manager of the MEF Assigned Names and
      Numbers (MANN) registry.</t>
    </abstract>
  </front>

  <middle>
    <section title="Introduction">
      <t>The MEF Forum (MEF), is a nonprofit international industry standards
      organization, dedicated to the worldwide adoption of Carrier Ethernet
      (CE) networks and services. The forum creates specifications in the area
      of Services, Architecture, Operations and Management.</t>

      <t>As part of these specifications efforts, there is a 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 Unified Resource Name (URN) <xref target="RFC2141">URN
      Syntax</xref> Namespace Identifier (NID) for use by MEF is being
      specified in this document, in full conformance with the NID
      registration process specified in <xref target="RFC3406">URN Namespace
      Definition Mechanism</xref>.</t>

      <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
      "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
      document are to be interpreted as described in <xref
      target="RFC2119">Key words for use in RFCs to Indicate Requirement
      Levels</xref>.</t>

      <section title="Terminology">
        <texttable>
          <ttcol>Acronym</ttcol>

          <ttcol>Meaning</ttcol>

          <c>CE</c>

          <c>Carrier Ethernet</c>

          <c>MANN</c>

          <c>MEF Assigned Names and Numbers</c>

          <c>MEF</c>

          <c>MEF Forum</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>URN</c>

          <c>Uniform Resource Name</c>
        </texttable>
      </section>
    </section>

    <section title="URN Specification for MEF">
      <t>Namespace ID:</t>

      <t><list>
          <t>mef</t>
        </list></t>

      <t>Registration information:</t>

      <t><list>
          <t>registration version number: 1</t>

          <t>registration date: 2015-10-17</t>
        </list></t>

      <t>Declared registrant of the namespace:</t>

      <t><list>
          <t>Registering organization</t>

          <t><list>
              <t>Name: MEF Forum</t>

              <t>Address: 6033 W. Century Boulevard, Suite 1107 Los Angeles CA
              90045 USA</t>
            </list></t>

          <t>Designated contact:</t>

          <t><list>
              <t>Role: Manager, MEF Namespace</t>

              <t>Email: namespace@mef.net</t>
            </list></t>
        </list></t>

      <t>Declaration of syntactic structure:</t>

      <t><list>
          <t>The Namespace Specific String (NSS) of all URNs that use the MEF
          NID will be maintained by MEF Assigned Names and Numbers (MANN)
          registry.</t>
        </list></t>

      <t>Relevant ancillary documentation:</t>

      <t><list>
          <t>MEF publishes information regarding the registered resources in
          the MEF Assigned Names and Numbers (MANN) registry.</t>
        </list></t>

      <t>Identifier uniqueness considerations:</t>

      <t><list>
          <t>MEF will manage resource classes using the "mef" NID and will be
          the authority for managing resources and associated subsequent
          strings. MEF is expected to guarantee the uniqueness of the strings
          themselves, or it may permit secondary responsibility for certain
          defined resources.</t>

          <t>MEF could allow for use of experimental type values for testing
          purposes only. Note that using experimental types may create
          collision as multiple users may use the same values for resources
          and specific strings.</t>
        </list></t>

      <t>Identifier persistence considerations:</t>

      <t><list>
          <t>MEF will update the MEF Assigned Names and Numbers (MANN)
          registry to document the registered resources that will use the
          "mef" NID.</t>
        </list></t>

      <t>Process of identifier assignment:</t>

      <t><list>
          <t>Assignment of a URN from the MEF namespace will be documented as
          part of the MEF Assigned Names and Numbers (MANN) registry.</t>
        </list>Process of identifier resolution:</t>

      <t><list>
          <t>The namespace is not listed with an Resolution Discovery System
          (RDS). Therefore this process is not relevant.</t>
        </list>Rules for Lexical Equivalence:</t>

      <t><list>
          <t>The entire URN is case-insensitive.</t>
        </list>Conformance with URN Syntax:</t>

      <t><list>
          <t>No special considerations</t>
        </list>Validation mechanism:</t>

      <t><list>
          <t>None specified. URN assignment will be handled by procedures
          implemented in support of MEF activities.</t>
        </list>Scope:</t>

      <t><list>
          <t>Global</t>
        </list></t>

      <t/>

      <t/>

      <t/>
    </section>

    <section title="Examples">
      <t>The following are examples of URNs that a resolver for this namespace
      can resolve:</t>

      <t><list>
          <t>urn:mef:params:xml:ns:yang:mef-services</t>

          <t>urn:mef:params:xml:ns:yang:mef-interfaces</t>
        </list></t>
    </section>

    <section title="Security Considerations">
      <t>There are no additional security considerations other than those
      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="RFC2141">URN Syntax</xref>, and <xref
      target="RFC3406">URN Namespace Definition Mechanism</xref>.</t>
    </section>

    <section anchor="IANA" title="IANA Considerations">
      <t>This document adds a new entry ("mef") in the urn-namespace registry.
      This is the defining document. When published, the entry can be found in
      the "Uniform Resource Names (URN) Namespaces" registry available from
      the IANA site (http://www.iana.org) and any associated mirrors.</t>
    </section>
  </middle>

  <back>
    <references title="Normative References">
      <?rfc include='reference.RFC.2119'?>

      <?rfc include='reference.RFC.1737'?>

      <?rfc include='reference.RFC.2141'?>

      <?rfc include='reference.RFC.3406'?>

      <?rfc include='reference.RFC.6020'?>
    </references>

    <references title="Informative References">
      <?rfc include='reference.RFC.5226'?>
    </references>
  </back>
</rfc>