7818
INFORMATIONAL
URN Namespace for MEF Documents
Authors: M. Jethanandani
Date: March 2016
Working Group: NON WORKING GROUP
Stream: IETF
Abstract
This document describes the Namespace Identifier (NID) "mef" for Uniform Resource Names (URNs) used to identify resources published by MEF Forum (https://www.mef.net). 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.
RFC 7818
INFORMATIONAL
Internet Engineering Task Force (IETF) M. Jethanandani
Request for Comments: 7818 Cisco Systems, Inc
Category: Informational March 2016
ISSN: 2070-1721
<span class="h1">URN Namespace for MEF Documents</span>
Abstract
This document describes the Namespace Identifier (NID) "mef" for
Uniform Resource Names (URNs) used to identify resources published by
MEF Forum (<a href="https://www.mef.net">https://www.mef.net</a>). 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 document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="https://www.rfc-editor.org/info/rfc7818">http://www.rfc-editor.org/info/rfc7818</a>.
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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.
<span class="grey">Jethanandani Informational [Page 1]</span><span id="page-2" ></span>
<span class="grey"><a href="./rfc7818">RFC 7818</a> Namespace for MEF March 2016</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-1.1">1.1</a>. Terminology . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
<a href="#section-2">2</a>. URN Specification for MEF . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
<a href="#section-3">3</a>. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-4">4</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-5">5</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-6">6</a>. Normative References . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
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
areas of Services, Architecture, and 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 URN Syntax [<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>] Namespace Identifier
(NID) for use by MEF is being specified in this document.
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Terminology</span>
+---------+--------------------------------+
| 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 |
+---------+--------------------------------+
<span class="grey">Jethanandani Informational [Page 2]</span><span id="page-3" ></span>
<span class="grey"><a href="./rfc7818">RFC 7818</a> Namespace for MEF March 2016</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. URN Specification for MEF</span>
Namespace ID:
mef
Registration information:
registration version number: 1
registration date: 2016-02-08
Declared registrant of the namespace:
Registering organization
Name: MEF Forum
Address: 6033 W. Century Boulevard, Suite 1107
Los Angeles, CA 90045
United States
Designated contact:
Role: Manager, MEF Namespace
Email: [email protected]
Declaration of syntactic structure:
The syntax of namespace-specific strings for the "mef" namespace
is <NSS> in <a href="./rfc2141">RFC 2141</a>.
Relevant ancillary documentation:
MEF publishes information regarding the registered resources in
the MEF Assigned Names and Numbers (MANN) registry
(<a href="https://www.mef.net/MANN">https://www.mef.net/MANN</a>).
<span class="grey">Jethanandani Informational [Page 3]</span><span id="page-4" ></span>
<span class="grey"><a href="./rfc7818">RFC 7818</a> Namespace for MEF March 2016</span>
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
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
collisions as multiple users may use the same values for different
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 a 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.
Scope:
Global
<span class="grey">Jethanandani Informational [Page 4]</span><span id="page-5" ></span>
<span class="grey"><a href="./rfc7818">RFC 7818</a> Namespace for MEF March 2016</span>
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Examples</span>
The following are examples of URNs that MEF is looking to assign:
urn:mef:yang:mef-services
urn:mef:yang:mef-interfaces
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
There are no security considerations other than those normally
associated with the use and resolution of URNs in general, which are
described in "Function Requirements for Uniform Resource Names"
[<a href="./rfc1737" title=""Functional Requirements for Uniform Resource Names"">RFC1737</a>] and "URN Syntax" [<a href="./rfc2141" title=""URN Syntax"">RFC2141</a>].
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
Per this document, IANA has added a new entry ("mef") in the "Uniform
Resource Names (URN) Namespaces" registry available from the IANA
site (<a href="https://www.iana.org">https://www.iana.org</a>).
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Normative References</span>
[<a id="ref-RFC1737">RFC1737</a>] Sollins, K. and L. Masinter, "Functional Requirements for
Uniform Resource Names", <a href="./rfc1737">RFC 1737</a>, DOI 10.17487/RFC1737,
December 1994, <<a href="https://www.rfc-editor.org/info/rfc1737">http://www.rfc-editor.org/info/rfc1737</a>>.
[<a id="ref-RFC2141">RFC2141</a>] Moats, R., "URN Syntax", <a href="./rfc2141">RFC 2141</a>, DOI 10.17487/RFC2141,
May 1997, <<a href="https://www.rfc-editor.org/info/rfc2141">http://www.rfc-editor.org/info/rfc2141</a>>.
Author's Address
Mahesh Jethanandani
Cisco Systems, Inc
170 W. Tasman Drive
San Jose, CA 95134
United States
Phone: +1 408.526.8763
Email: [email protected]
Jethanandani Informational [Page 5]
Annotations
Select text to annotate