Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

[802SEC] Proposed PAR: P802d - Overview and Architecture - Amendment: URN Namespace


This is a late submission by me of a PAR for EC pre-submission for approval in November.

This could be considered under the same category as maintenance since we have two currently approved YANG PARs (P802.1Qcp & P802.1Xck) that are now dependent on the creation of a root URN namespace (that would be defined in the O&A per this new PAR).     

This was discussed at the September 802.1 meeting that produced this PAR and CSD:

I would note that this effort will be in conjunction to an IEEE RAC written IETF Internet Draft that is planned to be submitted for the November IETF –it is attached.

I would request that this be considered for review by all WGs at the November plenary, and also be considered for approval by the EC.

Please let me know if you have any comments or questions.




Glenn Parsons - Chair, IEEE 802.1



---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.

Network Working Group                                          A. Thomas
Internet-Draft                                        							IEEE
Intended status: Standards Track                               
Expires: February 1, 2016                              September 1, 2015

                       URN Namespace for IEEE 


   This document describes the Namespace Identifier (NID) 'ieee' for
   Uniform Resource Names (URNs) used to identify resources published by
   Institute of Electrical and Electronics Engineers (IEEE).  IEEE
   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 IEEE Assigned Names and Number

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

   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 February 1, 2016.

Copyright Notice

   Copyright (c) 2015 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
   ( 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

Thomas                   Expires February 1, 2016                [Page 1]
Internet-Draft             Namespace for IEEE                  July 2015

   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

   Institute of Electrical and Electronic Engineers (IEEE) is an
   organization whose objective are the educational and technical
   advancement of electrical and electronic engineering,
   telecommunications, computer engineering and allied disciplines.
   Within IEEE, standardiation activities are organized into sponsors,
   such as the LAN/MAN Stadnards Commitee, and then working groups 
   such as 802.1 and 802.3.

   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) URN Syntax
   [RFC2141] Namespace Identifier (NID) for use by IEEE is being
   specified in this document, in full conformance with the NID
   registration process specified in URN Namespace Definition Mechanism

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   document are to be interpreted as described in Key words for use in
   RFCs to Indicate Requirement Levels [RFC2119].

1.1.  Terminology

      | Acronym | Meaning                                           |
      | IEEE    | Institute of Electrical and Electronics Engineers |
      |         |                                                   |
      | NID     | Namespace Identifier                              |
      |         |                                                   |
      | URN     | Uniform Resource Name                             |

2.  URN Specification for IEEE

   Namespace ID:


   Registration information:

   	registration version number: 1

Thomas                  Expires February 1, 2016                [Page 2]
Internet-Draft             Namespace for IEEE             September 2015

   	registration date: 2015-09-01

   Declared registrant of the namespace:

   	Registering organization:

   		Name: Institute of Electrical and Electronics Engineers

   		Address:      445 Hoes Lane 
                    Piscataway, NJ 08854

   		Designated contact:   Angela Thomas

   			Role: Manager, IEEE Registration Authority 


   Declaration of syntactic structure:

   	The Namespace Specific String (NSS) of all URNs that use the IEEE NID
   	will have the following structure:
   	  The Namespace Specific String (NSS) of all URNs that use the IEEE
      NID will have the following structure:


      where the "IEEEresource" is a US-ASCII string that conforms to the
      URN syntax requirements [RFC2141] and defines a specific class of
      resource type.  Each resource type has a specific labeling scheme

Thomas                        Informational                      [Page 2]
Internet-Draft          URN Namespace for OMA                January 2006

      that is covered by "ResourceSpecificString", which also conforms
      to the naming requirements of [RFC2141].

      IEEE maintains a regirstation authority, the IEEE Registration 
      Authority (IEEE RA), that will manage the assignment of 
      "IEEEresources" and the specific registration values assigned 
      for each resource class.

   Relevant ancillary documentation:

      The IEEE Registration Authority (IEEE RA) provides information on
      the registered resources and the registrations for each.  More
      information about IEEE RA and the registration activities and
      procedures to be followed are available at:

   Identifier uniqueness considerations:

   	  The IEEE RA will manage resources using the IEEE NID and will be
      the authority for managing the resources and subsequent strings
      associated.  In the associated procedures, IEEE RA will ensure the
      uniqueness of the strings themselves or shall permit secondary
      responsibility for management of well-defined sub-trees.

   Identifier persistence considerations:

  		IEEE will provide clear documentation of the registered uses of
      the IEEE NID.  This will be structured such that each IEEEresource
      will have a separate description and registration table.

      The registration tables and information will be published and
      maintained by the IEEE RA on its web site.

   Process of identifier assignment:

   	 IEEE will provide procedures for registration of each type of
     resource that it maintains.

   Process of identifier resolution:

   	 The namespace is not listed with an RDS; this is not relevant.

   Rules for Lexical Equivalence:

   	No special considerations; the rules for lexical equivalence of
    [RFC2141] apply.

Thomas                   Expires February 1, 2016               [Page 3]
Internet-Draft             Namespace for IEEE             September 2015

   Conformance with URN Syntax:

   	No special considerations.
   Validation mechanism:

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



3.  Examples

   The following examples are representative urns that could be assigned
   by IEEE RA.  They may not be the actual strings that would be assigned.



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 Functional Requirements for URN [RFC1737], URN
   Syntax [RFC2141], and URN Namespace Definition Mechanism [RFC3406].

5.  IANA Considerations

   This document adds a new entry ("ieee") 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 ( and any
   associated mirrors.

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

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,

   [RFC2141]  Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141,
              May 1997, <>.

Thomas                  Expires February 1, 2016                [Page 4]
Internet-Draft             Namespace for IEEE             September 2015

   [RFC3406]  Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom,
              "Uniform Resource Names (URN) Namespace Definition
              Mechanisms", BCP 66, RFC 3406, DOI 10.17487/RFC3406,
              October 2002, <>.

   [RFC6020]  Bjorklund, M., Ed., "YANG - A Data Modeling Language for
              the Network Configuration Protocol (NETCONF)", RFC 6020,
              DOI 10.17487/RFC6020, October 2010,

6.2.  Informative References

   [RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing an
              IANA Considerations Section in RFCs", BCP 26, RFC 5226,
              DOI 10.17487/RFC5226, May 2008,

Authors' Addresses

   Angela Thomas
	 IEEE Registration Authority 
   445 Hoes Lane 
   Piscataway, NJ 08854

   Phone: +1 732 465 6481  

Thomas                  Expires February 1, 2016                [Page 5]

This email is sent from the 802 Executive Committee email reflector.  This list is maintained by Listserv.