💾 Archived View for gemini.bortzmeyer.org › rfc-mirror › rfc8515.txt captured on 2023-07-22 at 17:40:09.
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
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.
Jethanandani & Reina Ortega Informational [Page 1]
RFC 8515 Namespace for ETSI February 2019
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
Jethanandani & Reina Ortega Informational [Page 2]
RFC 8515 Namespace for ETSI February 2019
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 |
+---------+-------------------------------------------------+
Jethanandani & Reina Ortega Informational [Page 3]
RFC 8515 Namespace for ETSI February 2019
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.
Jethanandani & Reina Ortega Informational [Page 4]
RFC 8515 Namespace for ETSI February 2019
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>.
Jethanandani & Reina Ortega Informational [Page 5]
RFC 8515 Namespace for ETSI February 2019
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>.
Jethanandani & Reina Ortega Informational [Page 6]
RFC 8515 Namespace for ETSI February 2019
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
Jethanandani & Reina Ortega Informational [Page 7]