Internet Engineering Task Force (IETF) B. Rosen
Request for Comments: 6061 NeuStar
Category: Informational January 2011
ISSN: 2070-1721
Internet Engineering Task Force (IETF) B. Rosen
Request for Comments: 6061 NeuStar
Category: Informational January 2011
ISSN: 2070-1721
Uniform Resource Name (URN) Namespace for the National Emergency Number Association (NENA)
国家应急号码协会（NENA）的统一资源名称（URN）命名空间
Abstract
摘要
This document describes the Namespace Identifier (NID) "nena" for Uniform Resource Name (URN) resources published by the National Emergency Number Association (NENA). NENA defines and manages resources that utilize this URN model. Management activities for these and other resource types are provided by the NENA Registry System (NRS).
本文档描述了由国家应急编号协会（nena）发布的统一资源名称（URN）资源的名称空间标识符（NID）“nena”。NENA定义并管理利用此URN模型的资源。这些和其他资源类型的管理活动由NENA注册系统（NRS）提供。
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 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 5741第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/rfc6061.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc6061.
Copyright Notice
版权公告
Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2011 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
2. URN Specification for "nena" NID ................................2
3. Examples ........................................................4
4. Namespace Considerations ........................................5
5. Community Considerations ........................................5
6. Security Considerations .........................................6
7. IANA Considerations .............................................6
8. Acknowledgements ................................................6
9. References ......................................................7
9.1. Normative References .......................................7
9.2. Informative References .....................................7
1. Introduction ....................................................2
2. URN Specification for "nena" NID ................................2
3. Examples ........................................................4
4. Namespace Considerations ........................................5
5. Community Considerations ........................................5
6. Security Considerations .........................................6
7. IANA Considerations .............................................6
8. Acknowledgements ................................................6
9. References ......................................................7
9.1. Normative References .......................................7
9.2. Informative References .....................................7
The National Emergency Number Association (NENA) is currently in the process of setting standards, processes, and procedures for the use of an IP-based Emergency Services IP Network (ESInet) for all public safety entities in North America. Some of the solutions being developed by NENA require XML namespaces that are managed so that they are unique and persistent. To assure that the uniqueness is absolute, the registration of a specific Uniform Resource Name (URN) [RFC2141] Namespace ID (NID) for use by NENA is required. This document defines and registers such a namespace in accordance with [RFC3406].
国家应急号码协会（NENA）目前正在为北美所有公共安全实体制定基于IP的应急服务IP网络（ESInet）的使用标准、流程和程序。NENA正在开发的一些解决方案需要管理XML名称空间，以便它们是唯一和持久的。为了确保唯一性是绝对的，需要注册NENA使用的特定统一资源名（URN）[RFC2141]命名空间ID（NID）。本文件根据[RFC3406]定义并注册了此类名称空间。
Namespace ID: nena
名称空间ID:nena
Registration information:
注册资料：
registration version number: 1
注册版本号：1
registration date: 2010-10-13
注册日期：2010-10-13
Declared registrant of the namespace:
已声明命名空间的注册人：
Registering organization Name: National Emergency Number Association (NENA) Address: 4350 North Fairfax Drive, Suite 750 Arlington, VA 22203-1695
注册机构名称：国家紧急号码协会（NENA）地址：弗吉尼亚州阿灵顿市北费尔法克斯大道4350号750室22203-1695
Designated contact:
指定联系人：
Role: NENA Registry Services Administrator Email: nrs-admin@nena.org
角色：NENA注册服务管理员电子邮件：nrs-admin@nena.org
Declaration of syntactic structure:
句法结构声明：
The Namespace Specific String (NSS) of all URNs that use the
"nena" NID will have the following structure:
{NENAclass}:{ClassSpecificString}
The Namespace Specific String (NSS) of all URNs that use the
"nena" NID will have the following structure:
{NENAclass}:{ClassSpecificString}
The "NENAclass" conforms to the URN syntax requirements [RFC2141] and defines a specific class of resource type. Each class will have a specific labeling scheme that is covered by "ClassSpecificString", which also conforms to the naming requirements of [RFC2141].
“NENAclass”符合URN语法要求[RFC2141]，并定义了资源类型的特定类。每个类都有一个特定的标签方案，该方案包含在“ClassSpecificString”中，它也符合[RFC2141]的命名要求。
NENA maintains a naming authority, the National Emergency Number Association (NENA) Registry System (NRS), that will manage the assignment of "NENAclass" and the specific registration values assigned for each class. Other NENA standards documents will define the "ClassSpecificStrings" for a given "NENAclass".
NENA拥有一个命名机构，即国家应急号码协会（NENA）注册系统（NRS），该系统将管理“NENAclass”的分配以及为每个类别分配的特定注册值。其他NENA标准文档将为给定的“NENAclass”定义“ClassSpecificString”。
Relevant ancillary documentation:
相关辅助文件：
The National Emergency Number Association Registry System (NRS) provides information on the registered resources and the registrations for each. More information about the NRS and the registration activities and procedures to be followed are defined in "NENA Registry System Standard", NENA 70-001 [NENA70-001], which is available at http://www.nena.org/.
国家应急号码协会注册系统（NRS）提供了注册资源的信息以及每个资源的注册信息。有关NRS和注册活动以及要遵循的程序的更多信息，请参见“NENA注册系统标准”，NENA 70-001[NENA70-001]，该标准可在http://www.nena.org/.
Identifier uniqueness considerations:
标识符唯一性注意事项：
The NRS will manage resources using the "nena" NID and will be the authority for managing the resources and subsequent strings associated. The NRS shall ensure the uniqueness of all nena URNs by checking such names against the list of existing namespace names, as documented in NENA 70-001 [NENA70-001].
NRS将使用“nena”NID管理资源，并将成为管理资源和后续相关字符串的机构。NRS应根据nena 70-001[NENA70-001]中记录的现有名称空间名称列表检查所有nena URN的唯一性。
Identifier persistence considerations:
标识符持久性注意事项：
The NRS will provide clear documentation of the registered uses of the "nena" NID. The NRS will establish a registry for "NENAclass", as defined in NENA08-003 [NENA08-003]. Each "NENAclass" will have a separate description in the registry and may have its own sub-registry. In particular, new "NENAclass" registry entries will require a full NENA Technical Standard document.
NRS将提供“nena”NID注册使用的清晰文件。NRS将建立NENA08-003[NENA08-003]中定义的“NENAclass”注册表。每个“NENAclass”在注册表中都有单独的描述，并且可能有自己的子注册表。特别是，新的“NENAclass”注册表项需要完整的NENA技术标准文件。
The NRS will maintain a website at a stable address that provides XML and text renderings of the urn:nena registry.
NRS将在一个稳定的地址维护一个网站，提供urn:nena注册表的XML和文本呈现。
Process of identifier assignment:
标识符分配过程：
The NRS processes and procedures for identifier assignment are documented in NENA 07-001 [NENA70-001]. The registry that will control the urn:nena namespace is defined in NENA 08-003 [NENA08-003]. In particular, assignments to the "NENAclass" registry will require a NENA Technical Standard document. Subregistries for particular "NENAclasses" may be established by such technical standards. Subregistries may be defined to have more liberal management policies as defined in NENA 70-001 [NENA70-001], but must be NRS managed and will not be permitted to be delegated to any other organization or registry. Thus, the NRS will manage the entire urn:nena tree.
NENA 07-001[NENA70-001]中记录了标识分配的NRS流程和程序。nena 08-003[NENA08-003]中定义了控制urn:nena命名空间的注册表。特别是，分配给“NENAclass”注册中心需要一份NENA技术标准文件。可根据此类技术标准建立特定“NENACLASS”的分区域。根据NENA 70-001[NENA70-001]的定义，子区域可能具有更为宽松的管理政策，但必须由NRS管理，且不得委托给任何其他组织或注册机构。因此，NRS将管理整个urn:nena树。
Process for identifier resolution:
标识符解析过程：
The namespace is not currently listed with a Resolution Discovery System (RDS), but nothing about the namespace prohibits the future definition of appropriate resolution methods or listing with an RDS.
名称空间当前未与解析发现系统（RDS）一起列出，但名称空间的任何内容都不禁止将来定义适当的解析方法或与RDS一起列出。
Rules for lexical equivalence:
词汇对等规则：
No special considerations; the rules for lexical equivalence of [RFC2141] apply.
没有特别考虑；[RFC2141]的词汇对等规则适用。
Conformance with URN syntax:
符合URN语法：
No special considerations.
没有特别考虑。
Validation mechanism:
验证机制：
None specified. URN assignment will be handled by procedures implemented in support of NENA activities.
没有具体说明。URN任务将由支持NENA活动的程序执行。
Scope:
范围：
Global
全球的
The following examples are representative URNs that could be assigned by the NRS. They may not be the actual strings that would be assigned.
以下示例是可由NRS分配的代表性URN。它们可能不是要分配的实际字符串。
NENAresource "psaproute" Syntax: "urn:nena:emergencyresponders:<responder name>" ResourceSpecificString: simple string with name of responder, defined in a subregistry Use: Defines the URN to be used for queries to an NG9-1-1 Emergency Call Routing Function that provides URIs for responding agencies.
NENAresource“psaproute”语法：“urn:nena:emergencyresponders:<responder name>”ResourceSpecificString：带有响应者名称的简单字符串，在子区域中定义使用：定义用于查询NG9-1-1紧急呼叫路由函数的urn，该函数为响应机构提供URI。
Examples:
示例：
urn:nena:emergencyresponders:ambulance
urn:nena:emergencyresponders:fire
urn:nena:emergencyresponders:police
urn:nena:emergencyresponders:poison
urn:nena:emergencyresponders:coastguard
urn:nena:emergencyresponders:marine
urn:nena:emergencyresponders:ambulance
urn:nena:emergencyresponders:fire
urn:nena:emergencyresponders:police
urn:nena:emergencyresponders:poison
urn:nena:emergencyresponders:coastguard
urn:nena:emergencyresponders:marine
The National Emergency Number Association has developed standards for emergency calling in North America for several decades. NENA is developing a variety of applications and services using Internet protocols built upon IETF standards. Some of these services require that supporting information (e.g., data descriptions, attributes, etc.) be fully specified. For proper operation, descriptions of the needed supporting information must exist and be available in a unique, reliable, and persistent manner. These dependencies provide the basis of the need for namespaces, in one form or another, and will enable NENA to define URNs that are to assign cleaner, more general, more permanent, more reliable, and more controllable namespace names related to NENA standards, while keeping URNs defined by NENA properly separate from the IETF-defined URNs.
几十年来，美国国家紧急电话号码协会（National Emergency Number Association）制定了北美紧急呼叫标准。NENA正在使用基于IETF标准的互联网协议开发各种应用程序和服务。其中一些服务要求完全指定支持信息（例如，数据描述、属性等）。对于正确的操作，必须存在所需支持信息的描述，并以独特、可靠和持久的方式提供。这些依赖关系以一种或另一种形式提供了名称空间需求的基础，并将使NENA能够定义URN，以分配与NENA标准相关的更干净、更通用、更永久、更可靠和更可控的名称空间名称，同时使NENA定义的URN与IETF定义的URN适当分开。
As the National Emergency Number Association work is ongoing and covers many technical areas, the possibility of binding to various other namespace repositories has been deemed impractical. Each object or description, as defined in NENA, could possibly be related to multiple different namespaces, so further conflicts of association could occur. Thus, the intent is to utilize the National Emergency Number Association Registry System, operated by NENA, as the naming authority for NENA-defined objects and descriptions.
由于国家紧急号码协会的工作正在进行中，涵盖了许多技术领域，因此，将其绑定到各种其他名称空间存储库的可能性被认为是不切实际的。NENA中定义的每个对象或描述可能与多个不同的名称空间相关，因此可能会发生进一步的关联冲突。因此，目的是利用NENA运营的国家应急号码协会登记系统作为NENA定义的对象和描述的命名机构。
The North American public safety organizations will benefit from publication of this namespace by having permanent and reliable URNs to be used with protocols defined by NENA. The objects and descriptions required for services defined by NENA are generally available for use by other organizations. The National Emergency
北美公共安全组织将受益于该名称空间的发布，因为它们拥有永久和可靠的URN，可与NENA定义的协议一起使用。NENA定义的服务所需的对象和描述通常可供其他组织使用。国家紧急情况
Number Association will provide access and support for name requests by these organizations within the constraints of the defined NRS processes and the specific urn:nena registry and subregistries. This support can be enabled in a timely and responsive fashion as new objects and descriptions are produced. These will be enabled in a fashion similar to current IANA processes, as documented in NENA70-001 [NENA70-001].
数字协会将在规定的NRS流程和特定的urn:nena注册和子地区的约束范围内，为这些组织的姓名请求提供访问和支持。随着新对象和描述的产生，这种支持可以以及时和响应的方式启用。如NENA70-001[NENA70-001]所述，这些将以类似于当前IANA流程的方式启用。
The NRS establishes registries when called for in a NENA Technical Standard. Such standards must provide the NRS with clear and concise instructions on creating and maintaining such registries. Defined management policies include "NENA Technical Standard Required", "NENA Document Required", "Expert Review", and "First Come First Served", which correspond to similar IANA management policies. NENA is establishing a website that provides controlled entry of new registries and entries in registries, and automatically produces HTML and XML descriptions of registry contents that are used by vendors and other consumers of the content.
当NENA技术标准要求时，NRS建立登记册。此类标准必须向NRS提供关于创建和维护此类登记册的清晰简明说明。定义的管理政策包括“需要NENA技术标准”、“需要NENA文件”、“专家评审”和“先到先得”，这与类似的IANA管理政策相对应。NENA正在建立一个网站，提供新注册中心和注册中心中的受控条目，并自动生成注册中心内容的HTML和XML描述，供内容的供应商和其他消费者使用。
There are no additional security considerations other than those normally associated with the use and resolution of URNs in general.
除了通常与使用和解决骨灰盒相关的安全注意事项外，没有其他安全注意事项。
This document adds a new entry in the URN Namespaces registry. The namespace is "nena". The defining document is this RFC. The entry can be found in the Uniform Resource Names (URN) Namespaces registry available from http://www.iana.org and any associated mirrors.
此文档在URN名称空间注册表中添加一个新条目。名称空间是“nena”。定义文档就是这个RFC。该项可以在统一资源名称（URN）命名空间注册表中找到，该注册表可从http://www.iana.org 以及任何相关的镜子。
The author thanks Alfred Hoenes (TR-Sys) for his careful reading and extensive comments and suggestions. The author also acknowledges that the text from [RFC4358] formed the basis of this document.
作者感谢Alfred Hoenes（TR Sys）的仔细阅读和广泛的评论和建议。作者还承认，[RFC4358]中的文本构成了本文件的基础。
[RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997.
[RFC2141]Moats，R.，“瓮语法”，RFC 21411997年5月。
[NENA08-003] NENA, "Detailed Functional and Interface Specification for the NENA i3 Solution - Stage 3", NENA Standard 08-003, September 2010.
[NENA08-003]NENA，“NENA i3解决方案的详细功能和接口规范-第3阶段”，NENA标准08-003，2010年9月。
[NENA70-001] NENA, "NENA Registry System Standard", NENA Standard 70-001, September 2009.
[NENA70-001]NENA，“NENA注册系统标准”，NENA标准70-001，2009年9月。
[RFC3406] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, "Uniform Resource Names (URN) Namespace Definition Mechanisms", BCP 66, RFC 3406, October 2002.
[RFC3406]Daigle，L.，van Gulik，D.，Iannella，R.，和P.Faltstrom，“统一资源名称（URN）命名空间定义机制”，BCP 66，RFC 3406，2002年10月。
[RFC4358] Smith, D., "A Uniform Resource Name (URN) Namespace for the Open Mobile Alliance (OMA)", RFC 4358, January 2006.
[RFC4358]Smith，D.“开放移动联盟（OMA）的统一资源名（URN）命名空间”，RFC 4358，2006年1月。
Author's Address
作者地址
Brian Rosen NeuStar, Inc. 470 Conrad Dr. Mars, PA 16046 US
布莱恩·罗森·纽斯塔公司，美国宾夕法尼亚州康拉德·马尔斯博士，邮编：16046
EMail: br@brianrosen.net
EMail: br@brianrosen.net