LDAP Schema for supporting XMPP in White Pages
draft-kille-ldap-xmpp-schema-05

Document Type Active Internet-Draft (individual in art area)
Last updated 2017-09-12
Stream IETF
Intended RFC status Informational
Formats plain text xml pdf html bibtex
Reviews
Stream WG state (None)
Document shepherd Alexey Melnikov
IESG IESG state In Last Call (ends 2017-09-27)
Consensus Boilerplate Unknown
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 None
Network Working Group                                           S. Kille
Internet-Draft                                                 Isode Ltd
Intended status: Informational                        September 11, 2017
Expires: March 15, 2018

             LDAP Schema for supporting XMPP in White Pages
                    draft-kille-ldap-xmpp-schema-05

Abstract

   The Extensible Messaging and Presence Protocol (XMPP) identifies
   users by use of JID (Jabber IDs).  Lightweight Directory Access
   Protocol (LDAP) enables provision of a white pages service with
   schema relating to users and support for internet protocols.  This
   specification defines 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 Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on March 15, 2018.

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

Kille                    Expires March 15, 2018                 [Page 1]
Internet-Draft            LDAP Schema for XMPP            September 2017

   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 . . . . . . . . . . . . . .   2
   3.  Schema Definition . . . . . . . . . . . . . . . . . . . . . .   2
     3.1.  Object Class  . . . . . . . . . . . . . . . . . . . . . .   2
     3.2.  Attribute . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   6.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   Extensible Messaging and Presence Protocol (XMPP) [RFC6120]
   identifies users by use of JID (Jabber IDs).  Lightweight Directory
   Access Protocol (LDAP) [RFC4510] enables provision of a white pages
   service with schema relating to users and support for internet
   protocols defined in [RFC4519].  This specification defines 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
   (JIDObject).

2.  Conventions Used in This Document

   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 [RFC2119].

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 (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, to enable configuring

Kille                    Expires March 15, 2018                 [Page 2]
Internet-Draft            LDAP Schema for XMPP            September 2017
Show full document text