Internet Engineering Task Force T. Sloane, Ed. Internet-Draft Open Networking Foundation Intended status: Informational May 22, 2018 Expires: November 23, 2018 URN Namespace for ONF draft-onf-urn Abstract This document describes the Namespace Identifier (NID) 'onf' for Uniform Resource Names (URNs) used to identify resources published by the Open Networking Foundation. 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 https://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 November 23, 2018. Copyright Notice Copyright (c) 2018 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 (https://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 the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Sloane Expires November 23, 2018 [Page 1] Internet-Draft URN Namespace for ONF May 2018 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. URN Specification for ONF . . . . . . . . . . . . . . . . . . 2 2.1. Namespace Identifier . . . . . . . . . . . . . . . . . . 3 2.2. Version . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.3. Date . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.4. Registrant . . . . . . . . . . . . . . . . . . . . . . . 3 2.5. Purpose . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.6. Syntax . . . . . . . . . . . . . . . . . . . . . . . . . 3 2.7. Assignment . . . . . . . . . . . . . . . . . . . . . . . 4 2.8. Security and Privacy . . . . . . . . . . . . . . . . . . 4 2.9. Interoperability . . . . . . . . . . . . . . . . . . . . 4 2.10. Resolution . . . . . . . . . . . . . . . . . . . . . . . 4 2.11. Documentation . . . . . . . . . . . . . . . . . . . . . . 4 3. Additional Information . . . . . . . . . . . . . . . . . . . 4 4. Revision Information . . . . . . . . . . . . . . . . . . . . 5 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 7. Security Considerations . . . . . . . . . . . . . . . . . . . 5 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 8.1. Normative References . . . . . . . . . . . . . . . . . . 5 8.2. Informative References . . . . . . . . . . . . . . . . . 5 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 1. Introduction The Open Networking Foundation (ONF) is a non-profit operator-led consortium driving transformation of network infrastructure and carrier business models. As part of these specification efforts, there is a need to maintain identifiers in a managed namespace that is unique and persistent. To ensure that this namespace's uniqueness is absolute, specification of an URN Namespace Identifier (NID) for use by the ONF is specified in this document, in full conformance with the URN registration process specified in Uniform Resource Names (URNs) RFC 8141 [1]. The ONF 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 ONF URN document. 2. URN Specification for ONF This section contains the material identified in Appendix A RFC 8141 [1]. Sloane Expires November 23, 2018 [Page 2] Internet-Draft URN Namespace for ONF May 2018 2.1. Namespace Identifier Request is made for a formal assignment: onf 2.2. Version 1 2.3. Date 2018-05-31 2.4. Registrant Registering organization: Name: Open Networking Foundation (ONF) Address: 1000 El Camino Real, Suite 100 Menlo Park, California 94205 United States of America Designated contact person: Timon Sloane Role: VP Marketing & Ecosystem, ONF Email: timon@opennetworking.org 2.5. Purpose Namespace needed for YANG RFC 6020 [2] RFC 7950 [3] modules. 2.6. Syntax urn:onf:{ResourceSpecificString} "ResourceSpecificString" identifies the information about the resource. ONF will manage the assignment of "ResourceSpecificString" and the specific registration values assigned for each resource. For clarity, examples of how the ONF plans to manage the IANA provisioned NamespaceId and the ResourceSpecificString follows: urn:{ONF-NamespaceId}:{ONF-Project}:{ONF-SubProject}:{Protocol}:{ModuleName} o ONF-NamespaceId: onf Sloane Expires November 23, 2018 [Page 3] Internet-Draft URN Namespace for ONF May 2018 o The ONF-Project: Example: Open Transport Configuration & Control (OTCC) o ONF-SubProject: Example: Transport API (tapi) o Protocol: Example: yang o ModuleName: Example connectivity So a complete example that provides the URI for the connectivity yang model for the tapi sub-project of the otcc project for the ONF would be: urn:onf:otcc:tapi:yang:connectivity 2.7. Assignment ONF manages resources that utilize this URN identification model. 2.8. Security and Privacy See the material in the Security Considerations (Section 7) section. 2.9. Interoperability The purpose of the ONF namespace and its use for YANG is meant to aid interoperability by avoiding duplicate or conflicting namespaces. 2.10. Resolution No resolution mechanism is intended or anticipated. 2.11. Documentation The ONF maintains a Uniform Resource Names (URN) document that provides the mechanism to ensure the resource identifiers are unique. The ONF URN Management [4] document contains the formatting guidelines for the URN hierarchy that is rooted at the base URN that was assigned by IANA. 3. Additional Information None. Sloane Expires November 23, 2018 [Page 4] Internet-Draft URN Namespace for ONF May 2018 4. Revision Information o v1: Initial Version o v2: Aligned with template in Appendix A RFC 8141 [1] o v3: Moved example to the syntax system. Removed reference to RFC1737, and moved RFC8141 to normative. 5. Acknowledgements Technical contact person: Kam Lam Role: Co-Chair of Open Information Modeling and Tooling Project Email: kam.lam@fiberhome.com 6. IANA Considerations This document adds "onf" to the "Formal URN Namespaces" registry . This is the defining document. 7. Security Considerations There are no additional security considerations other than those normally associated with the use and resolution of URNs in general, which is described in Uniform Resource Names (URNs) RFC 8141 [1]. 8. References 8.1. Normative References [1] Saint-Andre, P. and J. Klensin, "Uniform Resource Names (URNs)", RFC 8141, DOI 10.17487/RFC8141, April 2017, . 8.2. Informative References [2] Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, DOI 10.17487/RFC6020, October 2010, . [3] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", RFC 7950, DOI 10.17487/RFC7950, August 2016, . [4] ONF, "ONF URN Management", 2018, . Sloane Expires November 23, 2018 [Page 5] Internet-Draft URN Namespace for ONF May 2018 Author's Address Timon Sloane (editor) Open Networking Foundation 1000 El Camino Real Suite 100 Menlo Park, California 94025 United States of America Phone: +1 650 208 0857 Email: timon@opennetworking.org Sloane Expires November 23, 2018 [Page 6]