Internet Engineering Task Force (IETF) A. Thomas
Request for Comments: 8069 IEEE
Category: Informational February 2017
ISSN: 2070-1721
Internet Engineering Task Force (IETF) A. Thomas
Request for Comments: 8069 IEEE
Category: Informational February 2017
ISSN: 2070-1721
URN Namespace for IEEE
IEEE的URN命名空间
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.
本文档描述了统一资源名称（URN）的名称空间标识符（NID）‘ieee’，用于标识电气和电子工程师协会（ieee）发布的资源。IEEE指定并管理利用此URN标识模型的资源。这些和其他资源类型的管理活动由IEEE注册机构的经理处理。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 7841.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 7841第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc8069.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc8069.
Copyright Notice
版权公告
Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2017 IETF信托基金和确定为文件作者的人员。版权所有。
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 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.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
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 ....................................................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
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 Standards Committee, and then working groups such as 802.1 and 802.3. See <http://standards.ieee.org>.
电气和电子工程师协会（IEEE）是一个组织，其目标包括电气和电子工程、电信、计算机工程和相关学科的教育和技术进步。在IEEE内部，标准化活动被组织成赞助商，如LAN/MAN标准委员会，然后是工作组，如802.1和802.3。看<http://standards.ieee.org>.
As part of these specification efforts, there is a need to maintain identifiers in a managed namespace that is unique and persistent. To ensure that this namespace's uniqueness is absolute, a registration of a specific URN Syntax [RFC2141] Namespace Identifier (NID) for use by IEEE is specified in this document, in full conformance with the NID registration process specified in URN Namespace Definition Mechanisms [RFC3406].
作为这些规范工作的一部分，需要在唯一且持久的托管命名空间中维护标识符。为确保该名称空间的唯一性是绝对的，本文档中规定了IEEE使用的特定URN语法[RFC2141]名称空间标识符（NID）的注册，完全符合URN名称空间定义机制[RFC3406]中规定的NID注册过程。
+---------+---------------------------------------------------+
| Acronym | Meaning |
+---------+---------------------------------------------------+
| IEEE | Institute of Electrical and Electronics Engineers |
| | |
| NID | Namespace Identifier |
| | |
| URN | Uniform Resource Name |
+---------+---------------------------------------------------+
+---------+---------------------------------------------------+
| Acronym | Meaning |
+---------+---------------------------------------------------+
| IEEE | Institute of Electrical and Electronics Engineers |
| | |
| NID | Namespace Identifier |
| | |
| URN | Uniform Resource Name |
+---------+---------------------------------------------------+
Namespace ID:
命名空间ID:
ieee
ieee
Registration information:
注册资料：
registration version number: 1
注册版本号：1
registration date: 2016-12-05
注册日期：2016-12-05
Declared registrant of the namespace:
已声明命名空间的注册人：
Registering organization:
注册机构：
Name: Institute of Electrical and Electronics Engineers
名称：电气与电子工程师学会
Address: 445 Hoes Lane Piscataway, NJ 08854 USA
地址：美国新泽西州皮斯卡塔韦霍斯巷445号，邮编：08854
Designated contact person: Angela Thomas Role: Manager, IEEE Registration Authority Email: ieee-registration-authority@ieee.org
指定联系人：Angela Thomas角色：IEEE注册机构经理电子邮件：IEEE注册-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:
使用IEEE NID的所有URN的命名空间特定字符串（NSS）将具有以下结构：
urn:ieee:{IEEEresource}:{ResourceSpecificString}
urn:ieee:{IEEEresource}:{ResourceSpecificString}
where "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 that is covered by "ResourceSpecificString", which also conforms to the naming requirements [RFC2141].
其中，“IEEEresource”是符合URN语法要求[RFC2141]的US-ASCII字符串，并定义资源类型的特定类别。每个资源类型都有一个特定的标签方案，该方案由“ResourceSpecificString”涵盖，它也符合命名要求[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.
IEEE拥有一个注册机构，即IEEE注册机构（IEEE RA），该机构将管理“IEEEresource”的分配以及为每个资源类别分配的特定注册值。
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:
IEEE注册机构（IEEE RA）提供有关注册资源和每个资源的注册的信息。有关此注册表和要遵循的程序的更多信息，请访问：
http://standards.ieee.org/develop/regauth/tut/ieeeurn.pdf
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 associated strings. In the associated procedures, the IEEE RA will ensure the uniqueness of the strings themselves or will permit secondary responsibility for management of well-defined sub-trees.
IEEE RA将使用IEEE NID管理资源，并将是管理资源和后续相关字符串的机构。在相关程序中，IEEE RA将确保字符串本身的唯一性，或允许对定义良好的子树进行二级管理。
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.
IEEE将根据需要更新IEEE NID注册使用的文件。其结构应确保每个“IEEEresource”都有单独的说明和登记表。
The registration tables and information are published and maintained by the IEEE RA on its web site.
注册表和信息由IEEE RA在其网站上发布和维护。
Process of identifier assignment:
标识符分配过程：
IEEE RA will provide procedures for registration of each type of resource that it maintains.
IEEE RA将提供其维护的每种资源类型的注册程序。
Process for identifier resolution:
标识符解析过程：
The namespace is not listed with an RDS; this is not relevant.
名称空间未与RDS一起列出；这是不相关的。
Rules for Lexical Equivalence:
词汇对等规则：
The strings used as values for "IEEEresource" and "ResourceSpecificString" are case insensitive.
用作“IEEEresource”和“ResourceSpecificString”值的字符串不区分大小写。
Conformance with URN Syntax:
符合URN语法：
No special considerations.
没有特别考虑。
Validation mechanism:
验证机制：
None specified. URN assignment will be handled by procedures implemented in support of IEEE activities.
没有具体说明。URN分配将由支持IEEE活动的程序处理。
Scope:
范围：
Global
全球的
The following examples are representative URNs that could be assigned by the IEEE RA. While support for YANG [RFC6020] [RFC7950] was a catalyst for the creation of the namespace, the following are not necessarily the strings that would be assigned.
以下示例是IEEE RA可以分配的代表性URN。虽然对YANG[RFC6020][RFC7950]的支持是创建名称空间的催化剂，但以下内容不一定是要分配的字符串。
urn:ieee:std:802.5:yang
urn:ieee:std:802.5:yang
urn:ieee:foobar
urn:ieee:foobar
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 URNs [RFC1737], URN Syntax [RFC2141], and URN Namespace Definition Mechanisms [RFC3406].
除了通常与URN的使用和解析相关的安全注意事项外，没有其他安全注意事项，如URN的功能要求[RFC1737]、URN语法[RFC2141]和URN命名空间定义机制[RFC3406]中所述。
This document adds "ieee" to the "Formal URN Namespaces" registry <http://www.iana.org/assignments/urn-namespaces>. This is the defining document.
本文档将“ieee”添加到“正式URN名称空间”注册表中<http://www.iana.org/assignments/urn-namespaces>. 这是定义文档。
[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>.
[RFC3406]Daigle，L.，van Gulik，D.，Iannella，R.，和P.Faltstrom，“统一资源名称（URN）命名空间定义机制”，BCP 66，RFC 3406，DOI 10.17487/RFC3406，2002年10月<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>.
[RFC2141]护城河，R.，“瓮语法”，RFC 2141，DOI 10.17487/RFC2141，1997年5月<http://www.rfc-editor.org/info/rfc2141>.
[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>.
[RFC1737]Sollins，K.和L.Masinter，“统一资源名称的功能要求”，RFC 1737，DOI 10.17487/RFC1737，1994年12月<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>.
[RFC6020]Bjorklund，M.，Ed.“YANG-网络配置协议的数据建模语言（NETCONF）”，RFC 6020，DOI 10.17487/RFC6020，2010年10月<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>.
[RFC7950]Bjorklund，M.，Ed.“YANG 1.1数据建模语言”，RFC 7950，DOI 10.17487/RFC7950，2016年8月<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:
IEEE注册机构委员会（RAC）是IEEE注册机构的监督委员会。本文件的内容已与RAC协调。RAC的技术联系人是：
Glenn Parsons Email: glenn.parsons@ericsson.com
格伦·帕森斯电子邮件：格伦。parsons@ericsson.com
Author's Address
作者地址
Angela Thomas IEEE Registration Authority 445 Hoes Lane Piscataway, NJ 08854 USA
美国新泽西州皮斯卡塔韦Hoes Lane 445号Angela Thomas IEEE注册管理局08854
Phone: +1 732 465 6481
Email: a.n.thomas@ieee.org
Phone: +1 732 465 6481
Email: a.n.thomas@ieee.org