idnits 2.17.1 draft-kille-ldap-xmpp-schema-05.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 (September 11, 2017) is 2412 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 September 11, 2017 5 Expires: March 15, 2018 7 LDAP Schema for supporting XMPP in White Pages 8 draft-kille-ldap-xmpp-schema-05 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 https://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 March 15, 2018. 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 (https://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 . . . . . . . . . . . . . . . . . . . 4 61 6. Normative References . . . . . . . . . . . . . . . . . . . . 5 62 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 6 63 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 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 structural Object Class. This Object 94 Class is used to augment entries for objects that act or may act as 95 an XMPP client. The JID attribute is optional, to enable configuring 96 an object that is allowed to have an associated JID but does not 97 currently have one. 99 ( TBA.1 NAME 'JIDObject' 100 AUXILIARY 101 MAY jid ) 103 3.2. Attribute 105 This section defines the JID attribute referenced by the JIDObject 106 Auxiliary Object Class. The syntax of the JID attribute MUST follow 107 the rules of [RFC7622]. The JID stored MUST be a bare JID (e.g., a 108 JID such as romeo@shakespeare.lit representing a user) and not a full 109 JID (e.g. a JID such as romeo@shakespare.lit/AABBCC representing a 110 specific client). Note that the LDAP directory server is NOT 111 expected to enforce this syntax. The syntax rules are for LDAP 112 clients setting this attribute, noting that human usage is a key 113 target. Applications using this attribute should format that string 114 in a manner appropriate to the application and XMPP applications 115 SHOULD apply [RFC7622] to the attribute. The directory service 116 doesn't enforce the JID syntax and values are compared according to 117 the matching rules specified in the attribute definition. 119 NOTE: The directory string syntax and the caseIgnoreMatch matching 120 rule are chosen to allow entry and matching of values according to 121 common rules used within the directory, for convenience for users and 122 administrators as well as implementors. As this syntax and matching 123 rules differs from [RFC7622] false positive and false negative can 124 possibly occur. This is not anticipated to cause operational issues 125 (based on implementation experience with similar syntax/matching rule 126 mismatches). 128 ( TBA.2 NAME 'jid' 129 EQUALITY caseIgnoreMatch 130 SUBSTR caseIgnoreSubstringsMatch 131 SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 ) 133 1.3.6.1.4.1.1466.115.121.1.15 refers to the Directory String syntax 134 defined in [RFC4517]. 136 4. IANA Considerations 138 The following registrations are requested in the LDAP Registry 139 in line with BP 64 [RFC4520]. This will lead to 141 assignment of the two Object Identifiers, referenced as TBA.1 and 142 TBA.2 in this draft. 144 Object Identifier Registration 146 Subject: Request for LDAP OID Registration (Internet 147 Directory Numbers) 148 Person & email address to contact for further 149 information: S. Kille 150 Specification: This document 151 Author/Change Controller: IESG 152 Comments: Identifies the XMPP schema elements assigned 154 In the following two registrations, TBD is replaced with the OID 155 assigned in the preceding registration. 157 'JIDObject' Descriptor Registration 159 Subject: Request for LDAP Descriptor Registration (Object 160 Identifier Descriptors) 161 Descriptor (short name): JIDObject 162 Object Identifier: TBD.1 163 Person & email address to contact for further 164 information: S. Kille 165 Usage: Object Class 166 Specification: this document 167 Author/Change Controller: IESG 169 'jid' Descriptor Registration 171 Subject: Request for LDAP Descriptor Registration (Object 172 Identifier Descriptors) 173 Descriptor (short name): jid 174 Object Identifier: TBD.2 175 Person & email address to contact for further 176 information: S. Kille 177 Usage: Attribute Type 178 Specification: this document 179 Author/Change Controller: IESG 181 5. Security Considerations 183 XMPP JIDs are often personal identifiers enabling electronic 184 communication, with similar considerations to email addresses. This 185 schema enables publishing of this information in LDAP directories 186 which may be corporate or public services. Care should be taken to 187 only publish JID information which is acceptable to be linked to the 188 LDAP object and be made accessible to all LDAP users. The general 189 LDAP Security Considerations specified in [RFC4510] also apply. 191 6. Normative References 193 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 194 Requirement Levels", BCP 14, RFC 2119, 195 DOI 10.17487/RFC2119, March 1997, 196 . 198 [RFC4510] Zeilenga, K., Ed., "Lightweight Directory Access Protocol 199 (LDAP): Technical Specification Road Map", RFC 4510, 200 DOI 10.17487/RFC4510, June 2006, 201 . 203 [RFC4517] Legg, S., Ed., "Lightweight Directory Access Protocol 204 (LDAP): Syntaxes and Matching Rules", RFC 4517, 205 DOI 10.17487/RFC4517, June 2006, 206 . 208 [RFC4519] Sciberras, A., Ed., "Lightweight Directory Access Protocol 209 (LDAP): Schema for User Applications", RFC 4519, 210 DOI 10.17487/RFC4519, June 2006, 211 . 213 [RFC4520] Zeilenga, K., "Internet Assigned Numbers Authority (IANA) 214 Considerations for the Lightweight Directory Access 215 Protocol (LDAP)", BCP 64, RFC 4520, DOI 10.17487/RFC4520, 216 June 2006, . 218 [RFC6120] Saint-Andre, P., "Extensible Messaging and Presence 219 Protocol (XMPP): Core", RFC 6120, DOI 10.17487/RFC6120, 220 March 2011, . 222 [RFC7622] Saint-Andre, P., "Extensible Messaging and Presence 223 Protocol (XMPP): Address Format", RFC 7622, 224 DOI 10.17487/RFC7622, September 2015, 225 . 227 Appendix A. Acknowledgements 229 Thanks to Alexey Melnikov for suggestions on preparing this draft. 230 Thanks to Alan Murdock, Yoav Nir, Peter Saint-Andre and Kurt Zeilenga 231 for review comments. 233 Author's Address 235 Steve Kille 236 Isode Ltd 237 14 Castle Mews 238 Hampton, Middlesex TW12 2NP 239 UK 241 EMail: Steve.Kille@isode.com