Skip to main content

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

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 8515.
Authors Mahesh Jethanandani , Miguel Angel Reina Ortega
Last updated 2018-05-24 (Latest revision 2018-05-17)
RFC stream Internet Engineering Task Force (IETF)
Formats
Reviews
Additional resources
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 8515 (Informational)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD Ignas Bagdonas
Send notices to (None)
draft-mahesh-etsi-urn-00
Network Working Group                                    M. Jethanandani
Internet-Draft
Intended status: Informational                     M. Angel Reina Ortega
Expires: November 20, 2018                                          ETSI
                                                            May 19, 2018

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

Abstract

   This document describes the Namespace Identifier (NID) 'etsi' for
   Uniform Resource Names (URNs) used to identify resources published by
   European Telecommuncations Standards Instititue (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 Assigned Names
   and Numbers (EANN) registry.

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 20, 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

Jethanandani & Angel ReiExpiresgNovember 20, 2018               [Page 1]
Internet-Draft             Namespace for ETSI                   May 2018

   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.

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, aeornautical 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 Unified Resource Name (URN) Uniform
   Resource Names (URNs) [RFC8141] 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                                          |
      +---------+--------------------------------------------------+
      | EANN    | ETSI Assigned Names and Numbers                  |
      |         |                                                  |
      | ETSI    | European Telecommunications Standards Instititue |
      |         |                                                  |
      | NID     | Namespace Identifier                             |
      |         |                                                  |
      | NSS     | Namespace Specific String                        |
      |         |                                                  |
      | RDS     | Resolution Discovery System                      |
      |         |                                                  |
      | URN     | Uniform Resource Name                            |
      +---------+--------------------------------------------------+

2.  URN Specification for ETSI

   Namespace ID:

      etsi

   Registration information:

      registration version number: 1

      registration date: 2018-05-01

Jethanandani & Angel ReiExpiresgNovember 20, 2018               [Page 2]
Internet-Draft             Namespace for ETSI                   May 2018

   Declared registrant of the namespace:

      Registering organization

         Name: ETSI

         Address: 650, Route des Lucioles, Sophia Antipoles 06560,
         France

      Designated contact:

         Role: ETSI Protocol Naming and Numbering Service

         Email: pnns@etsi.org

   Declaration of syntactic structure:

      The syntax of namespace specific strings for the 'etsi' namespace
      is <NSS> in Uniform Resource Names (URNs) [RFC8141].

   Relevant ancillary documentation:

      ETSI publishes information regarding the registered resources in
      the ETSI URN Namespace (EUN) registry
      (https://portal.etsi.org/PNNS/GenericAllocation/
      ETSIURNNamespace.aspx).

   Identifier uniqueness considerations:

      ETSI will manage resource classes using the "etsi" NID and will be
      the authority for managing resources and associated subsequent
      strings.  ETSI is expected to guarantee the uniqueness of the
      strings themselves, or it may permit secondary responsibility for
      certain defined resources.

      ETSI could allow for use of experimental type values 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.

   Identifier persistence considerations:

Jethanandani & Angel ReiExpiresgNovember 20, 2018               [Page 3]
Internet-Draft             Namespace for ETSI                   May 2018

      ETSI will update the ETSI Assigned Names and Numbers (EANN)
      registry to document the registered resources that will use the
      "etsi" NID.

   Process of identifier assignment:

      Assignment of a URN from the ETSI namespace will be documented as
      part of the ETSI Assigned Names and Numbers (EANN) registry.

   Process of identifier resolution:

      The namespace is not listed with an Resolution Discovery System
      (RDS).  Therefore this process is not relevant.

   Rules for Lexical Equivalence:

      The entire URN is case-insensitive.

   Conformance with URN Syntax:

      No special considerations

   Validation mechanism:

      None specified.  URN assignment will be handled by procedures
      implemented in support of ETSI activities.

   Scope:

      Global

3.  Examples

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

      urn:etsi:yang:etsi-services

      urn:etsi:yang:etsi-interfaces

4.  Security Considerations

   There are no additional security considerations other than those
   normally associated with the use and resolution of URNs in general,
   which are described in Function Requirements for URN [RFC1737],
   Uniform Resource Names (URNs) [RFC8141].

Jethanandani & Angel ReiExpiresgNovember 20, 2018               [Page 4]
Internet-Draft             Namespace for ETSI                   May 2018

5.  IANA Considerations

   This document adds a new entry ("etsi") in the urn-namespace
   registry.  This is the defining document.  When published, the entry
   can be found in the "Uniform Resource Names (URN) Namespaces"
   registry available from the IANA site (http://www.iana.org) and any
   associated mirrors.

6.  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>.

   [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>.

Authors' Addresses

   Mahesh Jethanandani
   USA

   Email: mjethanandani@gmail.com

   Miguel Angel Reina Ortega
   ETSI
   650, Route des Lucioles
   Sophia Antipoles  06560
   France

   Email: MiguelAngel.ReinaOrtega@etsi.org

Jethanandani & Angel ReiExpiresgNovember 20, 2018               [Page 5]