Panel

bgColor	white

MEF Assigned Names and Numbers (MANN)

Panel
© MEF Forum 20172020. Any reproduction of this document or any portion thereof shall contain the following statement: "Reproduced with permission of MEF Forum." No user of this document is authorized to modify any of the information contained herein.

...

Example use of Namespace

Example Request is for Namespace String: "mef-global". The following figure illustrates where the namespace request is used in the YANG module.

The name of the module "mef-global" is the namespace string being requested.
The full path of the namespace is then specified in line number 2, and it specifies where in the tree the namespace string is going to be used.
A brief description of where the namespace is going to be used is specified in the description section of this module and could be cut and pasted in the request for namespace application.

Numbered Headings

start-numbering-with	1

Terminology

Captioned Item

anchor	#Acronyms
name	Table
caption	Acronyms

Acronym	Description	Reference
Namespace	A collection of uniquely-assigned identifiers. That is, the identifiers are not ever assigned to more than 1 resource, nor are they ever re-assigned to a different resource.	RFC3406
NID	Namespace Identifier Identifier registered with the Internet Assigned Numbers Authority, IANA	RFC 2141
NSS	Namespace Specific Strings Namespace ID determines the _syntactic_ interpretation of the Namespace Specific String	RFC 2141
URI	Uniform Resource Identifier a compact string of characters for identifying an abstract or physical resource classified as a locator, a name, or both	RFC 2396
URN	Uniform Resource Names subset of URI that are required to remain globally unique and persistent even when the resource ceases to exist or becomes unavailable. All URNs have the following syntax (phrases enclosed in quotes are REQUIRED): <URN> ::= "urn:" <NID> ":" <NSS>	RFC 2141 RFC 2396
WCWorking Committee	MEF Working Committees like Technical the Digital Services Committee, Service Operations LSO Committee, Marketing Committee, Certification Committeeetc.	This Document

MEF Forum URN

MEF has registered the NID:mef with IANA as described in RFC X (draft work in progress - see IETF draft MEF URN )7818. This namespace is maintained by MEF Forum for use by the Working Committees (WC) in MEF.

This document lists the Namespaces registered by MEF and the corresponding MEF specifications that contain the modules using the Namespace. Additionally, this document outlines the process to request namespaces for work that is developed by MEF.

NameSpace Specific String Root

Caption Reference

anchor	#NSSroots

lists the Namespace Specific Strings (NSS) Root identified by MEF for use in the URN:

Captioned Item

anchor	#NSSroots
name	Table
caption	NameSpace Specific String Roots

Structure	NSS-Root	urn:NID:NSS-Root	Type	Comments
yang-nss	"yang:"	urn:mef:yang:	string	Branch of tree. This value is present when purpose is for YANG.
xidlso-nss	"xidlso:"	urn:mef:xidlso:	string	Branch of tree. This value is present when purpose is for experimentalOpenAPI Specifications.
otherxid-nss	"<other>xid:"	urn:mef:<other>xid:	string	Branch of tree. This value is present when purpose is for experimental.
other-nss	"<other>:"	urn:mef:<other>:	string	beginning with a beginning with a prefix other than one of those above for future expansion

string = (ALPHA)0*(ALPHANUMERIC/-/_)

i.e., a string that starts with an alphabet (a-z, A-Z) and has 0 or more mix of alphanumeric (a-zA-Z0-9) or hyphen or underscore.

All URNs have the following syntax (phrases enclosed in quotes are REQUIRED):

<URN> ::= "urn":" <NID> ":" <NSS-Root> ": "<NSS-restoftree>"

Note that a NSS includes <NSS-root>:<NSS-restoftree> where the <NSS-restoftree> is the rest of tree that has one or more strings each separated with a colon, ":". Note that the colon, ":", is not allowed in a branch or leaf name.

As example, a URN might be constructed as: urn:mef:foo:bar:baz, where," bar:baz" is the <NSS-restoftree> appended to "foo:" as <NSS-root>.

Contact Information

Addition of a new NSS Root requires that an updated version of this document is approved by a Technical Motion of the relevant MEF Working Committee.

Contact Information

All correspondence related to MEF Namespace should be send to All correspondence related to MEF Namespace should be send to namespace@mef.net.

MEF Assigned URN

Updated: January 2020

Captioned Item

anchor	#Assigned
name	Table
caption	Assigned URN

