Network Working Group P. Saint-Andre
Request for Comments: 4854 XSF
Category: Informational April 2007
Network Working Group P. Saint-Andre
Request for Comments: 4854 XSF
Category: Informational April 2007
A Uniform Resource Name (URN) Namespace for Extensions to the Extensible Messaging and Presence Protocol (XMPP)
用于扩展消息和状态协议（XMPP）扩展的统一资源名称（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 (2007).
版权所有（C）IETF信托基金（2007年）。
Abstract
摘要
This document describes a Uniform Resource Name (URN) namespace for uniquely identifying Extensible Markup Language (XML) formats and protocols that provide extensions to the Extensible Messaging and Presence Protocol (XMPP) and are defined in specifications published by the XMPP Standards Foundation (XSF).
该文档描述了一种统一资源名称（URN）命名空间，用于唯一标识可扩展标记语言（XML）格式和协议，该协议提供可扩展消息和存在协议（XMPP）的扩展，并在XMPP标准基金会（XSF）公布的规范中定义。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Specification Template . . . . . . . . . . . . . . . . . . . . 3
3. Namespace Considerations . . . . . . . . . . . . . . . . . . . 6
4. Community Considerations . . . . . . . . . . . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
7.1. Normative References . . . . . . . . . . . . . . . . . . . 8
7.2. Informative References . . . . . . . . . . . . . . . . . . 8
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Specification Template . . . . . . . . . . . . . . . . . . . . 3
3. Namespace Considerations . . . . . . . . . . . . . . . . . . . 6
4. Community Considerations . . . . . . . . . . . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
7.1. Normative References . . . . . . . . . . . . . . . . . . . 8
7.2. Informative References . . . . . . . . . . . . . . . . . . 8
While the Extensible Messaging and Presence Protocol (XMPP), as specified in [XMPP-CORE] and [XMPP-IM], provides basic messaging and presence functionality, the fact that XMPP is at root a technology for streaming Extensible Markup Language [XML] data makes it possible to include virtually any structured information within XMPP, as long as such information is qualified by appropriate XML namespaces [XML-NAMES]. When sent over XMPP, such structured data formats and protocols are generally referred to as "XMPP extensions".
虽然[XMPP-CORE]和[XMPP-IM]中规定的可扩展消息和状态协议（XMPP）提供了基本的消息和状态功能，但事实上XMPP是一种流式传输可扩展标记语言[XML]数据的技术，这使得在XMPP中包含几乎任何结构化信息成为可能，只要这些信息由适当的XML名称空间[XML-NAMES]限定。当通过XMPP发送时，这种结构化数据格式和协议通常被称为“XMPP扩展”。
A large number of such XMPP extensions exist. The main standards development organization in which such extensions are defined is the XMPP Standards Foundation (XSF) (formerly the Jabber Software Foundation), which contributed XMPP to the Internet Standards process. Typically, such extensions are defined within the XSF's XMPP Extension Protocol (XEP) specification series. To date, the XML namespaces defined within the Jabber/XMPP community have used names of the form "jabber:*" (deprecated since early 2002) and "http://jabber.org/protocol/*" (not including names of the form "urn:ietf:params:xml:ns:xmpp-*" specified in the XMPP RFCs). However, it is desirable that names associated with future XMPP extensions be both unique and persistent, which is not necessarily the case with names that are also HTTP URLs. Therefore, in accordance with the process defined in [MECHANISMS], this document registers a formal namespace identifier (NID) for Uniform Resource Names [URN] associated with XMPP extensions published in the XSF's XEP series and for XML namespaces registered with the XSF's XMPP Registrar function [REGISTRAR].
存在大量这样的XMPP扩展。定义此类扩展的主要标准开发组织是XMPP标准基金会（XSF）（以前是JabBER软件基金会），它向互联网标准进程贡献XMPP。通常，此类扩展是在XSF的XMPP扩展协议（XEP）规范系列中定义的。到目前为止，Jabber/XMPP社区中定义的XML名称空间使用了形式为“Jabber:*（自2002年初以来就不推荐）和”的名称http://jabber.org/protocol/*“（不包括xmpp RFC中指定的格式“urn:ietf:params:xml:ns:xmpp-*”的名称）。然而，与未来的XMPP扩展相关联的名称应该是唯一的和持久的，这对于同样是HTTP URL的名称来说不一定是这样。因此，根据[Mechaniss]中定义的过程，本文档为与XSF的XEP系列中发布的XMPP扩展相关联的统一资源名[URN]以及使用XSF的XMPP注册器函数[Registrar]注册的XML命名空间注册一个正式的命名空间标识符（NID）。
Namespace ID:
命名空间ID:
The Namespace ID "xmpp" is requested.
请求名称空间ID“xmpp”。
Registration Information:
注册资料：
Version 1 Date: 2007-04-27
版本1日期：2007-04-27
Declared Registrant of the Namespace:
已声明命名空间的注册人：
Registering organization Organization: XMPP Standards Foundation Address: P.O. Box 1641, Denver, CO 80201 USA
注册组织机构：XMPP标准基金会地址：CO丹佛市邮政信箱1641号，美国80201
Designated contact Role: XMPP Registrar Email: registrar@xmpp.org
指定联系人角色：XMPP注册者电子邮件：registrar@xmpp.org
Declaration of Syntactic Structure:
句法结构声明：
The Namespace Specific String (NSS) of all URNs that use the "xmpp" NID shall have the following structure:
使用“xmpp”NID的所有URN的命名空间特定字符串（NSS）应具有以下结构：
urn:xmpp:{ShortName}:{SubName}
urn:xmpp:{ShortName}:{SubName}
The keywords have the following meaning:
这些关键字具有以下含义：
(1) the "ShortName" is a required US-ASCII string that conforms to the URN syntax requirements (see RFC 2141) and defines a particular protocol or format that is used as an XMPP extension.
(1) “ShortName”是一个必需的US-ASCII字符串，它符合URN语法要求（请参见RFC 2141），并定义了用作XMPP扩展的特定协议或格式。
(2) the "SubName" is an optional US-ASCII string that conforms to the URN syntax requirements (see RFC 2141) and defines a particular subset of the relevant protocol or format.
(2) “子名称”是一个可选的US-ASCII字符串，符合URN语法要求（请参阅RFC 2141），并定义相关协议或格式的特定子集。
The XSF's XMPP Registrar function shall be responsible for managing the assignment of both "ShortName" and "SubName" strings and maintaining a registry of resulting namespaces at <http://www.xmpp.org/registrar/namespaces.html>. The XMPP Registrar may also assign URNs in sub-trees below the level of the ShortName or SubName as needed for use in various XMPP extensions.
XSF的XMPP注册器功能应负责管理“ShortName”和“SubName”字符串的分配，并在<http://www.xmpp.org/registrar/namespaces.html>. XMPP注册器还可以根据需要在短名称或子名称级别下的子树中分配URN，以用于各种XMPP扩展。
Relevant Ancillary Documentation:
相关辅助文件：
Information about the XSF's XMPP Registrar function can be found at <http://www.xmpp.org/extensions/xep-0053.html> and <http://www.xmpp.org/registrar/>.
有关XSF的XMPP注册器函数的信息，请访问<http://www.xmpp.org/extensions/xep-0053.html>及<http://www.xmpp.org/registrar/>.
Identifier Uniqueness Considerations:
标识符唯一性注意事项：
The XMPP Registrar is already responsible for managing
the assignment of XML namespace names of the form
"http://jabber.org/protocol/{ShortName}" and
"http://jabber.org/protocol/{ShortName}#{SubName}"
(e.g., "http://jabber.org/protocol/pubsub" and
"http://jabber.org/protocol/disco#info"). In order to
assign namespace names in the context of the "xmpp"
NID, the XMPP Registrar shall simply modify the syntax
of the namespace names it assigns from
The XMPP Registrar is already responsible for managing
the assignment of XML namespace names of the form
"http://jabber.org/protocol/{ShortName}" and
"http://jabber.org/protocol/{ShortName}#{SubName}"
(e.g., "http://jabber.org/protocol/pubsub" and
"http://jabber.org/protocol/disco#info"). In order to
assign namespace names in the context of the "xmpp"
NID, the XMPP Registrar shall simply modify the syntax
of the namespace names it assigns from
"http://jabber.org/protocol/{ShortName}" and "http://jabber.org/protocol/{ShortName}#{SubName}" to "urn:xmpp:{ShortName}" and "urn:xmpp:{ShortName}:{SubName}".
"http://jabber.org/protocol/{ShortName}“和”http://jabber.org/protocol/{ShortName}{SubName}改为“urn:xmpp:{ShortName}”和“urn:xmpp:{ShortName}:{SubName}”。
The XMPP Registrar shall ensure the uniqueness of all XMPP URNs by checking such names against the list of existing namespace names, as documented in XEP-0053 (the controlling specification for the XMPP Registrar function). The XMPP Registrar shall, in all cases, directly ensure the uniqueness of the assigned strings and shall not assign secondary responsibility for management of any sub-trees. However, the XMPP Registrar may assign URNs in sub-trees below the level of the ShortName or SubName as needed for use in various XMPP extensions. The resulting URNs shall not be re-assigned.
XMPP注册器应通过对照XEP-0053（XMPP注册器功能的控制规范）中记录的现有命名空间名称列表检查这些名称，确保所有XMPP URN的唯一性。在所有情况下，XMPP注册员应直接确保指定字符串的唯一性，且不得指定任何子树管理的次要责任。但是，XMPP注册器可以根据需要在短名称或子名称级别下的子树中分配URN，以便在各种XMPP扩展中使用。产生的骨灰盒不得重新分配。
Identifier Persistence Considerations:
标识符持久性注意事项：
The XMPP Registrar shall provide clear documentation of the registered uses of the "xmpp" NID in the form of XMPP Extension Protocol (XEP) specifications published at <http://www.xmpp.org/extensions/>, as well as a registry of the namespace names themselves at <http://www.xmpp.org/registrar/namespaces.html>.
XMPP注册官应以XMPP扩展协议（XEP）规范的形式提供“XMPP”NID注册使用的清晰文件，该规范发布于<http://www.xmpp.org/extensions/>，以及命名空间名称本身的注册表<http://www.xmpp.org/registrar/namespaces.html>.
Process of Identifier Assignment:
标识符分配过程：
The XMPP Registrar's processes and procedures for identifier assignment are documented in XEP-0053, which is the controlling specification for the XMPP Registrar function. In particular, identifiers shall be issued only upon advancement of the relevant protocol specification to a status of Draft within the standards process, followed by the XMPP Standards Foundation (as specified in XEP-0001). The XMPP Registrar shall check all identifiers against the list of existing namespace names to ensure uniqueness and to encourage relevance and memorability. Assignment of URNs within the "xmpp" tree is reserved to the XMPP Standards Foundation, specifically to its XMPP Registrar function.
XMPP注册器的标识符分配过程和程序记录在XEP-0053中，XEP-0053是XMPP注册器功能的控制规范。特别是，标识符只有在相关协议规范进展到标准过程中的草案状态之后，然后是XMPP标准基金会（XEP—001中规定）才发布。XMPP注册员应对照现有名称空间名称列表检查所有标识符，以确保唯一性，并鼓励相关性和可记忆性。在“XMPP”树中指派URN保留给XMPP标准基金会，特别是其XMPP注册功能。
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 specified in RFC 2141 apply.
没有特别考虑；RFC 2141中规定的词汇等价规则适用。
Conformance with URN Syntax:
符合URN语法：
No special considerations.
没有特别考虑。
Validation Mechanism:
验证机制：
None specified.
没有具体说明。
Scope:
范围：
Global.
全球的
The XMPP Standards Foundation has been developing Internet protocols since August 2001 and that work is expected to continue for the foreseeable future. The old-style "jabber:*" namespace names originally used in the Jabber open-source community were not proper URNs or URIs and thus were deprecated in early 2002. Since then, the namespace names assigned by the XMPP Registrar function of the XMPP Standards Foundation have been (equivalent to) specialized HTTP URLs whose authority component is "jabber.org". While that domain is currently under the control of the XMPP Standards Foundation, there is no guarantee that it will always remain so, thus potentially threatening the reliability and permanence of the assigned namespace names. The use of Uniform Resource Names with an appropriate Namespace ID will enable the XMPP Standards Foundation to assign cleaner, more general, more permanent, more reliable, and more controllable namespace names related to the XMPP extensions it defines, while keeping the tree of XMPP extensions produced by the XMPP Standards Foundation properly separate from the IETF tree used to define some of the core XMPP namespaces as well as namespaces related to XMPP extensions that may be produced in the future by the IETF.
XMPP标准基金会自2001年8月以来一直在开发互联网协议，预计工作将在可预见的将来继续进行。jabber开源社区最初使用的旧式“jabber:*”命名空间名称不是合适的URN或URI，因此在2002年初被弃用。从那时起，XMPP标准基金会的XMPP注册函数分配的命名空间名称已经相当于专门的HTTP URL，其授权组件是“Jabb.org”。虽然该域目前处于XMPP标准基金会的控制之下，但不能保证它始终保持这样，因此可能威胁指定的命名空间名称的可靠性和持久性。使用具有适当命名空间ID的统一资源名称将使XMPP标准基金会指派与它定义的XMPP扩展相关的更干净、更一般、更持久、更可靠和更可控的命名空间名称，在保持XMPP标准基金会产生的XMPP扩展树的基础上，正确地分离了用于定义一些核心XMPP命名空间的IETF树以及将来可能由IETF生成的与XMPP扩展相关的命名空间。
The XMPP standards development community will benefit from publication of this namespace by having more permanent and reliable names for the XML namespaces defined in XMPP Extension Protocol specifications produced by the XMPP Standards Foundation.
XMPP标准开发社区将通过对XMPP标准基金会产生的XMPP扩展协议规范中定义的XML命名空间拥有更持久和可靠的名称来受益于此命名空间的发布。
The standards process followed by the XSF is open to contributions from any interested individual; such a contribution takes the form of a proposal submitted to the XMPP Extensions Editor <mailto:editor@xmpp.org>, accepted by the XMPP Council <http://www.xmpp.org/council/>, and published in the XSF's XMPP Extension Protocol (XEP) series at <http://www.xmpp.org/extensions/>. Use of the proposed space for a particular XML format or protocol extension will be contingent upon advancement of the appropriate specification within the XSF's standards process (as documented in [XEP]) and issuance of a namespace name within the "xmpp" tree by the XMPP Registrar (as documented in [REGISTRAR]).
XSF遵循的标准过程对任何感兴趣的个人都是开放的；这种贡献的形式是提交给XMPP扩展编辑器的提案<mailto:editor@xmpp.org>，被XMPP委员会接受<http://www.xmpp.org/council/>，并发表在XSF的XMPP扩展协议（XEP）系列中<http://www.xmpp.org/extensions/>. 将提议的空间用于特定XML格式或协议扩展将取决于XSF标准过程中适当规范的推进（如[XEP]中所述）以及xmpp注册者在“xmpp”树中发布名称空间名称（如[Register]中所述）。
This document introduces no additional security considerations beyond those associated with the use and resolution of URNs in general.
本文档除了介绍与一般URN的使用和解析相关的安全注意事项外，没有介绍其他安全注意事项。
This document defines a URN NID registration of "xmpp", which has been entered into the IANA registry located at <http://www.iana.org/assignments/urn-namespaces>.
本文档定义了“xmpp”的URN NID注册，该注册已输入位于<http://www.iana.org/assignments/urn-namespaces>.
[MECHANISMS] Daigle, L., van Gulik, D., Iannella, R., and P. Faltstrom, "Uniform Resource Names (URN) Namespace Definition Mechanisms", BCP 66, RFC 3406, October 2002.
[机制]Daigle，L.，van Gulik，D.，Iannella，R.，和P.Faltstrom，“统一资源名称（URN）命名空间定义机制”，BCP 66，RFC 3406，2002年10月。
[URN] Moats, R., "URN Syntax", RFC 2141, May 1997.
[瓮]护城河，右，“瓮语法”，RFC 21411997年5月。
[REGISTRAR] Saint-Andre, P., "XMPP Registrar Function", XSF XEP 0053, December 2006.
[注册官]圣安德烈，P.，“XMPP注册官职能”，XSF XEP 0053，2006年12月。
[XEP] Saint-Andre, P., "XMPP Extension Protocols", XSF XEP 0001, December 2006.
[XEP]圣安德烈，P.，“XMPP扩展协议”，XSF XEP 0001，2006年12月。
[XML] Bray, T., Paoli, J., Sperberg-McQueen, C., and E. Maler, "Extensible Markup Language (XML) 1.0 (2nd ed)", W3C REC-xml, October 2000, <http://www.w3.org/TR/REC-xml>.
[XML]Bray，T.，Paoli，J.，Sperberg McQueen，C.，和E.Maler，“可扩展标记语言（XML）1.0（第二版）”，W3C REC XML，2000年10月<http://www.w3.org/TR/REC-xml>.
[XML-NAMES] Bray, T., Hollander, D., and A. Layman, "Namespaces in XML", W3C REC-xml-names, January 1999, <http://www.w3.org/TR/REC-xml-names>.
[XML-NAMES]Bray，T.，Hollander，D.，和A.Layman，“XML中的名称空间”，W3C REC XML名称，1999年1月<http://www.w3.org/TR/REC-xml-names>.
[XMPP-CORE] Saint-Andre, P., "Extensible Messaging and Presence Protocol (XMPP): Core", RFC 3920, October 2004.
[XMPP-CORE]Saint Andre，P.，“可扩展消息和状态协议（XMPP）：CORE”，RFC 3920，2004年10月。
[XMPP-IM] Saint-Andre, P., "Extensible Messaging and Presence Protocol (XMPP): Instant Messaging and Presence", RFC 3921, October 2004.
[XMPP-IM]Saint Andre，P.，“可扩展消息和状态协议（XMPP）：即时消息和状态”，RFC 39212004年10月。
Author's Address
作者地址
Peter Saint-Andre XMPP Standards Foundation P.O. Box 1641 Denver, CO 80201 USA
彼得圣安德烈XMPP标准基金会邮政信箱1641丹佛，CO 80201美国
EMail: stpeter@jabber.org
URI: xmpp:stpeter@jabber.org
EMail: stpeter@jabber.org
URI: xmpp:stpeter@jabber.org
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编辑功能的资金目前由互联网协会提供。