Return-Path: X-Original-To: urn-nid@ietfa.amsl.com Delivered-To: urn-nid@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61C5C1B3360 for ; Thu, 15 Oct 2015 07:56:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.413 X-Spam-Level: * X-Spam-Status: No, score=1.413 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MANGLED_MEDS=2.3, MPART_ALT_DIFF_COUNT=1.112, SPF_PASS=-0.001] autolearn=no Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1x1kwuCvIIhN for ; Thu, 15 Oct 2015 07:56:27 -0700 (PDT) Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E2551B324C for ; Thu, 15 Oct 2015 07:56:18 -0700 (PDT) Received: by oixx6 with SMTP id x6so31604865oix.2 for ; Thu, 15 Oct 2015 07:56:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:date:message-id:cc:to:mime-version; bh=iOpskOXImEp5GHKbgONGpwMfKw7GJHhOq0x52hSpEKA=; b=vmCWyajHHoFwY3O/MRO9JlsdNJHqpAHtgBF3xxZNERPTk5g4DqptB9QEP7RMb9hpW9 r6KEAjj5ECq9uIAoULAbqNZ1+wsSStJL4QiqY4EnASFPopfWL9BbSID+DFHLv/UwTLEW gpRySGL21Y/nn01RzJeScNEI7JRI5fk8aD7S02rnH/G9p2+6ZqR3N0BSJtJujIip9sB0 Qe3EATKKO7omVYfjJ3zF1T5kxgI5m07JmybvJ52wSpWtPdqqiKKhXKAEPCmRkMlDGNY1 cwLiPYSB/8XOQCvWRh7Vdh1sh5hkbYZ8nU/lMSZEx1YRevjMFUsMvbgZVBUs9+POAssv e0Kg== X-Received: by 10.202.97.196 with SMTP id v187mr5649482oib.91.1444920977411; Thu, 15 Oct 2015 07:56:17 -0700 (PDT) Received: from mahesh-m-62at.attlocal.net ([2602:306:cf77:df90:39e8:94df:fd6b:e48c]) by smtp.gmail.com with ESMTPSA id x205sm6512380oix.0.2015.10.15.07.56.15 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 15 Oct 2015 07:56:16 -0700 (PDT) From: Mahesh Jethanandani Content-Type: multipart/alternative; boundary="Apple-Mail=_F6FAA6F9-6516-419D-8C92-CD1554C87B69" Subject: URN Namespace for MEF Date: Thu, 15 Oct 2015 07:56:14 -0700 Message-Id: To: urn-nid@apps.ietf.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) X-Mailer: Apple Mail (2.2098) Archived-At: Cc: Benoit Claise , "Wolfe, Jason \(P020296\)" , "Ranganathan, Raghu" X-BeenThere: urn-nid@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: discussion of new namespace identifiers for URNs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Oct 2015 14:56:29 -0000 --Apple-Mail=_F6FAA6F9-6516-419D-8C92-CD1554C87B69 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii This submission is for a URN NID for MEF. Comments are welcome on this = draft. There is a companion document, called the MEF Assignment of Names and = Numbers (MANN) that is an MEF document under discussion, and has some of = the answers in this template. The attached drafts points to the MANN = document in the relevant section. MANN will be posted on MEF website = once the committee has had a chance to review and approve it. Mahesh Jethanandani mjethanandani@gmail.com --Apple-Mail=_F6FAA6F9-6516-419D-8C92-CD1554C87B69 Content-Type: multipart/mixed; boundary="Apple-Mail=_B74345FA-E34D-4426-A103-16AC02518D8B" --Apple-Mail=_B74345FA-E34D-4426-A103-16AC02518D8B Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii This submission is for a URN NID for MEF. Comments are welcome on this draft.

There is a companion document, called the MEF Assignment of Names and Numbers (MANN) that is an MEF document under discussion, and has some of the answers in this template. The attached drafts points to the MANN document in the relevant section. MANN will be posted on MEF website once the committee has had a chance to review and approve it.

Mahesh Jethanandani


--Apple-Mail=_B74345FA-E34D-4426-A103-16AC02518D8B Content-Disposition: attachment; filename=draft-mahesh-mef-urn-00.txt Content-Type: text/plain; name="draft-mahesh-mef-urn-00.txt" Content-Transfer-Encoding: quoted-printable Network Working Group M. Jethanandani Internet-Draft Cisco Systems, Inc Intended status: Standards Track September 15, 2015 Expires: March 18, 2016 URN Namespace for MEF Documents draft-mahesh-mef-urn-00 Abstract 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 http://datatracker.ietf.org/drafts/current/. 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 March 18, 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 (http://trustee.ietf.org/license-info) 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 March 18, 2016 [Page 1] =0C Internet-Draft Namespace for MEF September 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 [RFC3406]. 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 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 March 18, 2016 [Page 2] =0C Internet-Draft Namespace for MEF September 2015 2. URN Specification for MEF Namespace ID: mef Registration information: registration version number: 1 registration date: 2015-09-15 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 Email: namespace@mef.net 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) = registry. 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 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 Jethanandani Expires March 18, 2016 [Page 3] =0C Internet-Draft Namespace for MEF September 2015 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. Scope: Global 3. Examples The following are examples of URNs that a resolver for this namespace can resolve: urn:mef:params:xml:ns:yang:mef-services urn:mef:params:xml:ns:yang:mef-interfaces Jethanandani Expires March 18, 2016 [Page 4] =0C Internet-Draft Namespace for MEF September 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 (http://www.iana.org) and any associated mirrors. 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 March 18, 2016 [Page 5] =0C Internet-Draft Namespace for MEF September 2015 Author's Address Mahesh Jethanandani Cisco Systems, Inc 180 W. Tasman Drive San Jose, CA 95134 USA Phone: 408.526.8763 Email: mjethanandani@gmail.com Jethanandani Expires March 18, 2016 [Page 6] --Apple-Mail=_B74345FA-E34D-4426-A103-16AC02518D8B Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii



--Apple-Mail=_B74345FA-E34D-4426-A103-16AC02518D8B-- --Apple-Mail=_F6FAA6F9-6516-419D-8C92-CD1554C87B69--