Network Working Group A. Mayrhofer
Request for Comments: 4979 enum.at
Category: Standards Track August 2007
Network Working Group A. Mayrhofer
Request for Comments: 4979 enum.at
Category: Standards Track August 2007
IANA Registration for Enumservice 'XMPP'
Enumservice“XMPP”的IANA注册
Status of This Memo
关于下段备忘
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The IETF Trust (2007).
版权所有（C）IETF信托基金（2007年）。
Abstract
摘要
This document requests IANA registration of an Enumservice for XMPP, the Extensible Messaging and Presence Protocol. This Enumservice specifically allows the use of 'xmpp' Uniform Resource Identifiers (URIs) in the context of E.164 Number Mapping (ENUM).
本文档要求IANA注册XMPP的Enumservice，这是一种可扩展的消息和状态协议。此Enumservice特别允许在E.164数字映射（ENUM）上下文中使用“xmpp”统一资源标识符（URI）。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Enumservice Registration - XMPP . . . . . . . . . . . . . . . . 2
4. XMPP IRI/URI Considerations for ENUM . . . . . . . . . . . . . 3
4.1. Authority Component . . . . . . . . . . . . . . . . . . . . 3
4.2. IRI-to-URI mapping . . . . . . . . . . . . . . . . . . . . 3
5. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
6. Security and Privacy Considerations . . . . . . . . . . . . . . 4
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
9.1. Normative References . . . . . . . . . . . . . . . . . . . 5
9.2. Informative References . . . . . . . . . . . . . . . . . . 5
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Enumservice Registration - XMPP . . . . . . . . . . . . . . . . 2
4. XMPP IRI/URI Considerations for ENUM . . . . . . . . . . . . . 3
4.1. Authority Component . . . . . . . . . . . . . . . . . . . . 3
4.2. IRI-to-URI mapping . . . . . . . . . . . . . . . . . . . . 3
5. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
6. Security and Privacy Considerations . . . . . . . . . . . . . . 4
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
9.1. Normative References . . . . . . . . . . . . . . . . . . . 5
9.2. Informative References . . . . . . . . . . . . . . . . . . 5
E.164 Number Mapping (ENUM) [1] uses the Domain Name System (DNS) [6] to refer from E.164 numbers [7] to Uniform Resource Identifiers (URIs) [3]. Specific services to be used with ENUM must be registered with IANA. Section 3 of RFC 3761 describes the process of such an Enumservice registration.
E.164编号映射（ENUM）[1]使用域名系统（DNS）[6]将E.164编号[7]引用到统一资源标识符（URI）[3]。要与ENUM一起使用的特定服务必须向IANA注册。RFC 3761的第3节描述了此类服务注册的过程。
The Extensible Messaging and Presence Protocol (XMPP) [9] provides means for streaming Extensible Markup Language (XML) [8] elements between endpoints in close to real time. The XMPP framework is mainly used to provide instant messaging, presence, and streaming media services.
可扩展消息和状态协议（XMPP）[9]提供了在端点之间近乎实时地流式传输可扩展标记语言（XML）[8]元素的方法。XMPP框架主要用于提供即时消息、状态和流媒体服务。
RFC 4622 [5] registers a Uniform Resource Identifier (URI) scheme for identifying an XMPP entity as a URI or as an Internationalized Resource Identifier (IRI) [4]. The Enumservice specified in this document allows the provisioning of such "xmpp" URIs (and the URI representations of "xmpp" IRIs) in ENUM.
RFC 4622[5]注册了一个统一资源标识符（URI）方案，用于将XMPP实体标识为URI或国际化资源标识符（IRI）[4]。本文档中指定的Enumservice允许在ENUM中提供此类“xmpp”URI（以及“xmpp”IRI的URI表示）。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [2].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[2]中所述进行解释。
The following template contains information required for the IANA registrations of the 'XMPP' Enumservice, according to Section 3 of RFC 3761:
根据RFC 3761第3节，以下模板包含“XMPP”Enumservice的IANA注册所需的信息：
Enumservice Name: "XMPP"
枚举服务名称：“XMPP”
Enumservice Type: "xmpp"
枚举服务类型：“xmpp”
Enumservice Subtype: n/a
枚举服务子类型：不适用
URI Schemes: "xmpp"
URI方案：“xmpp”
Functional Specification:
功能规格：
This Enumservice indicates that the resource identified is an XMPP entity.
此Enumservice表示标识的资源是XMPP实体。
Security Considerations: see Section 6
安全注意事项：见第6节
Intended Usage: COMMON
预期用途：普通
Author: Alexander Mayrhofer <alexander.mayrhofer@enum.at>
Author: Alexander Mayrhofer <alexander.mayrhofer@enum.at>
XMPP IRIs/URIs optionally contain an "Authority Component" (see Section 2.3 of RFC 4622). The presence of such an Authority Component in an IRI/URI signals the processing application to authenticate as the user indicated in the URI/IRI rather than using the preconfigured identity.
XMPP IRIs/URI可选地包含“权限组件”（请参阅RFC 4622的第2.3节）。在IRI/URI中存在这样的授权组件，表示处理应用程序按照URI/IRI中指示的用户进行身份验证，而不是使用预配置的身份。
In the context of this Enumservice, arbitrary clients may discover and use the XMPP URIs/IRIs associated to an E.164 number. Hence, in most cases, those clients will not be able to authenticate as requested in the Authority Component.
在该Enumservice的上下文中，任意客户端可能会发现并使用与E.164号码关联的XMPP URI/IRI。因此，在大多数情况下，这些客户端将无法按照授权组件中的请求进行身份验证。
Therefore, URIs/IRIs that result from processing an XMPP Enumservice record SHOULD NOT contain an Authority Component.
因此，处理XMPP Enumservice记录产生的URI/IRI不应包含权限组件。
While XMPP supports IRIs as well as 'plain' URIs, ENUM itself supports only the use of URIs for Enumservices.
虽然XMPP支持IRIs和“普通”URI，但ENUM本身只支持对ENUM服务使用URI。
Therefore, XMPP IRIs MUST be mapped to URIs for use in an XMPP Enumservice record. The mapping MUST follow the procedures outlined in Section 3.1 of RFC 3987.
因此，XMPP IRI必须映射到URI，以便在XMPP Enumservice记录中使用。映射必须遵循RFC 3987第3.1节中概述的程序。
An example ENUM entry referencing to a XMPP URI could look like:
引用XMPP URI的示例枚举条目如下所示：
$ORIGIN 6.9.4.0.6.9.4.5.1.1.4.4.e164.arpa.
@ IN NAPTR ( 100 10 "u"
"E2U+xmpp"
"!^.*$!xmpp:some-user@example.com!" .
)
$ORIGIN 6.9.4.0.6.9.4.5.1.1.4.4.e164.arpa.
@ IN NAPTR ( 100 10 "u"
"E2U+xmpp"
"!^.*$!xmpp:some-user@example.com!" .
)
General security considerations of the protocols on which this Enumservice registration is based are addressed in Sections 3.1.3 and 6 of RFC 3761 (ENUM) and Section 14 of RFC 3920 (XMPP).
RFC 3761（ENUM）第3.1.3节和第6节以及RFC 3920（XMPP）第14节介绍了此Enumservice注册所基于的协议的一般安全注意事项。
Since ENUM uses DNS -- a publicly available database -- any information contained in records provisioned in ENUM domains must be considered public as well. Even after revoking the DNS entry and removing the referred resource, copies of the information could still be available.
由于ENUM使用DNS（一个公开可用的数据库），所以在ENUM域中提供的记录中包含的任何信息也必须被视为公开的。即使在撤销DNS条目并删除引用的资源后，信息的副本仍然可用。
Information published in ENUM records could reveal associations between E.164 numbers and their owners -- especially if IRIs/URIs contain personal identifiers or domain names for which ownership information can be obtained easily.
ENUM记录中发布的信息可能会揭示E.164号码与其所有者之间的关联——特别是当IRIs/URI包含个人标识符或域名时，可以轻松获取其所有权信息。
However, it is important to note that the ENUM record itself does not need to contain any personal information. It just points to a location where access to personal information could be granted.
但是，需要注意的是，枚举记录本身不需要包含任何个人信息。它只是指向一个可以访问个人信息的位置。
ENUM records pointing to third-party resources can easily be provisioned on purpose by the ENUM domain owner -- so any assumption about the association between a number and an entity could therefore be completely bogus unless some kind of identity verification is in place. This verification is out of scope for this memo.
指向第三方资源的ENUM记录可以很容易地由ENUM域所有者故意提供——因此，任何关于数字和实体之间关联的假设都可能是完全虚假的，除非某种身份验证已经到位。此验证超出此备忘录的范围。
This memo requests IANA to add a new "XMPP" Enumservice to the 'Enumservice Registrations' registry, according to the definitions in this document and RFC 3761 [1].
本备忘录要求IANA根据本文件和RFC 3761[1]中的定义，向“Enumservice Registrations”注册表添加新的“XMPP”Enumservice。
The required template is contained in Section 3.
所需模板包含在第3节中。
Some text from RFC 4622 was used in the Introduction of this document. Charles Clancy, Miguel Garcia, Andrew Newton, Jon Peterson, and Peter Saint-Andre provided extensive reviews and valuable feedback.
本文件介绍中使用了RFC 4622中的一些文本。查尔斯·克兰西、米格尔·加西亚、安德鲁·牛顿、乔恩·彼得森和彼得·圣安德烈提供了广泛的评论和宝贵的反馈。
[1] Faltstrom, P. and M. Mealling, "The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)", RFC 3761, April 2004.
[1] Faltstrom，P.和M.Mealling，“E.164到统一资源标识符（URI）动态委托发现系统（DDDS）应用程序（ENUM）”，RFC 3761，2004年4月。
[2] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[2] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[3] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, January 2005.
[3] Berners Lee，T.，Fielding，R.，和L.Masinter，“统一资源标识符（URI）：通用语法”，STD 66，RFC 3986，2005年1月。
[4] Duerst, M. and M. Suignard, "Internationalized Resource Identifiers (IRIs)", RFC 3987, January 2005.
[4] Duerst，M.和M.Suignard，“国际化资源标识符（IRIs）”，RFC 3987，2005年1月。
[5] Saint-Andre, P., "Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP)", RFC 4622, July 2006.
[5] Saint Andre，P.，“可扩展消息和状态协议（XMPP）的国际化资源标识符（IRI）和统一资源标识符（URI）”，RFC 4622，2006年7月。
[6] Mockapetris, P., "Domain names - implementation and specification", STD 13, RFC 1035, November 1987.
[6] Mockapetris，P.，“域名-实现和规范”，STD 13，RFC 10351987年11月。
[7] ITU-T, "The international public telecommunication numbering plan", Recommendation E.164 (02/05), Feb. 2005.
[7] ITU-T，“国际公共电信编号计划”，建议E.164（02/05），2005年2月。
[8] Maler, E., Paoli, J., Bray, T., Yergeau, F., and C. Sperberg-McQueen, "Extensible Markup Language (XML) 1.0 (Third Edition)", World Wide Web Consortium FirstEdition REC-xml-20040204, February 2004, <http://www.w3.org/TR/2004/REC-xml-20040204>.
[8] Maler，E.，Paoli，J.，Bray，T.，Yergeau，F.，和C.Sperberg McQueen，“可扩展标记语言（XML）1.0（第三版）”，万维网联盟第一版REC-XML-200402042004年2月<http://www.w3.org/TR/2004/REC-xml-20040204>.
[9] Saint-Andre, P., Ed., "Extensible Messaging and Presence Protocol (XMPP): Core", RFC 3920, October 2004.
[9] Saint Andre，P.，Ed.“可扩展消息传递和存在协议（XMPP）：核心”，RFC 3920，2004年10月。
Author's Address
作者地址
Alexander Mayrhofer enum.at GmbH Karlsplatz 1/2/9 Wien A-1010 Austria
Alexander Mayrhofer enum.at GmbH Karlsplatz 1/2/9维也纳A-1010奥地利
Phone: +43 1 5056416 34
EMail: alexander.mayrhofer@enum.at
URI: http://www.enum.at/
Phone: +43 1 5056416 34
EMail: alexander.mayrhofer@enum.at
URI: http://www.enum.at/
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2007).
版权所有（C）IETF信托基金（2007年）。
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编辑功能的资金目前由互联网协会提供。