Network Working Group M. Jethanandani
Internet-Draft VMware
Intended status: Informational M. Angel Reina Ortega
Expires: May 21, 2019 ETSI
November 17, 2018

URN Namespace for ETSI Documents
draft-mahesh-etsi-urn-05

Abstract

This document describes the Namespace Identifier (NID) 'etsi' for Uniform Resource Names (URNs) used to identify resources published by European Telecommunications Standards Institute (http://etsi.org). ETSI 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 ETSI Protocol Naming and Numbering Service (PNNS).

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 May 21, 2019.

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.


Table of Contents

1. Introduction

ETSI is a nonprofit international industry standards organization, that produces globally acceptable standards for Information & Communication Technologies including fixed, mobile, radio, broadcast, internet, aeronautical and other areas.

As part of these specifications efforts, there is a need to identify identifiers in a managed namespace that are unique and persistent. To ensure that this namespace's uniqueness is absolute, a registration of a specific Uniform Resource Names (URNs) Namespace Identifier (NID) for use by ETSI is being specified in this document, in full conformance with the NID registration process specified in the document.

1.1. Terminology

Acronym Meaning
ETSI European Telecommunications Standards Institute
EUN ETSI URN Namespace
NID Namespace Identifier
NSS Namespace Specific String
PNNS Protocol Name and Numbering Service
RDS Resolution Discovery System
URI Uniform Resouce Identifier
URN Uniform Resource Name

2. URN Specification for ETSI

Namespace Identifier:

Version:

Date:

Registrant:

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 it defines and which 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. It is the servers that 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 entire URN is case-insensitive.

Assignment:

Interoperability:

There are no known interoperability issues at this time.

Resolution:

Documentation:

3. Examples

The following are examples of URNs that ETSI is looking to assign:

Although all of these examples are related to network management with YANG, 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 that are normally associated with the use and resolution of URNs in general, which are described in Function Requirements for URN, Uniform Resource Names (URNs).

5. IANA Considerations

IANA is requested to register the formal URN namespace "etsi" using the template given above 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.
[RFC6963] Saint-Andre, P., "A Uniform Resource Name (URN) Namespace for Examples", BCP 183, RFC 6963, DOI 10.17487/RFC6963, May 2013.
[RFC8141] Saint-Andre, P. and J. Klensin, "Uniform Resource Names (URNs)", RFC 8141, DOI 10.17487/RFC8141, April 2017.

6.2. Informative References

[RFC7950] Bjorklund, M., "The YANG 1.1 Data Modeling Language", RFC 7950, DOI 10.17487/RFC7950, August 2016.

Authors' Addresses

Mahesh Jethanandani VMware USA EMail: mjethanandani@gmail.com
Miguel Angel Reina Ortega ETSI 650, Route des Lucioles Sophia Antipolis, 06560 France EMail: MiguelAngel.ReinaOrtega@etsi.org