idnits 2.17.00 (12 Aug 2021) /tmp/idnits13100/draft-mahesh-mef-urn-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 3, 2016) is 2292 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 2141 (Obsoleted by RFC 8141) Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group M. Jethanandani 3 Internet-Draft Cisco Systems, Inc 4 Intended status: Informational February 3, 2016 5 Expires: August 6, 2016 7 URN Namespace for MEF Documents 8 draft-mahesh-mef-urn-02 10 Abstract 12 This document describes the Namespace Identifier (NID) 'mef' for 13 Uniform Resource Names (URNs) used to identify resources published by 14 MEF Forum (https://www.mef.net). MEF specifies and manages resources 15 that utilize this URN identification model. Management activities 16 for these and other resources types are handled by the manager of the 17 MEF Assigned Names and Numbers (MANN) registry. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on August 6, 2016. 36 Copyright Notice 38 Copyright (c) 2016 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 1. Introduction 53 The MEF Forum (MEF), is a nonprofit international industry standards 54 organization, dedicated to the worldwide adoption of Carrier Ethernet 55 (CE) networks and services. The forum creates specifications in the 56 area of Services, Architecture, Operations and Management. 58 As part of these specifications efforts, there is a need to identify 59 identifiers in a managed namespace that are unique and persistent. 60 To ensure that this namespace's uniqueness is absolute, a 61 registration of a specific Unified Resource Name (URN) URN Syntax 62 [RFC2141] Namespace Identifier (NID) for use by MEF is being 63 specified in this document. 65 1.1. Terminology 67 +---------+--------------------------------+ 68 | Acronym | Meaning | 69 +---------+--------------------------------+ 70 | CE | Carrier Ethernet | 71 | | | 72 | MANN | MEF Assigned Names and Numbers | 73 | | | 74 | MEF | MEF Forum | 75 | | | 76 | NID | Namespace Identifier | 77 | | | 78 | NSS | Namespace Specific String | 79 | | | 80 | RDS | Resolution Discovery System | 81 | | | 82 | URN | Uniform Resource Name | 83 +---------+--------------------------------+ 85 2. URN Specification for MEF 87 Namespace ID: 89 mef 91 Registration information: 93 registration version number: 1 94 registration date: YYYY-MM-DD (Note to RFC Editor: Please add the 95 registration date when this request gets accepted and remove this 96 instruction) 98 Declared registrant of the namespace: 100 Registering organization 102 Name: MEF Forum 104 Address: 6033 W. Century Boulevard, Suite 1107 Los Angeles CA 105 90045 USA 107 Designated contact: 109 Role: Manager, MEF Namespace 111 Email: namespace@mef.net 113 Declaration of syntactic structure: 115 The syntax of namespace specific strings for the 'mef' namespace 116 is in RFC 2141. 118 Relevant ancillary documentation: 120 MEF publishes information regarding the registered resources in 121 the MEF Assigned Names and Numbers (MANN) registry 122 (https://www.mef.net/MANN). 124 Identifier uniqueness considerations: 126 MEF will manage resource classes using the "mef" NID and will be 127 the authority for managing resources and associated subsequent 128 strings. MEF is expected to guarantee the uniqueness of the 129 strings themselves, or it may permit secondary responsibility for 130 certain defined resources. 132 MEF could allow for use of experimental type values for testing 133 purposes only. Note that using experimental types may create 134 collision as multiple users may use the same values for different 135 resources and specific strings. 137 Identifier persistence considerations: 139 MEF will update the MEF Assigned Names and Numbers (MANN) registry 140 to document the registered resources that will use the "mef" NID. 142 Process of identifier assignment: 144 Assignment of a URN from the MEF namespace will be documented as 145 part of the MEF Assigned Names and Numbers (MANN) registry. 147 Process of identifier resolution: 149 The namespace is not listed with an Resolution Discovery System 150 (RDS). Therefore this process is not relevant. 152 Rules for Lexical Equivalence: 154 The entire URN is case-insensitive. 156 Conformance with URN Syntax: 158 No special considerations 160 Validation mechanism: 162 None specified. URN assignment will be handled by procedures 163 implemented in support of MEF activities. 165 Scope: 167 Global 169 3. Examples 171 The following are examples of URNs that MEF is looking to assign: 173 urn:mef:yang:mef-services 175 urn:mef:yang:mef-interfaces 177 4. Security Considerations 179 There are no additional security considerations other than those 180 normally associated with the use and resolution of URNs in general, 181 which are described in Function Requirements for URN [RFC1737], URN 182 Syntax [RFC2141]. 184 5. IANA Considerations 186 This document adds a new entry ("mef") in the urn-namespace registry. 187 This is the defining document. When published, the entry can be 188 found in the "Uniform Resource Names (URN) Namespaces" registry 189 available from the IANA site (https://www.iana.org) and any 190 associated mirrors. 192 6. Normative References 194 [RFC1737] Sollins, K. and L. Masinter, "Functional Requirements for 195 Uniform Resource Names", RFC 1737, DOI 10.17487/RFC1737, 196 December 1994, . 198 [RFC2141] Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141, 199 May 1997, . 201 Author's Address 203 Mahesh Jethanandani 204 Cisco Systems, Inc 205 180 W. Tasman Drive 206 San Jose, CA 95134 207 USA 209 Phone: +1 408.526.8763 210 Email: mjethanandani@gmail.com