URN Namespace for IEEE
draft-ieee-urn-03
The information below is for an old version of the document that is already published as an RFC.
Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 8069.
|
|
---|---|---|---|
Author | Angela Thomas | ||
Last updated | 2017-02-07 (Latest revision 2016-11-16) | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | Informational | ||
Formats | |||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | (None) | ||
IESG | IESG state | Became RFC 8069 (Informational) | |
Action Holders |
(None)
|
||
Consensus boilerplate | Yes | ||
Telechat date | (None) | ||
Responsible AD | Alexey Melnikov | ||
Send notices to | (None) | ||
IANA | IANA review state | IANA OK - Actions Needed | |
IANA action state | RFC-Ed-Ack |
draft-ieee-urn-03
Network Working Group A. Thomas Internet-Draft IEEE Intended status: Informational Expires: April 16, 2017 November 16, 2016 URN Namespace for IEEE draft-ieee-urn-03 Abstract This document describes the Namespace Identifier (NID) 'ieee' for Uniform Resource Names (URNs) used to identify resources published by the 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 Registration Authority. 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 http://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 March 26, 2017. Copyright Notice Copyright (c) 2016 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 (http://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 Thomas Expires April 26, 2017 [Page 1] Internet-Draft Namespace for IEEE November 2016 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 The Institute of Electrical and Electronic Engineers (IEEE) is an organization whose objectives include the educational and technical advancement of electrical and electronic engineering, telecommunications, computer engineering and allied disciplines. Within IEEE, standardization activities are organized into sponsors, such as the LAN/MAN Stadnards Commitee, and then working groups such as 802.1 and 802.3. See http://standards.ieee.org. 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 [RFC3406]. 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: ieee Registration information: registration version number: 1 Thomas Expires April 16, 2017 [Page 2] Internet-Draft Namespace for IEEE November 2016 registration date: 2016-09-26 (Note to RFC Editor: Please update the registration date when this request gets accepted and remove this instruction) Declared registrant of the namespace: Registering organization: Name: Institute of Electrical and Electronics Engineers Address: 445 Hoes Lane Piscataway, NJ 08854 USA Designated contact: Angela Thomas Role: Manager, IEEE Registration Authority Email: ieee-registration-authority@ieee.org Declaration of syntactic structure: The Namespace Specific String (NSS) of all URNs that use the IEEE NID will have the following structure: urn:ieee:{IEEEresource}:{ResourceSpecificString} 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 Expires April 16, 2017 [Page 2] Internet-Draft Namespace for IEEE November 2016 that is covered by "ResourceSpecificString", which also conforms to the naming requirements of [RFC2141]. IEEE maintains a registration authority, the IEEE Registration Authority (IEEE RA), that will manage the assignment of "IEEEresource" 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 this registry and the procedures to be followed are available at: http://standards.ieee.org/develop/regauth/tut/ieeeurn.pdf 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 update documentation of the registered uses of the IEEE NID as needed. This will be structured such that each "IEEEresource" will have a separate description and registration table. The registration tables and information are published and maintained by the IEEE RA on its web site. Process of identifier assignment: IEEE RA 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: The strings used as values of "IEEEresource" and "ResourceSpecificString" are case-insensitive. Thomas Expires April 16, 2017 [Page 3] Internet-Draft Namespace for IEEE November 2016 Conformance with URN Syntax: No special considerations. Validation mechanism: None specified. URN assignment will be handled by procedures implemented in support of IEEE activities. Scope: Global 3. Examples The following examples are representative URNs that could be assigned by IEEE RA. While support for YANG [RFC6020],[RFC7950] was a driver for the creation of the namespace, the following are not necessarily the strings that would be assigned. urn:ieee:std:802.5:yang urn:ieee:foobar 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 (http://www.iana.org) and any associated mirrors. 6. References 6.1. Normative References [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, <http://www.rfc-editor.org/info/rfc3406>. [RFC2141] Moats, R., "URN Syntax", RFC 2141, DOI 10.17487/RFC2141, May 1997, <http://www.rfc-editor.org/info/rfc2141>. Thomas Expires April 16, 2017 [Page 4] Internet-Draft Namespace for IEEE November 2016 6.2. Informative References [RFC1737] Sollins, K. and L. Masinter, "Functional Requirements for Uniform Resource Names", RFC 1737, DOI 10.17487/RFC1737, December 1994, <http://www.rfc-editor.org/info/rfc1737>. [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for the Network Configuration Protocol (NETCONF)", RFC 6020, DOI 10.17487/RFC6020, October 2010, <http://www.rfc-editor.org/info/rfc6020>. [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", RFC 7950, DOI 10.17487/RFC7950, August 2016, <http://www.rfc-editor.org/info/rfc7950>. Acknowledgements The IEEE Registration Authority Committee (RAC) is the oversight committee for the IEEE Registration Authority. The content of this document has been coordinated with the RAC. The technical contact from the RAC was: Glenn Parsons Email: glenn.parsons@ericsson.com Authors' Addresses Angela Thomas IEEE Registration Authority 445 Hoes Lane Piscataway, NJ 08854 USA Phone: +1 732 465 6481 Email: a.n.thomas@ieee.org Thomas Expires April 16, 2017 [Page 5]