Lightweight Directory Access Protocol (LDAP) Schema for Supporting the Extensible Messaging and Presence Protocol (XMPP) in White Pages
RFC 8284
| Document | Type |
RFC - Informational
(November 2017; No errata)
Was draft-kille-ldap-xmpp-schema (individual in art area)
|
|
|---|---|---|---|
| Author | Steve Kille | ||
| Last updated | 2017-11-30 | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | (None) | |
| Document shepherd | Alexey Melnikov | ||
| Shepherd write-up | Show (last changed 2017-09-27) | ||
| IESG | IESG state | RFC 8284 (Informational) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Ben Campbell | ||
| Send notices to | Alexey Melnikov <alexey.melnikov@isode.com> | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
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 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. 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. 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. Kille Informational [Page 1] RFC 8284 LDAP Schema for XMPP November 2017 Copyright Notice 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. 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 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. Kille Informational [Page 2] RFC 8284 LDAP Schema for XMPP November 2017 2. Conventions Used in This Document 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. 3. Schema Definition This section defines the schema used to store JIDs in the directory. 3.1. Object Class 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. ( 1.3.6.1.1.23.1 NAME 'JIDObject' AUXILIARY MAY jid ) 3.2. AttributeShow full document text