RFC 8069

URN Namespace for IEEE

📅 published February 2017, from ietf

RFC 8069: URN Namespace for IEEE 🎀

Okay bestie, here's the title block tea ☕💅

  • Number and title: RFC 8069, URN Namespace for IEEE
  • Author: A. Thomas (Angela Thomas), IEEE
  • Category: Informational
  • Date: February 2017
  • ISSN: 2070-1721
  • Obsoletes / Updates: none listed in the title block, so this one doesn't replace or update anything 🙈

Abstract ✨

This doc defines the Namespace Identifier (NID) ieee for Uniform Resource Names (URNs) 🫶 It's for identifying resources published by the Institute of Electrical and Electronics Engineers (IEEE). IEEE specifies and manages resources that use this URN identification model, and management for these and other resource types is handled by the manager of the IEEE Registration Authority 👑

Status of This Memo 📝

Lowkey important: this is not an Internet Standards Track spec. It's published for informational purposes 🦋

It's a product of the Internet Engineering Task Force (IETF) and represents IETF community consensus. It got public review and was approved for publication by the Internet Engineering Steering Group (IESG). Not every IESG-approved doc is a candidate for any level of Internet Standard, so check Section 2 of RFC 7841 for that 🌸

For the current status, errata, and how to send feedback, go to http://www.rfc-editor.org/info/rfc8069 💜

Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved 🌈

This doc is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) as they stand on the publication date. Please actually read those, because they spell out your rights and restrictions for this doc 🙈 Any Code Components pulled out of this doc must include the Simplified BSD License text, as described in Section 4.e of the Trust Legal Provisions, and they come with no warranty, as described in the Simplified BSD License 💅

Table of Contents 🗺️

1. Introduction ....................................................2
   1.1. Terminology ................................................2
2. URN Specification for IEEE ......................................3
3. Examples ........................................................5
4. Security Considerations .........................................5
5. IANA Considerations .............................................5
6. References ......................................................5
   6.1. Normative References .......................................5
   6.2. Informative References .....................................6
Acknowledgements ...................................................6
Author's Address ...................................................6

1. Introduction 🌸

The Institute of Electrical and Electronic Engineers (IEEE) is an organization whose goals include the educational and technical advancement of electrical and electronic engineering, telecommunications, computer engineering, and allied disciplines 🧚 Inside IEEE, standardization work is organized into sponsors, like the LAN/MAN Standards Committee, and then working groups such as 802.1 and 802.3. More info at http://standards.ieee.org ✨

Here's the need: IEEE's spec work requires identifiers in a managed namespace that's unique and persistent 💖 To make sure that uniqueness is absolute, this doc specifies a registration of a specific URN Syntax [RFC2141] Namespace Identifier (NID) for IEEE use. The registration follows the NID registration process in URN Namespace Definition Mechanisms [RFC3406] in full conformance 💅

1.1. Terminology 📚

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

2. URN Specification for IEEE 🔥

This is the core bit, so pay attention bestie 👀

Namespace ID: ieee

Registration information:

  • Registration version number: 1
  • Registration date: 2016-12-05

Declared registrant of the namespace:

  • Registering organization: Institute of Electrical and Electronics Engineers
  • Address:
445 Hoes Lane
Piscataway, NJ 08854
USA
  • Designated contact person: Angela Thomas
  • Role: Manager, IEEE Registration Authority
  • Email: ieee-registration-authority@ieee.org

Declaration of syntactic structure:

The Namespace Specific String (NSS) of every URN that uses the IEEE NID has this structure 🎀

urn:ieee:{IEEEresource}:{ResourceSpecificString}

IEEEresource is a US-ASCII string that follows the URN syntax requirements [RFC2141] and defines one specific class of resource type. Each resource type has its own labeling scheme, which is covered by ResourceSpecificString, and that also follows the naming requirements [RFC2141] 🦋

IEEE keeps a registration authority, the IEEE Registration Authority (IEEE RA), which manages the assignment of IEEEresource and the specific registration values for each resource class 👑

Relevant ancillary documentation:

The IEEE RA shares info on the registered resources and the registrations for each one. You can find more about this registry and its procedures at http://standards.ieee.org/develop/regauth/tut/ieeeurn.pdf 📄

Identifier uniqueness considerations:

The IEEE RA manages resources under the IEEE NID and is the authority for managing those resources and their related strings. In its procedures, the IEEE RA either makes sure the strings themselves are unique or allows secondary responsibility for managing well-defined sub-trees 🫶

Identifier persistence considerations:

IEEE updates its documentation of registered uses of the IEEE NID as needed. It's set up so each IEEEresource has its own description and registration table 💜

The IEEE RA publishes and maintains the registration tables and info on its website 🌈

Process of identifier assignment:

The IEEE RA provides procedures for registering each type of resource it maintains ✨

Process for identifier resolution:

The namespace is not listed with an RDS, which isn't relevant here 🙈

Rules for Lexical Equivalence:

The strings used as values for IEEEresource and ResourceSpecificString are case insensitive 💅

Conformance with URN Syntax:

No special considerations 🍓

Validation mechanism:

None specified. URN assignment is handled by procedures set up for IEEE activities ⭐

Scope:

Global 🌍

3. Examples 🧚

These are representative URNs that the IEEE RA could assign. YANG [RFC6020] [RFC7950] support was the catalyst for creating this namespace, but these aren't necessarily the strings that would actually get assigned 💖

urn:ieee:std:802.5:yang

urn:ieee:foobar

4. Security Considerations 🔒

⚠️ Serious bestie moment: there are no security considerations beyond the ones that normally come with using and resolving URNs in general. Those are covered in Functional Requirements for URNs [RFC1737], URN Syntax [RFC2141], and URN Namespace Definition Mechanisms [RFC3406]. Go read them 🙏

5. IANA Considerations 📋

This doc adds ieee to the "Formal URN Namespaces" registry at http://www.iana.org/assignments/urn-namespaces. This is the defining document 👑

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

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. This doc was coordinated with the RAC, and their technical contact was:

Glenn Parsons
Email: glenn.parsons@ericsson.com

Author's Address 💌

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

Phone: +1 732 465 6481
Email: a.n.thomas@ieee.org
📦 where this page comes from