Advanced Tables - Table Plus

sortDescending	true
columnStyles	border:solid;,1,1,1,1,1
rowStyles	border:solid;,1,
autoNumberSort	true
multiple	false
autoNumber	true
sortIcon	true

URN*	Description	Tentative/Final	Reference (MEF Project/Specification Standard using namespace)	Additional Information(also, work in progress or published)
urn:mef:yang:mef-global	Global Profiles and Lists configured for MEF Services	Legato - EVC Service YANG (Service Configuration & Activation)	in Letter Ballot https://github.com/MEF-GIT/YANG-public		Final	MEF 58
urn:mef:yang:mef-legato-services	Carrier Ethernet Services defined in MEF 10.3 and MEF 6.2	Legato - EVC Service YANG (Service Configuration & Activation)	Final	MEF 58 in Letter Ballot https://github.com/MEF-GIT/YANG-public
urn:mef:yang:mef-legato-interfaces	UNI Functionality defined in MEF 10.3 and MEF 6.2	Legato - EVC Service YANG (Service Configuration & Activation)	Final	MEF 58 in Letter Ballot https://github.com/MEF-GIT/YANG-public
urn:mef:yang:mef-types	Common YANG types and definitions used by MEF.	Legato - EVC Service YANG (Service Configuration & Activation)	in Letter Ballot https://github.com/MEF-GIT/YANG-public	Final	MEF 58

* As of July 2017

Use of MEF Assigned URN

MEF Working Committees develop and publish various work such as Technical Specifications, Implementation Agreements, Test Suites, Best Current Practice documents and software modulesworks as MEF Standards. A list is available at MEF SpecificationsStandards. These include Information and Data Models as well as Interface Profiles for Management Systems. As example, MEF has ongoing published work on YANG Modules for MEF Services. Such work in MEF could use the NSS Prefixes specified in this document.

The NSS chosen by a project have to be unique among all MEF projects. See also Namespace Structure

Other Assigned URN

There are no other assigned URNs (e.g., from namespace belonging to another organization) for use in MEF.

Request for Namespaces

Applications for new NSS, using one of the NSS-Roots (excluding xid-nss) specified in Namespace Specific String Root, must be made via email to namespace@mef.net.

Namespace Application Review

The Application will be reviewed by a group including Co-Chairs of relevant Working Committees in MEF Forum as well as one or more Subject Matter Experts (SME) from Member Companies. There may be 1 or more SMEs assigned for each <NSS-Root>. The SMEs are to be approved in a Procedural Motion approved at of the relevant Working Committee approved at a MEF Quarterly Meeting.

Application Details

Applications for the NSS should be made in the context of an approved MEF project. The request can happen at any time during the life of the project. The application should include the following:

Approved MEF Project Proposal Contribution
<NSS-root>, i.e., Namespace String Root from
Caption Reference
anchor #NSSroots
<NSS-restoftree>. See also Namespace Structure for examples
a brief description of its functionality;
the name and email address of the person making the application; and
any supplementary information considered necessary to support the application.

An example use in a YANG module is provided in ExampleuseofNamespace

Approval requirements: New NSS applications can be approved by the review group as specified above.

Application with Request for New Branches

When a Namespace Request Application includes a request for a new branch under a <NSS-Root>, then the application should include the following:

Approved MEF Project Proposal Contribution
<NSS-root>, i.e., Namespace String Root from
Caption Reference
anchor #NSSroots
New Branch for <NSS-restoftree>. See also Namespace Structure for examples
a brief description of the Branch and the possible leaves under this branch;
a brief description of its functionality;
the name and email address of the person making the application; and,
any supplementary information considered necessary to support the application.

Approval requirements: Applications for new branches can be approved by the review group as specified above, unless specified otherwise under Namespace Structure for the immediately preceding branch or NSS root.

Namespace Lifecycle

Captioned Item

anchor	#NamespaceLifecycle
caption	Namespace Lifecycle
alignment	left

Gliffy Diagram

sizename	LNamespace-structure
namepagePin	Namespace-process1

As shown in

Caption Reference

anchor	#NamespaceLifecycle

, a MEF project may choose NSS but making sure they are not in collision (See Manage Managing Collisions) with any existing (experimental or allocated) values. An application for NSS, with <NSS-root>, excluding value of <xid>, should be made during or after the first CfCB to give enough time for members to comment on the requested namespace.

