Network Working Group                                    M. Jethanandani
Internet-Draft                                        Cisco Systems, Inc
Intended status: Standards Track                        October 17, 2015
Expires: April 19, 2016

                    URN Namespace for MEF Documents


   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.

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

   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 April 19, 2016.

Copyright Notice

   Copyright (c) 2015 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
   ( 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

Jethanandani             Expires April 19, 2016                 [Page 1]

Internet-Draft              Namespace for MEF               October 2015

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

1.  Introduction

   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.

   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) URN Syntax
   [RFC2141] Namespace Identifier (NID) for use by MEF is being
   specified in this document, in full conformance with the NID
   registration process specified in URN Namespace Definition Mechanism

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   document are to be interpreted as described in Key words for use in
   RFCs to Indicate Requirement Levels [RFC2119].

1.1.  Terminology

               | Acronym | Meaning                        |
               | CE      | Carrier Ethernet               |
               |         |                                |
               | MANN    | MEF Assigned Names and Numbers |
               |         |                                |
               | MEF     | MEF Forum                      |
               |         |                                |
               | NID     | Namespace Identifier           |
               |         |                                |
               | NSS     | Namespace Specific String      |
               |         |                                |
               | RDS     | Resolution Discovery System    |
               |         |                                |
               | URN     | Uniform Resource Name          |

Jethanandani             Expires April 19, 2016                 [Page 2]

Internet-Draft              Namespace for MEF               October 2015

2.  URN Specification for MEF

   Namespace ID:


   Registration information:

      registration version number: 1

      registration date: 2015-10-17

   Declared registrant of the namespace:

      Registering organization

         Name: MEF Forum

         Address: 6033 W.  Century Boulevard, Suite 1107 Los Angeles CA
         90045 USA

      Designated contact:

         Role: Manager, MEF Namespace


   Declaration of syntactic structure:

      The Namespace Specific String (NSS) of all URNs that use the MEF
      NID will be maintained by MEF Assigned Names and Numbers (MANN)

   Relevant ancillary documentation:

      MEF publishes information regarding the registered resources in
      the MEF Assigned Names and Numbers (MANN) registry.

   Identifier uniqueness considerations:

      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

Jethanandani             Expires April 19, 2016                 [Page 3]

Internet-Draft              Namespace for MEF               October 2015

      strings themselves, or it may permit secondary responsibility for
      certain defined resources.

      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.

   Identifier persistence considerations:

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

   Process of identifier assignment:

      Assignment of a URN from the MEF namespace will be documented as
      part of the MEF Assigned Names and Numbers (MANN) registry.

   Process of identifier resolution:

      The namespace is not listed with an Resolution Discovery System
      (RDS).  Therefore this process is not relevant.

   Rules for Lexical Equivalence:

      The entire URN is case-insensitive.

   Conformance with URN Syntax:

      No special considerations

   Validation mechanism:

      None specified.  URN assignment will be handled by procedures
      implemented in support of MEF activities.



3.  Examples

   The following are examples of URNs that a resolver for this namespace
   can resolve:



Jethanandani             Expires April 19, 2016                 [Page 4]

Internet-Draft              Namespace for MEF               October 2015

4.  Security Considerations

   There are no additional security considerations other than those
   normally associated with the use and resolution of URNs in general,
   which are described in Function Requirements for URN [RFC1737], URN
   Syntax [RFC2141], and URN Namespace Definition Mechanism [RFC3406].

5.  IANA Considerations

   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 ( and any associated

6.  References

6.1.  Normative References

   [RFC1737]  Sollins, K. and L. Masinter, "Functional Requirements for
              Uniform Resource Names", RFC 1737, DOI 10.17487/RFC1737,
              December 1994, <>.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,

   [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", BCP 66, RFC 3406, DOI 10.17487/RFC3406,
              October 2002, <>.

   [RFC6020]  Bjorklund, M., Ed., "YANG - A Data Modeling Language for
              the Network Configuration Protocol (NETCONF)", RFC 6020,
              DOI 10.17487/RFC6020, October 2010,

6.2.  Informative References

   [RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", BCP 26, RFC 5226,
              DOI 10.17487/RFC5226, May 2008,

Jethanandani             Expires April 19, 2016                 [Page 5]

Internet-Draft              Namespace for MEF               October 2015

Author's Address

   Mahesh Jethanandani
   Cisco Systems, Inc
   180 W. Tasman Drive
   San Jose, CA  95134

   Phone: 408.526.8763

Jethanandani             Expires April 19, 2016                 [Page 6]