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
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.
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.
Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved.
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.
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.
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.
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.
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.
( 126.96.36.199.1.23.1 NAME 'JIDObject' AUXILIARY MAY 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 email@example.com representing a human user) and not a full JID (e.g., a JID such as firstname.lastname@example.org/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.
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
Kille Informational [Page 3]
RFC 8284 LDAP Schema for XMPP November 2017
negatives can possibly occur. This is not anticipated to cause operational issues (based on implementation experience with similar syntax/matching rule mismatches).
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 [188.8.131.52.1.]) registry:
Decimal: 23 Name: xmpp Description: LDAP schema for XMPP
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.