The NSS is allocated after successful review. The allocation is considered temporary till the document is approved for publication as a MEF SpecificationStandard. The approval of the NSS is conditional on the approval of the Letter Ballot document (that contains the module requesting the namespace). If the document does not get published, the namespace is available for future use.

Namespace Structure

All URNs have the following syntax (phrases enclosed in quotes are REQUIRED):

<URN> ::= "urn":" <NID> ":" <NSS-Root> ": "<NSS-restoftree>"

The number of levels in the tree after "urn:<NID>" is at least 2.

In this version of the document the focus is on the tree trees for yang-nss and lso-nss given the immediate need for use in development of Data Models such as YANG Modules for MEF Services. The trees for other <NSS-Root> are expected to be specified in future versions of this document.

In the current version, a table is used to describe the role of each string in NSS as well as example values for the string. When more description and constraints is needed for each string in the NSS, then the layout of this section might be changed with separate sub-section for each string in the NSS.

yang-nss

Each NSS in yang-nss identifies a specific Yang module in a published MEF Standard.

Caption Reference

anchor	#Structure-paramsyang

and

Caption Reference

anchor	#Structure-yang-figure

below provide explanation of an example hierarchy showing up to 4 additional level although an application may require less or more. Rows highlighted in Yellow indicate that a project team decides on the required values for <NSS-restoftree>. Some examples are included to help understand the use of a string in the NSS.

Captioned Item

anchor	#Structure-paramsyang
name	Table
caption	NSS when <NSS-Root> is paramsyang

Number in

Caption Reference

anchor	#Structure-yang-figure

Level in URN Tree

String

Comments

1

Scheme

"urn"

2

Authority, NID

"mef"

3

Namespaces Specific String Root, NSS-Root

"yang"

Project to choose one of the <NSS-Root> listed in

Caption Reference

displaytext	Table of NameSpace Specific String Roots
anchor	#NSSroots

4

Module Name

e.g., "mef-global:"

other examples could be mef-device-global, mef-controller-global

Namespace Request Application to include suitable string

Captioned Item

anchor	#Structure-yang-figure
caption	Example Namespace Structure

Gliffy Diagram

name	mef-ns-structure

xid-nss

This is available for use as experimental NSS for work that is not published. Note also that namespaces under xid-nss is limited in scope to that work. While IETF has RFC 6963 with a different <NID> for example URNs, MEF is using a method of different <NSS-Root>.

Captioned Item

anchor	#Structure-xid
name	Table
caption	NSS when <NSS-Root> is xid

Number in Structure

Level

Namespace String

Comments

1

Scheme

"urn"

2

Authority, NID

"mef"

3

Namespaces Specific String Root, NSS-Root

"xid"

Project to choose one of the <NSS-Root> listed in

Caption Reference

displaytext	Table of NameSpace Specific String Roots
anchor	#NSSroots

4

This document is not specifying the possible <NSS-restoftree> for this <NSS-Root>

5

<other>-nss

structure1
pagePin	1

lso-nss

Each NSS under "urn:mef:lso:spec" identifies a set of specification schema files for use with MEF LSO APIs, for a specific product or service specification, i.e. the schema file defining the schema for that product or service, plus any further referenced files. The URN identifies the version of the set as a whole, and the specific API function for which the schema can be used. Note that the same version applies to all API functions for a given product or service.

Caption Reference

anchor	#Structure-lso

and

Caption Reference

anchor	#Structure-lso-figure

below provide explanation of an example hierarchy showing 8 levels, although an application may require less or more. Rows highlighted in Yellow indicate that a project team decides on the required values for <NSS-restoftree>. Some examples are included to help understand the use of a string in the NSS.

Captioned Item

anchor	#Structure-lso
name	Table
caption	NSS when <NSS-Root> is lso

Number in

Caption Reference

anchor	#Structure-lso-figure

Level in URN Tree

String

Comments

Captioned Item

anchor	#Structure-other
name	Table
caption	NSS when <NSS-Root> is <other>

Number in Structure

Level

Namespace String

Comments

1

Scheme

"urn"

2

Authority, NID

"mef"

3

Namespaces Specific String Root, NSS-Root

"<other>lso"

Project to choose one of the <NSS-Root> listed in

Caption Reference

displaytext	Table of NameSpace Specific String Roots
anchor	#NSSroots

4

Tree to be specified in future versions of this document

5

