Internet Engineering Task Force (IETF) S. Kille
Request for Comments: 8284 Isode Ltd
Category: Informational November 2017
ISSN: 2070-1721
Internet Engineering Task Force (IETF) S. Kille
Request for Comments: 8284 Isode Ltd
Category: Informational November 2017
ISSN: 2070-1721
Lightweight Directory Access Protocol (LDAP) Schema for Supporting the Extensible Messaging and Presence Protocol (XMPP) in White Pages
轻量级目录访问协议（LDAP）架构，用于支持白页中的可扩展消息和状态协议（XMPP）
Abstract
摘要
The Extensible Messaging and Presence Protocol (XMPP) identifies users by use of Jabber IDs (JIDs). The Lightweight Directory Access Protocol (LDAP) enables provision of a white pages service with a schema relating to users and support for Internet protocols. This specification defines a schema to enable XMPP JIDs to be associated with objects in an LDAP directory so that this information can be used with white pages applications.
可扩展消息和状态协议（XMPP）通过使用Jabber ID（JID）识别用户。轻量级目录访问协议（LDAP）支持使用与用户相关的模式提供白页服务，并支持Internet协议。该规范定义了一个模式，使XMPP JID能够与LDAP目录中的对象相关联，以便将此信息用于白页应用程序。
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 https://www.rfc-editor.org/info/rfc8284.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问https://www.rfc-editor.org/info/rfc8284.
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 (https://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文件的法律规定的约束(https://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions Used in This Document . . . . . . . . . . . . . . 3
3. Schema Definition . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Object Class . . . . . . . . . . . . . . . . . . . . . . 3
3.2. Attribute . . . . . . . . . . . . . . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. Normative References . . . . . . . . . . . . . . . . . . . . 5
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions Used in This Document . . . . . . . . . . . . . . 3
3. Schema Definition . . . . . . . . . . . . . . . . . . . . . . 3
3.1. Object Class . . . . . . . . . . . . . . . . . . . . . . 3
3.2. Attribute . . . . . . . . . . . . . . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. Normative References . . . . . . . . . . . . . . . . . . . . 5
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
Extensible Messaging and Presence Protocol (XMPP) [RFC6120] identifies users by use of Jabber IDs (JIDs). The Lightweight Directory Access Protocol (LDAP) [RFC4510] enables provision of a white pages service with a schema relating to users and support for Internet protocols defined in [RFC4519]. This specification defines a schema to enable XMPP JIDs to be associated with LDAP directory objects so that this information can be used with white pages applications.
可扩展消息和状态协议（XMPP）[RFC6120]通过使用Jabber ID（JID）识别用户。轻量级目录访问协议（LDAP）[RFC4510]支持提供白页服务，其模式与用户相关，并支持[RFC4519]中定义的互联网协议。该规范定义了一个模式，使XMPP JID能够与LDAP目录对象相关联，以便将此信息用于白页应用程序。
The LDAP schema for storing JIDs is defined to enable JIDs to be associated with any object stored in the directory. This is done by associating the new JID Attribute with a new Auxiliary Object Class called JIDObject.
用于存储JID的LDAP模式被定义为允许JID与目录中存储的任何对象相关联。这是通过将新的JID属性与名为JIDObject的新辅助对象类相关联来实现的。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“建议”、“不建议”、“可”和“可选”在所有大写字母出现时（如图所示）应按照BCP 14[RFC2119][RFC8174]所述进行解释。
This section defines the schema used to store JIDs in the directory.
本节定义用于在目录中存储JID的模式。
This section defines a new Auxiliary Object Class called JIDObject, which MAY be associated with any structural Object Class. This Object Class is used to augment entries for objects that act or may act as an XMPP client. The JID attribute is optional in order to enable configuring an object that is allowed to have an associated JID but does not currently have one.
本节定义了一个名为JIDObject的新辅助对象类，它可以与任何结构对象类相关联。此对象类用于为充当或可能充当XMPP客户端的对象增加条目。JID属性是可选的，以便能够配置允许有关联JID但当前没有关联JID的对象。
( 1.3.6.1.1.23.1 NAME 'JIDObject' AUXILIARY MAY jid )
（1.3.6.1.1.23.1名称“JIDObject”辅助可能jid）
This section defines the JID attribute referenced by the JIDObject Auxiliary Object Class. The syntax of the JID attribute MUST follow the rules of [RFC7622]. The JID stored MUST be a bare JID (e.g., a JID such as romeo@shakespeare.example.com representing a human user) and not a full JID (e.g., a JID such as romeo@shakespare.example.com/AABBCC, which represents a specific XMPP client used by the human user and is identified by the resource AABBCC). Note that the LDAP directory server is not expected to enforce this syntax. The syntax rules are for LDAP clients setting this attribute, noting that human usage is a key target. Applications using this attribute should format that string in a manner appropriate to the application, and XMPP applications SHOULD apply [RFC7622] to the attribute. The directory service doesn't enforce the JID syntax, and values are compared according to the matching rules specified in the attribute definition.
本节定义JIDObject辅助对象类引用的JID属性。JID属性的语法必须遵循[RFC7622]的规则。存储的JID必须是裸JID（例如，JID，例如romeo@shakespeare.example.com表示人类用户）而不是完整的JID（例如，JID，如romeo@shakespare.example.com/AABBCC，表示人工用户使用的特定XMPP客户端，由资源（AABBCC）标识。请注意，LDAP目录服务器不应强制执行此语法。语法规则用于LDAP客户端设置此属性，注意人的使用是一个关键目标。使用此属性的应用程序应以适合应用程序的方式格式化该字符串，XMPP应用程序应将[RFC7622]应用于该属性。目录服务不强制执行JID语法，并根据属性定义中指定的匹配规则对值进行比较。
Note that for the convenience of users and administrators as well as implementers, the Directory String syntax and the caseIgnoreMatch matching rule are chosen to allow entry and matching of values according to common rules used within the directory. As this syntax and matching rule differ from [RFC7622], false positives and false
请注意，为了方便用户和管理员以及实现者，选择了目录字符串语法和caseIgnoreMatch匹配规则，以允许根据目录中使用的通用规则输入和匹配值。由于此语法和匹配规则与[RFC7622]不同，因此会出现误报和误报
negatives can possibly occur. This is not anticipated to cause operational issues (based on implementation experience with similar syntax/matching rule mismatches).
可能会出现负面影响。这不会导致操作问题（基于类似语法/匹配规则不匹配的实现经验）。
( 1.3.6.1.1.23.2 NAME 'jid' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 )
（1.3.6.1.1.23.2名称“jid”相等caseIgnoreMatch SUBSTR caseIgnoreMatch语法1.3.6.1.4.1.1466.115.121.1.15）
1.3.6.1.4.1.1466.115.121.1.15 refers to the Directory String syntax defined in [RFC4517].
1.3.6.1.4.1.1466.115.121.1.15是指[RFC4517]中定义的目录字符串语法。
The following registrations have been made in the "Lightweight Directory Access Protocol (LDAP) Parameters" registry <https://www.iana.org/assignments/ldap-parameters> in line with BCP 64 [RFC4520].
在“轻量级目录访问协议（LDAP）参数”注册表中进行了以下注册<https://www.iana.org/assignments/ldap-parameters>符合BCP 64[RFC4520]的要求。
Object Identifier Registration
对象标识符注册
An object identifier has been assigned to support the registrations necessary for this specification by an entry in the Internet Directory Numbers (iso.org.dod.internet.directory [1.3.6.1.1.]) registry:
已通过互联网目录编号（iso.org.dod.Internet.Directory[1.3.6.1.1.]）注册表中的条目分配了一个对象标识符，以支持本规范所需的注册：
Decimal: 23 Name: xmpp Description: LDAP schema for XMPP
十进制：23名称：xmpp说明：xmpp的LDAP模式
Two object identifiers have been assigned:
已分配两个对象标识符：
'JIDObject' Descriptor Registration
“JIDObject”描述符注册
Name: JIDObject Type: O OID: 1.3.6.1.1.23.1
名称：JIDObject类型：O OID:1.3.6.1.1.23.1
'jid' Descriptor Registration
“jid”描述符注册
Name: jid Type: A OID: 1.3.6.1.1.23.2
名称：jid类型：A OID:1.3.6.1.1.23.2
XMPP JIDs are often personal identifiers enabling electronic communication and have similar considerations to email addresses. This schema enables publishing of this information in LDAP directories, which may be corporate or public services. Care should be taken to only publish JID information that is acceptable both to be linked to the LDAP object and to be made accessible to all LDAP users. The general LDAP security considerations specified in [RFC4510] also apply.
XMPP JID通常是支持电子通信的个人标识符，与电子邮件地址具有类似的考虑因素。此模式允许在LDAP目录中发布此信息，LDAP目录可以是公司或公共服务。应注意仅发布链接到LDAP对象并可供所有LDAP用户访问的JID信息。[RFC4510]中规定的一般LDAP安全注意事项也适用。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <https://www.rfc-editor.org/info/rfc2119>.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，DOI 10.17487/RFC2119，1997年3月<https://www.rfc-editor.org/info/rfc2119>.
[RFC4510] Zeilenga, K., Ed., "Lightweight Directory Access Protocol (LDAP): Technical Specification Road Map", RFC 4510, DOI 10.17487/RFC4510, June 2006, <https://www.rfc-editor.org/info/rfc4510>.
[RFC4510]Zeilenga，K.，Ed.“轻量级目录访问协议（LDAP）：技术规范路线图”，RFC 4510，DOI 10.17487/RFC4510，2006年6月<https://www.rfc-editor.org/info/rfc4510>.
[RFC4517] Legg, S., Ed., "Lightweight Directory Access Protocol (LDAP): Syntaxes and Matching Rules", RFC 4517, DOI 10.17487/RFC4517, June 2006, <https://www.rfc-editor.org/info/rfc4517>.
[RFC4517]Legg，S.，编辑，“轻量级目录访问协议（LDAP）：语法和匹配规则”，RFC 4517，DOI 10.17487/RFC4517，2006年6月<https://www.rfc-editor.org/info/rfc4517>.
[RFC4519] Sciberras, A., Ed., "Lightweight Directory Access Protocol (LDAP): Schema for User Applications", RFC 4519, DOI 10.17487/RFC4519, June 2006, <https://www.rfc-editor.org/info/rfc4519>.
[RFC4519]Sciberras，A.，Ed.，“轻量级目录访问协议（LDAP）：用户应用程序模式”，RFC 4519，DOI 10.17487/RFC4519，2006年6月<https://www.rfc-editor.org/info/rfc4519>.
[RFC4520] Zeilenga, K., "Internet Assigned Numbers Authority (IANA) Considerations for the Lightweight Directory Access Protocol (LDAP)", BCP 64, RFC 4520, DOI 10.17487/RFC4520, June 2006, <https://www.rfc-editor.org/info/rfc4520>.
[RFC4520]Zeilenga，K.，“轻量级目录访问协议（LDAP）的互联网分配号码管理局（IANA）注意事项”，BCP 64，RFC 4520，DOI 10.17487/RFC4520，2006年6月<https://www.rfc-editor.org/info/rfc4520>.
[RFC6120] Saint-Andre, P., "Extensible Messaging and Presence Protocol (XMPP): Core", RFC 6120, DOI 10.17487/RFC6120, March 2011, <https://www.rfc-editor.org/info/rfc6120>.
[RFC6120]Saint Andre，P.，“可扩展消息和状态协议（XMPP）：核心”，RFC 6120，DOI 10.17487/RFC6120，2011年3月<https://www.rfc-editor.org/info/rfc6120>.
[RFC7622] Saint-Andre, P., "Extensible Messaging and Presence Protocol (XMPP): Address Format", RFC 7622, DOI 10.17487/RFC7622, September 2015, <https://www.rfc-editor.org/info/rfc7622>.
[RFC7622]Saint Andre，P.，“可扩展消息和状态协议（XMPP）：地址格式”，RFC 7622，DOI 10.17487/RFC7622，2015年9月<https://www.rfc-editor.org/info/rfc7622>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, May 2017, <https://www.rfc-editor.org/info/rfc8174>.
[RFC8174]Leiba，B.，“RFC 2119关键词中大写与小写的歧义”，BCP 14，RFC 8174，DOI 10.17487/RFC8174，2017年5月<https://www.rfc-editor.org/info/rfc8174>.
Acknowledgements
致谢
Thanks to Alexey Melnikov for suggestions on preparing this document. Thanks to Alan Murdock, Yoav Nir, Peter Saint-Andre, and Kurt Zeilenga for their review comments.
感谢Alexey Melnikov就编写本文件提出的建议。感谢Alan Murdock、Yoav Nir、Peter Saint Andre和Kurt Zeilenga的评论。
Author's Address
作者地址
Steve Kille Isode Ltd 14 Castle Mews Hampton, Middlesex TW12 2NP United Kingdom
Steve Kille Isode Ltd 14 Castle Mews Hampton，英国米德尔塞克斯TW12 2NP
Email: Steve.Kille@isode.com
Email: Steve.Kille@isode.com