Network Working Group M. Jethanandani
Internet-Draft Cisco Systems, Inc
Intended status: Informational February 3, 2016
Expires: August 6, 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 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 August 6, 2016.

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 ( 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.

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.

1.1. Terminology

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

2. URN Specification for MEF

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:

Process of identifier resolution:

Rules for Lexical Equivalence:

Conformance with URN Syntax:

Validation mechanism:


3. Examples

The following are examples of URNs that MEF is looking to assign:

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].

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 mirrors.

6. Normative References

[RFC1737] Sollins, K. and L. Masinter, "Functional Requirements for Uniform Resource Names", RFC 1737, DOI 10.17487/RFC1737, December 1994.
[RFC2141] Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141, May 1997.

Author's Address

Mahesh Jethanandani Cisco Systems, Inc 180 W. Tasman Drive San Jose, CA 95134 USA Phone: +1 408.526.8763 EMail:

Table of Contents