An example use of NSS is shown inExampleuseofNamespace for usage of tree structure in a request for 'mef-global'

Managing Collisions

Any Project team may define a given NSS value based on one of the <NSS-Root> before making a Request for Namespace but should be careful to make sure it does not collide with any assigned NSS values listed in

Caption Reference

anchor	#Assigned

. These values should also not be used in a production network and should be used for test purposes only until MEF approves the publication of the work such as Specification or BCP.

Updates to MANN

Section AssignedURN in this document will get updated by one of the Co-Chairs of Working Groups in MEF Forum and can be done during the lifecycle shown in

Caption Reference

anchor	#NamespaceLifecycle

.

In the case of discrepancy between this Wiki page and a published module in a specification then the assigned values is as per published specification.

References

IETF RFC x, https://tools.ietf.org/html/draft-mahesh-mef-urn-01
IETF RFC 2141, URN Syntax , https://www.ietf.org/rfc/rfc2141.txt
IETF RFC 2396,Uniform Resource Identifiers (URI): Generic Syntax, https://www.ietf.org/rfc/rfc2396.txt
IETF RFC 3406, Uniform Resource Names (URN) Namespace Definition Mechanisms, https://tools.ietf.org/html/rfc3406
IETF RFC 6963, A Uniform Resource Name (URN) Namespace for Examples, https://tools.ietf.org/rfc/rfc6963.txt

Numbered Headings

number-format	custom
h1	Appendix [h1.upper-greek]:
h2	Appendix [h1.upper-greek].[h2.decimal]:

Code Block

language	xml
linenumbers	true

...

Branch under "lso"	"spec"	This is the only branch currently defined.
5	LSO Interface Reference Point	<irp>	One of "cantata", "sonata", "sonata-cantata", "allegro", "interlude", "interlude-allegro", "legato", "presto", "adagio".
6	Product or Service Name	e.g., "access-eline:"	Other examples could be "epl:", "subscriber-ethernet-uni:", "evp-lan:", "internet-access:", etc Namespace Request Application to include suitable string
7	Version	e.g. "v1.0.0"	Semantic version number of the corresponding schema. Namespace Request Application to include the appropriate number, which should be incremented according to SemVer 2.0.0. Note that the version applies to the set containing the schema for the product or service named, as well as all other schema objects referenced from it.
8	API Function	e.g. "poq"	Other examples could be "quote", "order", "inventory". If a single schema is use for all functions, the API Function should be "all" Namespace Request Application to include suitable string

New branches beyond those specified above under the "lso:" NSS Root and under "lso:spec" must be approved by a technical motion of the relevant MEF Working Committee. Changes to the structure above must also be approved by a technical motion of the relevant MEF Working Committee. However, the specific branch and leaf names following the structure above, including new branches at levels 6 and higher, can be approved by the review group as specified under Namespace Application Review.

Captioned Item

anchor	#Structure-lso-figure
caption	Example Namespace Structure

Gliffy Diagram

name	mef-oas-ns-structure
pagePin	1

xid-nss

This is available for use as experimental NSS for work that is not published. Note also that namespaces under xid-nss is limited in scope to that work. While IETF has RFC 6963 with a different <NID> for example URNs, MEF is using a method of different <NSS-Root>.

Captioned Item

anchor	#Structure-xid
name	Table
caption	NSS when <NSS-Root> is xid

Number

Level

Namespace String

Comments

1

Scheme

"urn"

2

Authority, NID

"mef"

3

Namespaces Specific String Root, NSS-Root

"xid"

Project to choose one of the <NSS-Root> listed in

Caption Reference

displaytext	Table of NameSpace Specific String Roots
anchor	#NSSroots

4

This document is not specifying the possible <NSS-restoftree> for this <NSS-Root>

5

<other>-nss

Captioned Item

anchor	#Structure-other
name	Table
caption	NSS when <NSS-Root> is <other>

Number

Level

Namespace String

Comments

1

Scheme

"urn"

2

Authority, NID

"mef"

3

Namespaces Specific String Root, NSS-Root

"<other>"

Project to choose one of the <NSS-Root> listed in

Caption Reference

displaytext	Table of NameSpace Specific String Roots
anchor	#NSSroots

4

Tree to be specified in future versions of this document

5

An example use of NSS is shown in ExampleuseofNamespace for usage of tree structure in a request for 'mef-global'

Managing Collisions

