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

Versions: 00 01 02 03 04 05 06 07 08 09 10                 Informational
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-04

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  . . . . . . . . . . . . . . . . . . . .   4
   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


   an object that is allowed to have an associated JID but does not
   currently have one.

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

3.2.  Attribute

   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.lit representing a user) and not a full
   JID (e.g. a JID such as romeo@shakespare.lit/AABBCC representing a
   specific client).  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.

         ( TBA.2 NAME 'jid'
            EQUALITY caseIgnoreMatch
            SUBSTR caseIgnoreSubstringsMatch
            SYNTAX 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].

4.  IANA Considerations

   The following registrations are requested in the LDAP Registry
   <https://www.iana.org/assignments/ldap-parameters/ldap-
   parameters.xhtml> in line with BP 64 [RFC4520].  This will lead to
   assignment of the two Object Identifiers, referenced as TBA.1 and
   TBA.2 in this draft.

   Object Identifier Registration

               Subject: Request for LDAP OID Registration (Internet
                 Directory Numbers)
               Person & email address to contact for further
                 information: S. Kille <steve.kille@isode.com>
               Specification: This document
               Author/Change Controller: IESG
               Comments: Identifies the XMPP schema elements assigned



Kille                    Expires March 15, 2018                 [Page 3]


Internet-Draft            LDAP Schema for XMPP            September 2017


   In the following two registrations, TBD is replaced with the OID
   assigned in the preceding registration.

   'JIDObject' Descriptor Registration

               Subject: Request for LDAP Descriptor Registration (Object
                 Identifier Descriptors)
               Descriptor (short name): JIDObject
               Object Identifier: TBD.1
               Person & email address to contact for further
                 information: S. Kille <steve.kille@isode.com>
               Usage: Object Class
               Specification: this document
               Author/Change Controller: IESG

   'jid' Descriptor Registration

               Subject: Request for LDAP Descriptor Registration (Object
                 Identifier Descriptors)
               Descriptor (short name): jid
               Object Identifier: TBD.2
               Person & email address to contact for further
                 information: S. Kille <steve.kille@isode.com>
               Usage: Attribute Type
               Specification: this document
               Author/Change Controller: IESG

5.  Security Considerations

   XMPP JIDs are often personal identifiers enabling electronic
   communication, with 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 which is acceptable to be linked to the
   LDAP object and be made accessible to all LDAP users.  The general
   LDAP Security Considerations specified in [RFC4510] also apply.

6.  Normative References

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

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



Kille                    Expires March 15, 2018                 [Page 4]


Internet-Draft            LDAP Schema for XMPP            September 2017


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

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

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

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

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




























Kille                    Expires March 15, 2018                 [Page 5]


Internet-Draft            LDAP Schema for XMPP            September 2017


Appendix A.  Acknowledgements

   Thanks to Alexey Melnikov for suggestions on preparing this draft.
   Thanks to Alan Murdock, Yoav Nir, Peter Saint-Andre and Kurt Zeilenga
   for review comments.

Author's Address

   Steve Kille
   Isode Ltd
   14 Castle Mews
   Hampton, Middlesex  TW12 2NP
   UK

   EMail: Steve.Kille@isode.com




































Kille                    Expires March 15, 2018                 [Page 6]