idnits 2.17.1 draft-kille-ldap-xmpp-schema-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (May 10, 2017) is 2543 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group S. Kille 3 Internet-Draft Isode Ltd 4 Intended status: Informational May 10, 2017 5 Expires: November 11, 2017 7 LDAP Schema for supporting XMPP in White Pages 8 draft-kille-ldap-xmpp-schema-01 10 Abstract 12 The Extensible Messaging and Presence Protocol (XMPP) identifies 13 users by use of JID (Jabber IDs). Lightweight Directory Access 14 Protocol (LDAP) enables provision of a white pages service with 15 schema relating to users and support for internet protocols. This 16 specification defines schema to enable XMPP JIDs to be associated 17 with objects in an LDAP directory so that this information can be 18 used with white pages applications. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at http://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on November 11, 2017. 37 Copyright Notice 39 Copyright (c) 2017 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (http://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 55 2. Conventions Used in This Document . . . . . . . . . . . . . . 2 56 3. Schema Definition . . . . . . . . . . . . . . . . . . . . . . 2 57 3.1. Object Class . . . . . . . . . . . . . . . . . . . . . . 2 58 3.2. Attribute . . . . . . . . . . . . . . . . . . . . . . . . 3 59 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 60 5. Security Considerations . . . . . . . . . . . . . . . . . . . 3 61 6. Normative References . . . . . . . . . . . . . . . . . . . . 3 62 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 5 63 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 65 1. Introduction 67 Extensible Messaging and Presence Protocol (XMPP) [RFC6120] 68 identifies users by use of JID (Jabber IDs). Lightweight Directory 69 Access Protocol (LDAP) [RFC4510] enables provision of a white pages 70 service with schema relating to users and support for internet 71 protocols defined in [RFC4519]. This specification defines schema to 72 enable XMPP JIDs to be associated with LDAP directory objects so that 73 this information can be used with white pages applications. 75 The LDAP schema for storing JIDs is defined to enable JIDs to be 76 associated with any object stored in the directory. This is done by 77 associating the new JID Attribute with a new Auxiliary Object Class 78 (JIDObject). 80 2. Conventions Used in This Document 82 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 83 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 84 document are to be interpreted as described in [RFC2119]. 86 3. Schema Definition 88 This section defines the schema used to store JIDs in the directory. 90 3.1. Object Class 92 This section defines a new Auxiliary Object Class (JIDObject) which 93 may be associated with any primary Object Class. 95 ( TBA.1 NAME 'JIDObject' 96 AUXILIARY 97 MAY jid ) 99 3.2. Attribute 101 This section defines the JID attribute referenced by the 102 ObjectWithJID Auxiliary Object Class. The syntax of the JID 103 attribute MUST follow the rules of [RFC7622]. The JID stored MUST be 104 a bare JID and not a full JID. Note that the LDAP directory server 105 is NOT expected to enforce this syntax. The syntax rules are for 106 LDAP clients setting this attribute. 108 ( TBA.2 NAME 'jid' 109 EQUALITY caseIgnoreMatch 110 SUBSTR caseIgnoreSubstringsMatch 111 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 ) 113 1.3.6.1.4.1.1466.115.121.1.15 refers to the Directory String syntax 114 defined in [RFC4517]. 116 4. IANA Considerations 118 The two Object Identifiers, references as TBA.1 and TBA.2 in this 119 draft are assigned by IANA in the "Object Identifier Descriptors" as 120 the name of the LDAP Registry . 123 5. Security Considerations 125 This schema enables publishing for XMPP JIDs, and care should be 126 taken to ensure that this information is not accessed 127 inappropriately. 129 6. Normative References 131 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 132 Requirement Levels", BCP 14, RFC 2119, 133 DOI 10.17487/RFC2119, March 1997, 134 . 136 [RFC4510] Zeilenga, K., Ed., "Lightweight Directory Access Protocol 137 (LDAP): Technical Specification Road Map", RFC 4510, 138 DOI 10.17487/RFC4510, June 2006, 139 . 141 [RFC4517] Legg, S., Ed., "Lightweight Directory Access Protocol 142 (LDAP): Syntaxes and Matching Rules", RFC 4517, 143 DOI 10.17487/RFC4517, June 2006, 144 . 146 [RFC4519] Sciberras, A., Ed., "Lightweight Directory Access Protocol 147 (LDAP): Schema for User Applications", RFC 4519, 148 DOI 10.17487/RFC4519, June 2006, 149 . 151 [RFC6120] Saint-Andre, P., "Extensible Messaging and Presence 152 Protocol (XMPP): Core", RFC 6120, DOI 10.17487/RFC6120, 153 March 2011, . 155 [RFC7622] Saint-Andre, P., "Extensible Messaging and Presence 156 Protocol (XMPP): Address Format", RFC 7622, 157 DOI 10.17487/RFC7622, September 2015, 158 . 160 Appendix A. Acknowledgements 162 Thanks to Alexey Melnikov for suggestions on preparing this draft. 163 Thanks to Peter Saint-Andre and Kurt Zeilenga for review comments. 165 Author's Address 167 Steve Kille 168 Isode Ltd 169 14 Castle Mews 170 Hampton, Middlesex TW12 2NP 171 UK 173 EMail: Steve.Kille@isode.com