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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2017-05-11
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Reviews
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           S. Kille
Internet-Draft                                                 Isode Ltd
Intended status: Informational                              May 10, 2017
Expires: November 11, 2017

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

Abstract

   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 http://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 November 11, 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
   (http://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 November 11, 2017               [Page 1]
Internet-Draft            LDAP Schema for XMPP                  May 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 . . . . . . . . . . . . . . . . . . .   3
   6.  Normative References  . . . . . . . . . . . . . . . . . . . .   3
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

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

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 primary Object Class.

       ( TBA.1 NAME 'JIDObject'
        AUXILIARY
        MAY jid )

Kille                   Expires November 11, 2017               [Page 2]
Internet-Draft            LDAP Schema for XMPP                  May 2017

3.2.  Attribute

   This section defines the JID attribute referenced by the
   ObjectWithJID Auxiliary Object Class.  The syntax of the JID
   attribute SHOULD follow the rules of [RFC7622].  Note that the LDAP
   directory server is NOT expected to enforce this syntax.  The syntax
   guidelines are for LDAP clients.  The JID stored SHOULD be a bare JID
   and not a full JID.

         ( TBA.2 NAME 'jid'
            EQUALITY caseIgnoreMatch
Show full document text