Network Working Group M. Abel
Request for Comments: 4729 NFC Forum
Category: Informational November 2006
Network Working Group M. Abel
Request for Comments: 4729 NFC Forum
Category: Informational November 2006
A Uniform Resource Name (URN) Namespace for the Near Field Communication (NFC) Forum
近场通信（NFC）论坛的统一资源名称（URN）命名空间
Status of This Memo
关于下段备忘
This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.
本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The IETF Trust (2006).
版权所有（C）IETF信托基金（2006年）。
Abstract
摘要
This document describes the Namespace Identifier (NID) for Uniform Resource Name (URN) resources published by the Near Field Communication (NFC) Forum. The NFC Forum defines and manages resources that utilize this URN identification model. Management activities for these and other resource types are provided by the NFC Forum Technical Committee.
本文档描述了近场通信（NFC）论坛发布的统一资源名（URN）资源的名称空间标识符（NID）。NFC论坛定义并管理利用此URN标识模型的资源。这些和其他资源类型的管理活动由NFC论坛技术委员会提供。
Table of Contents
目录
1. Introduction ....................................................2
2. URN Specification for "nfc" NID .................................2
3. Examples ........................................................5
4. Namespace Considerations ........................................5
5. Community Considerations ........................................5
6. Security Considerations .........................................6
7. IANA Considerations .............................................6
8. Informative References ..........................................6
Acknowledgments ....................................................6
1. Introduction ....................................................2
2. URN Specification for "nfc" NID .................................2
3. Examples ........................................................5
4. Namespace Considerations ........................................5
5. Community Considerations ........................................5
6. Security Considerations .........................................6
7. IANA Considerations .............................................6
8. Informative References ..........................................6
Acknowledgments ....................................................6
The NFC Forum is a specification development body developing technologies related to near-field communications. This activity is supported by a membership comprised of chip vendors, smart card vendors, equipment vendors, software developers, finance and banking service providers, content providers, and other interested companies.
NFC论坛是一个规范开发机构，开发与近场通信相关的技术。该活动由芯片供应商、智能卡供应商、设备供应商、软件开发商、金融和银行服务提供商、内容提供商和其他感兴趣的公司组成的会员支持。
Some of the technologies being developed by the NFC Forum need namespaces that are managed so that they are unique and persistent. To ensure that the uniqueness is absolute, the registration of a specific NID for use by the NFC Forum was deemed appropriate. Therefore, a full and complete registration will follow the namespace specification process as defined in [RFC3406].
NFC论坛正在开发的一些技术需要管理名称空间，以便它们是唯一和持久的。为了确保唯一性是绝对的，NFC论坛使用特定NID的注册被认为是适当的。因此，完全注册将遵循[RFC3406]中定义的命名空间规范过程。
Namespace ID:
命名空间ID:
nfc
nfc
Registration Information:
注册资料：
Registration version number: 1 Registration date: 2006-05-17
注册版本号：1注册日期：2006-05-17
Declared registrant of the namespace:
已声明命名空间的注册人：
Registering organization Name: Near Field Communication Forum, Inc. Address: 401 Edgewater Place, Suite 600 Wakefield, MA 01880
注册机构名称：近场通信论坛有限公司地址：马萨诸塞州韦克菲尔德600室Edgewater Place 401号01880
Designated contact Role: Technical Program Manager Email: TPM@nfc-forum.org
指定联系人角色：技术项目经理电子邮件：TPM@nfc-论坛
Declaration of syntactic structure:
句法结构声明：
The Namespace Specific String (NSS) of all URNs that use the "nfc" NID will have the following structure:
使用“nfc”NID的所有URN的命名空间特定字符串（NSS）将具有以下结构：
urn:nfc:{NFCresource}:{ResourceSpecificString}
urn:nfc:{NFCresource}:{ResourceSpecificString}
Where the "{NFCresource}" is a US-ASCII string that conforms to the URN syntax requirements [RFC2141] and defines a specific class of resource. Each resource class has a specific labeling scheme
其中，{NFCresource}是一个US-ASCII字符串，它符合URN语法要求[RFC2141]，并定义了一个特定的资源类。每个资源类都有一个特定的标记方案
that is covered by "{ResourceSpecificString}" which also conforms to the naming requirements of [RFC2141].
“{ResourceSpecificString}”涵盖了这一点，它也符合[RFC2141]的命名要求。
NFC Forum working groups will manage the assignment of NFC resources and the specific registration values assigned for each resource class. The Technical Committee will coordinate creation of new resource class assignments based on community need.
NFC论坛工作组将管理NFC资源的分配以及为每个资源类别分配的特定注册值。技术委员会将根据社区需要协调创建新的资源类作业。
Relevant ancillary documentation:
相关辅助文件：
The NFC Forum publishes specifications describing the use of near-field communication for interoperable exchange of information between devices in close proximity. Among these specifications are the designation of new data types, schema, XML elements and attributes, protocols, and other formally named items intended for machine parsing. Interested parties are referred to the NFC Forum web site where these publications will be made available to the community:
NFC论坛发布的规范描述了近场通信的使用，用于近距离设备之间的互操作信息交换。这些规范包括指定新的数据类型、模式、XML元素和属性、协议以及其他用于机器解析的正式命名项。有兴趣的人士请访问NFC论坛网站，该网站将向社区提供这些出版物：
http://www.nfc-forum.org/
http://www.nfc-forum.org/
Identifier uniqueness considerations:
标识符唯一性注意事项：
The NFC Forum working groups and Technical Committee will ensure uniqueness of resource names assigned by the NFC Forum within the resource classes for which they are responsible.
NFC论坛工作组和技术委员会将确保NFC论坛在其负责的资源类别中分配的资源名称的唯一性。
When authority and responsibility for assignment of names with a resource class are delegated to an external organization, commitment to adhere to the uniqueness requirements of the assigned resource names will be a pre-condition of such delegation.
当将资源类名称分配的权力和责任委托给外部组织时，遵守所分配资源名称的唯一性要求的承诺将是此类委托的先决条件。
The structure of the NFC Forum namespace into resource classes will further ensure isolation of names in each class from names in other classes.
NFC论坛名称空间到资源类的结构将进一步确保每个类中的名称与其他类中的名称隔离。
It is anticipated that some resource classes may be open to self-assignment by any interested individual or organization. To ensure a degree of uniqueness for these self-assigned resource names, fully-qualified domain names will be factored into the name to distinguish the naming authorities.
预计某些资源类可能会开放给任何感兴趣的个人或组织自行分配。为确保这些自行分配的资源名称具有一定程度的唯一性，将在名称中加入完全限定的域名，以区分命名机构。
It should be understood that due to the flexibility of the domain name system and the underlying market-based forces that allow for ownership transfer and abandonment of domain names, no guarantee of long-term uniqueness or persistence can be made for this class
应该理解的是，由于域名系统的灵活性以及允许域名所有权转移和放弃的潜在市场力量，无法保证此类域名的长期唯一性或持久性
of resource names beyond that made for the domain names themselves.
除此之外的资源名称的数量为域名本身所做。
Identifier persistence considerations:
标识符持久性注意事项：
The NFC Forum will not reassign names and will thus guarantee the persistence of names beyond the expected lifetime of the named resource. NFC Forum does not anticipate operating a name resolution service for the assigned names and does not anticipate any other usability issues of the assigned names beyond those for any other naturally aging technology.
NFC论坛不会重新分配名称，因此将保证名称的持久性超过指定资源的预期寿命。NFC论坛预计不会为指定的名称运行名称解析服务，也不会预计指定名称的任何其他可用性问题超出任何其他自然老化技术的可用性问题。
Process of identifier assignment:
标识符分配过程：
The NFC Forum will provide procedures for registration of each class of resource that it maintains. Each such resource may have three types of registration activities:
NFC论坛将提供其维护的每类资源的注册程序。每个此类资源可能有三种类型的注册活动：
1) Registered names associated with NFC Forum specifications or
services;
2) Registration of names or resource classes for other entities;
3) Name models for use in experimental purposes.
1) Registered names associated with NFC Forum specifications or
services;
2) Registration of names or resource classes for other entities;
3) Name models for use in experimental purposes.
Process for identifier resolution:
标识符解析过程：
The namespace is not listed with a Resolution Discovery System (RDS); this is not relevant.
名称空间未与解析发现系统（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 and registration will be handled by procedures implemented in support of NFC Forum activities.
没有具体说明。URN分配和注册将按照支持NFC论坛活动的程序进行。
Scope:
范围：
Global
全球的
The following examples are representative URNs that could be assigned by the NFC Forum. They may not be the actual strings that would be assigned:
以下示例是NFC论坛可以分配的代表性URN。它们可能不是要分配的实际字符串：
urn:nfc:wkt:Uri Defines the well-known type identifier used to identify URI bookmark data objects defined by the NFC Forum and exchanged by NFC devices.
urn:nfc:wkt:Uri定义了众所周知的类型标识符，用于标识由nfc论坛定义并由nfc设备交换的Uri书签数据对象。
urn:nfc:schema:manifest Declares an XML namespace for elements and attributes, used in an XML schema to describe an NFC Forum data transfer manifest.
urn:nfc:schema:manifest为元素和属性声明一个XML名称空间，在XML模式中用于描述nfc论坛数据传输清单。
The NFC Forum is developing a variety of communication protocol and data exchange specifications. Some of these specifications depend upon supporting information (e.g., data descriptions, attributes, schema, etc.) to 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 need for namespaces, in one form or another.
NFC论坛正在开发各种通信协议和数据交换规范。其中一些规范取决于要完全指定的支持信息（例如，数据描述、属性、模式等）。对于正确的操作，必须存在所需支持信息的描述，并以独特、可靠和持久的方式提供。这些依赖关系以某种形式提供了名称空间需求的基础。
As type information is relayed across NFC Forum protocols, the need for compact, machine-parsed type identification of data and meta-content, with the attributes of uniqueness and reliability mentioned above, becomes imperative for proper interoperation across widely varied implementations.
由于类型信息是通过NFC论坛协议传递的，因此需要对数据和元内容进行紧凑的、机器解析的类型标识，并具有上述唯一性和可靠性的属性，这对于在各种各样的实现中进行适当的互操作是必不可少的。
As the NFC Forum work is ongoing and covers many technical areas, the possibility of using various other namespace repositories has been deemed impractical. Each data object, description, or schema as defined in the NFC Forum could possibly be related to multiple different other namespaces, so further conflicts of association might occur. Thus, the intent is to utilize the requested URN namespace to manage NFC Forum-defined objects, descriptions, and schema.
由于NFC论坛的工作正在进行中，涵盖了许多技术领域，因此使用各种其他名称空间存储库的可能性被认为是不切实际的。NFC论坛中定义的每个数据对象、描述或模式可能与多个不同的其他名称空间相关，因此可能会发生进一步的关联冲突。因此，目的是利用请求的URN名称空间来管理NFC论坛定义的对象、描述和模式。
The objects and descriptions required for specifications produced and published by the NFC Forum are generally available for use by other organizations. The NFC Forum will provide access and support for name requests by these external organizations. This support can be enabled in a timely and responsive fashion as new objects and descriptions are produced.
NFC论坛制作和发布的规范所需的对象和描述通常可供其他组织使用。NFC论坛将为这些外部组织的名称请求提供访问和支持。随着新对象和描述的产生，这种支持可以以及时和响应的方式启用。
There are no additional security considerations other than those normally associated with the use and resolution of URNs in general.
除了通常与使用和解决骨灰盒相关的安全注意事项外，没有其他安全注意事项。
The requested NID (nfc) has been entered into the IANA registry for URN NIDs.
请求的NID（nfc）已输入到URN NID的IANA注册表中。
[RFC2141] Moats, R., "URN Syntax", RFC 2141, May 1997.
[RFC2141]Moats，R.，“瓮语法”，RFC 21411997年5月。
[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月。
Acknowledgments
致谢
The author wishes to express thanks to Dwight Smith (Motorola) for his guidance on the URN registration process and for providing, by example, a registration that was worthy of emulation.
作者希望感谢德怀特·史密斯（摩托罗拉）对URN注册过程的指导，并举例说明了值得效仿的注册。
Author's Address
作者地址
Miller Abel Technical Committee Delegate, NFC Forum Microsoft Corporation One Microsoft Way Redmond, WA 98052
米勒·阿贝尔技术委员会代表，美国华盛顿州雷德蒙市微软公司NFC论坛一号，邮编：98052
EMail: TPM@nfc-forum.org
EMail: TPM@nfc-forum.org
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2006).
版权所有（C）IETF信托基金（2006年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST, AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件及其包含的信息以“原样”为基础提供，贡献者、他/她所代表或赞助的组织（如有）、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。