Internet Engineering Task Force (IETF) M. Jethanandani Request for Comments: 8515 VMware Category: Informational M.A. Reina Ortega ISSN: 2070-1721 ETSI February 2019
URN Namespace for ETSI Documents
This document describes the Namespace Identifier (NID) "etsi" for Uniform Resource Names (URNs) used to identify resources published by the European Telecommunications Standards Institute (http://etsi.org). ETSI specifies and manages resources that utilize this URN identification model. Management activities for these and other resource types are handled by the manager of the ETSI Protocol Naming and Numbering Service (PNNS).
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 candidates for any level of Internet Standard; see Section 2 of RFC 7841.
Copyright (c) 2019 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.
ETSI is a nonprofit international industry standards organization that produces globally acceptable standards for information and communication technologies including fixed, mobile, radio, broadcast, internet, aeronautical, and other areas.
As part of these efforts, there is a need to specify identifiers in a managed namespace that are unique and persistent. To ensure that this namespace's uniqueness is absolute, the registration of a specific Uniform Resource Name (URN) [RFC8141] Namespace Identifier (NID) for use by ETSI is specified in this document, in full conformance with the NID registration process specified in [RFC8141].
ETSI Protocol Naming and Numbering Service (PNNS) European Telecommunications Standards Institute (ETSI) 650, Route des Lucioles Sophia Antipolis 06560 France Email: email@example.com
The Namespace Identifier (NID) "etsi" for Uniform Resource Names (URNs) will be used to identify resources published by ETSI. These might include published standards or protocols that ETSI defines and that make use of URNs. These namespaces are globally unique. The URN namespace will be used in public networks by clients to configure and manage resources in the network. Servers will enforce the uniqueness of the namespaces by using the namespace and the XPath associated with the managed node in the network when accessing a resource.
The syntax of Namespace Specific Strings for the "etsi" namespace is <NSS> in Uniform Resource Names (URNs) [RFC8141].
ETSI will maintain the list of registered subtrees that use the "etsi" NID in the "ETSI URN Namespace" registry at <https://portal.etsi.org/PNNS/GenericAllocation/ ETSIURNNamespace.aspx>. The registry describes the <NSS>, how namespaces will be allocated, and how experimental namespaces can be used within the allocated URN.
ETSI will manage resource classes using the "etsi" NID and will be the authority for managing resources and associated subsequent strings. ETSI will guarantee the uniqueness of the strings by validating them against the existing content of the registry. ETSI may also permit secondary responsibility for certain defined resources. Once a subtree assignment is made, it cannot be deleted or reassigned.
ETSI may allow use of experimental type values in specific subtrees for testing purposes only. Note that using experimental types may create collision as multiple users may use the same values for different resources and specific strings. All experimentation must follow the guidance set forth in "A Uniform Resource Name (URN) Namespace for Examples" [RFC6963].
The following are examples of URNs that ETSI is looking to assign:
Although all of these examples are related to network management with YANG [RFC7950], URNs related to other kinds of resources might be assigned in the future, in which case a "sub-identifier" other than "yang" might be created.
There are no additional security considerations apart from what are normally associated with the use and resolution of URNs in general, which are described in "Functional Requirements for Uniform Resource Names" [RFC1737] and "Uniform Resource Names (URNs)" [RFC8141].