Any Project team may define a given NSS value based on one of the <NSS-Root> before making a Request for Namespace but should be careful to make sure it does not collide with any assigned NSS values listed in

Caption Reference

anchor	#Assigned

. These values should also not be used in a production network and should be used for test purposes only until MEF approves the publication of the corresponding MEF Standard.

Updates to MANN

For new NSSs, section AssignedURN in this document will be updated by one of the Co-Chairs of the relevant MEF Working Committees according to the lifecycle shown in

Caption Reference

anchor	#NamespaceLifecycle

.

For new NSS Roots or new branches, section NameSpace Specific String Root or section Namespace Structure (respectively) will be updated by one of the Co-Chairs of the relevant MEF Working Committee once the approval requirements as specified above have been met.

In the case of discrepancy between this Wiki page and a published module in a MEF Standard then the assigned values is as per published MEF Standard.

References

IETF RFC 7818, https://tools.ietf.org/html/rfc7818
IETF RFC 2141, URN Syntax , https://www.ietf.org/rfc/rfc2141.txt
IETF RFC 2396,Uniform Resource Identifiers (URI): Generic Syntax, https://www.ietf.org/rfc/rfc2396.txt
IETF RFC 3406, Uniform Resource Names (URN) Namespace Definition Mechanisms, https://tools.ietf.org/html/rfc3406
IETF RFC 6963, A Uniform Resource Name (URN) Namespace for Examples, https://tools.ietf.org/rfc/rfc6963.txt

Numbered Headings

number-format	custom
h1	Appendix [h1.upper-greek]:
h2	Appendix [h1.upper-greek].[h2.decimal]:

Example use of Namespace

Example Request is for Namespace String: "mef-global". The following figure illustrates where the namespace request is used in the YANG module.

The name of the module "mef-global" is the namespace string being requested.
The full path of the namespace is then specified in line number 2, and it specifies where in the tree the namespace string is going to be used.
A brief description of where the namespace is going to be used is specified in the description section of this module and could be cut and pasted in the request for namespace application.

Code Block

language	xml
linenumbers	true


module mef-global {
  namespace "urn:mef:yang:mef-global";
  prefix mef-global;
  import ietf-yang-types {
    prefix yang;
  }
  import ietf-inet-types {
    prefix inet;
  }
  import mef-types {
    prefix mef-types;
  }
  organization "MEF Forum";
  contact
    "Web URL: http://mef.net/
     E-mail: namespace@mef.net
     Postal: MEF Forum
             6033 W. Century Boulevard, Suite 1107
             Los Angeles, CA 90045
             U.S.A.
     Phone: +1 310-642-2800
     Fax: +1 310-642-2808";
  description
    "This module defines the shared profiles and related lists
     to be referenced when configuring MEF Services. Service
     Providers are expected to define a set of profiles for
     Service Attributes associated with Bandwidth, L2CP, CoS,
     and so on. These are expected to be slowly changing as
     they reflect the Products offered by the Service Providers
     to their Subscribers.

Content

Space Tools

Versions Compared

Old Version 1

New Version 2

Key

MEF Assigned Names and Numbers (MANN)

Example use of Namespace

Terminology

MEF Forum URN

NameSpace Specific String Root

Contact Information

Contact Information

MEF Assigned URN

Use of MEF Assigned URN

Other Assigned URN

Request for Namespaces

Namespace Application Review

Application Details

Application with Request for New Branches

Namespace Lifecycle

Namespace Structure

yang-nss

xid-nss

<other>-nss

lso-nss

Managing Collisions

Updates to MANN

References

xid-nss

<other>-nss

Managing Collisions

Updates to MANN

References

Example use of Namespace

Content

Space Tools

Breadcrumbs

Page History

Versions Compared

Old Version 1

New Version 2

Key

MEF Assigned Names and Numbers (MANN)

Terminology

MEF Forum URN

NameSpace Specific String Root

Contact Information

Contact Information

MEF Assigned URN

Use of MEF Assigned URN

Other Assigned URN

Request for Namespaces

Namespace Application Review

Application Details

Application with Request for New Branches

Namespace Lifecycle

Namespace Structure

yang-nss

xid-nss

<other>-nss

lso-nss

Managing Collisions

Updates to MANN

References

Example use of Namespace

xid-nss

<other>-nss

Managing Collisions

Updates to MANN

References

Example use of Namespace