URN ETSI: URN Namespace for ETSI Documents
A permanent naming scheme for ETSI standards documents.
Jethanandani, M. and M.A. Reina Ortega, "URN Namespace for ETSI Documents", RFC 8515, DOI 10.17487/RFC8515, February 2019, <https://www.rfc-editor.org/info/rfc8515>.
@misc{rfc8515,
series = {Request for Comments},
number = 8515,
howpublished = {RFC 8515},
publisher = {RFC Editor},
doi = {10.17487/RFC8515},
url = {https://www.rfc-editor.org/info/rfc8515},
author = {M. Jethanandani and M.A. Reina Ortega},
title = {{URN Namespace for ETSI Documents}},
pagetotal = 7,
year = 2019,
month = feb,
} RFC text
Contents
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
Abstract
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.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8515.
Copyright Notice
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.
Table of Contents
1. Introduction ....................................................3
1.1. Terminology ................................................3
2. URN Specification for ETSI ......................................4
3. Examples ........................................................6
4. Security Considerations .........................................6
5. IANA Considerations .............................................6
6. References ......................................................6
6.1. Normative References .......................................6
6.2. Informative References .....................................6
Authors' Addresses .................................................7
1. Introduction
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].
1.1. Terminology
+---------+-------------------------------------------------+
| Acronym | Meaning |
+---------+-------------------------------------------------+
| ETSI | European Telecommunications Standards Institute |
| | |
| EUN | ETSI URN Namespace |
| | |
| NID | Namespace Identifier |
| | |
| NSS | Namespace Specific String |
| | |
| PNNS | Protocol Naming and Numbering Service |
| | |
| URI | Uniform Resource Identifier |
| | |
| URN | Uniform Resource Name |
+---------+-------------------------------------------------+
2. URN Specification for ETSI
Namespace Identifier:
etsi
Version:
1
Date:
2018-10-22
Registrant:
ETSI Protocol Naming and Numbering Service (PNNS)
European Telecommunications Standards Institute (ETSI)
650, Route des Lucioles
Sophia Antipolis 06560
France
Email: pnns@etsi.org
Purpose:
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.
Syntax:
The syntax of Namespace Specific Strings for the "etsi" namespace
is <NSS> in Uniform Resource Names (URNs) [RFC8141].
The entire URN is case-insensitive.
Assignment:
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].
Security and Privacy:
See Section 4 of RFC 8515.
Interoperability:
There are no known interoperability issues at this time.
Resolution:
It is not foreseen that URNs within this namespace will undergo
resolution.
Documentation:
Documentation can be found at
<https://portal.etsi.org/PNNS/GenericAllocation/
ETSIURNNamespace.aspx>.
3. Examples
The following are examples of URNs that ETSI is looking to assign:
urn:etsi:yang:etsi-nfv
urn:etsi:yang:etsi-nfv-vnf
urn:etsi:yang:etsi-nfv-pnf
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.
4. Security Considerations
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].
5. IANA Considerations
IANA has registered "etsi" in the "Formal URN Namespaces" registry
using the template in Section 2.
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, <https://www.rfc-editor.org/info/rfc1737>.
[RFC6963] Saint-Andre, P., "A Uniform Resource Name (URN) Namespace
for Examples", BCP 183, RFC 6963, DOI 10.17487/RFC6963,
May 2013, <https://www.rfc-editor.org/info/rfc6963>.
[RFC8141] Saint-Andre, P. and J. Klensin, "Uniform Resource Names
(URNs)", RFC 8141, DOI 10.17487/RFC8141, April 2017,
<https://www.rfc-editor.org/info/rfc8141>.
6.2. Informative References
[RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
RFC 7950, DOI 10.17487/RFC7950, August 2016,
<https://www.rfc-editor.org/info/rfc7950>.
Authors' Addresses
Mahesh Jethanandani
VMware
United States of America
Email: mjethanandani@gmail.com
Miguel Angel Reina Ortega
ETSI
650, Route des Lucioles
Sophia Antipolis 06560
France
Email: MiguelAngel.ReinaOrtega@etsi.org
AI ELI5
On this page
§1Introduction to URN Namespaces
ETSI (European Telecommunications Standards Institute) is an international standards organization that publishes specifications for information and communication technologies across many domains: fixed and mobile networks, radio, broadcast, internet and others.
Like other major standards bodies, ETSI needed a way to create persistent, globally unique identifiers for all the resources it publishes. This RFC registers a formal Uniform Resource Name (URN) Namespace Identifier called 'etsi' that allows ETSI to create identifiers following a standard format. A URN like 'urn:etsi:yang:etsi-nfv' serves as a permanent name that never changes, even if the physical location of the document changes.
Imagine you want to give everything you make its own permanent name tag that won't change no matter where you move it. That's what a URN namespace does.
§2URN Namespace Components
A URN has two main parts. The Namespace Identifier (NID) is the prefix, like 'etsi'. The Namespace Specific String (NSS) is everything after it, like 'yang:etsi-nfv' in the full URN 'urn:etsi:yang:etsi-nfv'.
The RFC specifies that ETSI's namespace is case-insensitive, so 'URN:ETSI:YANG:ETSI-NFV' and 'urn:etsi:yang:etsi-nfv' both refer to the same resource. The RFC follows the formal registration requirements defined in RFC 8141.
The prefix 'etsi' is the first part, like your first name. The rest is specific to each resource, like your last name and address.
§3How ETSI Manages the Namespace
ETSI maintains a registry of subtrees that use the 'etsi' NID at its Protocol Naming and Numbering Service (PNNS). When ETSI assigns a subtree (like 'yang' for YANG data models), that assignment cannot later be deleted or reassigned to something else, ensuring stability.
ETSI may permit secondary responsibility for certain defined resources and may allow experimental namespace values for testing, following the guidance in RFC 6963. Once a subtree assignment is made to a particular purpose, it remains dedicated to that purpose permanently.
ETSI keeps a list of all the different types of things it names, and once it decides that 'yang' means data models, that meaning stays forever.
§4Examples of ETSI URNs
The RFC provides examples of URNs that ETSI might assign: 'urn:etsi:yang:etsi-nfv', 'urn:etsi:yang:etsi-nfv-vnf' and 'urn:etsi:yang:etsi-nfv-pnf'. These examples are all related to network management using YANG, a data modeling language. The RFC notes that while these examples focus on YANG, ETSI may in the future create URNs with different sub-identifiers for other types of resources.
For example, ETSI might say 'urn:etsi:yang:etsi-nfv' is the permanent name for the NFV (network function virtualization) data model.
§5Security and Considerations
The RFC notes that there are no additional security considerations beyond those normally associated with URNs in general, as described in RFC 1737 and RFC 8141. The main benefit is that by having a stable, persistent naming scheme, downstream users can rely on the names staying the same, making systems more robust.
Using permanent names is actually safer because programs can rely on those names never disappearing.