INTERNET-DRAFT Kurt D. Zeilenga Intended Category: Experimental OpenLDAP Foundation Expires: 17 May 2001 17 November 2000 International Domain Names and LDAP 1. Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. This document is intended to be, after appropriate review and revision, submitted to the RFC Editor as an Experimental document. Distribution of this memo is unlimited. Technical discussion of this document will take place on the IETF LDAP Extensions Working Group mailing list . Please send editorial comments directly to the author . Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. 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.'' The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Copyright 2000, The Internet Society. All Rights Reserved. Please see the Copyright section near the end of this document for more information. 2. Abstract This document describes schema and mechanisms extending the Lightweight Directory Access Protocol [RFC 2251] to support the International Domain Name System [IDN]. The key words ``MUST'', ``MUST NOT'', ``REQUIRED'', ``SHALL'', ``SHALL NOT'', ``SHOULD'', ``SHOULD NOT'', ``RECOMMENDED'', and ``MAY'' in this document are to be interpreted as described in RFC 2119 [RFC2119]. Zeilenga [Page 1] INTERNET-DRAFT LDAP IDN 17 November 2000 3. Background and Intended Use Experimental internationalized domain name systems exist. The IETF is actively engineering standards in this area. Though this work is in progress, enough is known to experiment with international domain names in application protocols. 4. Domains use in LDAP Excepting user data transferred by the protocol (see Section 5), the only use of domain names is as part of an LDAPURL returned in a Referral LDAPResult or SearchResultReference response PDU. An LDAPURL may contain any URI [RFC2396] though is generally an LDAP URL [RFC 2255]. These URIs have a domain name as the host in the hostport part. The internationalization of URIs is beyond the scope of this document. Whatever mechanism defined for URIs will be applied to LDAP URLs. 5. International Domain Schema The schema described in this section is intended to be used similar to the schema described in [RFC2247] and [LOCATE] excepting that it is used conjunction with a International Domain Name System instead of the Internet Domain Name System and domain components are restricted to UTF-8 not IA5. This section defined internationalized versions of the domain related schema elements introduced in [RFC1274] and subsequently adapted for use with LDAP [RFC2247]. Editor's Note: object identifiers (OIDs) will be assigned before this document is published as an RFC. 5.1. International Domain Component The idc (short for International Domain Component) attribute type is defined as follows: ( OID.TBD NAME 'idc' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX directoryString SINGLE-VALUE ) Zeilenga [Page 2] INTERNET-DRAFT LDAP IDN 17 November 2000 The value of this attribute is a string holding one component of a international domain name. The encoding of directoryString for use in LDAP is simply the characters of the string itself. The equality matching rule is case insensitive, as is today's IDN. 5.2. International Domain Component Object The idcObject object class permits the idc attribute to be present in an entry. This object class is defined as auxiliary, as it would typically be used in conjunction with an existing structural object class, such as organization, organizationalUnit or locality. The following object class, along with the idc attribute, can be added to any entry. ( OID.TBD NAME 'idcObject' AUXILIARY MUST idc ) An example entry would be: dn: idc=example,idc=com objectClass: top objectClass: organization objectClass: idcObject idc: example o: Example Organization 6. Security Considerations This document describes how attributes of objects may be discovered and retrieved. Servers should ensure that an appropriate security policy is maintained. An enterprise is not restricted in the information which it may store in DNS or LDAP servers. A client which contacts an untrusted server may have incorrect or misleading information returned (e.g. an organization's server may claim to hold naming contexts representing domain names which have not been delegated to that organization). 7. Copyright Copyright 2000, The Internet Society. All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it Zeilenga [Page 3] INTERNET-DRAFT LDAP IDN 17 November 2000 or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE AUTHORS, THE INTERNET SOCIETY, AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 8. Acknowledgment This document borrows heavily from RFC 2247 and a number of other IETF documents. 9. Bibliography [RFC2219] S. Bradner, "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, March 1997. [RFC2251] M. Wahl, T. Howes, S. Kille, "Lightweight Directory Access Protocol (v3)", RFC 2251, December 1997. [RFC2252] M. Wahl, A. Coulbeck, T. Howes, S. Kille, "Lightweight Directory Access Protocol (v3): Attribute Syntax Definitions", RFC 2252, December 1997. [RFC2247] S. Kille, M. Wahl, A. Grimstad, R. Huber, S. Sataluri, "Using Domains in LDAP/X.500 Distinguished Names", RFC 2247, January 1998. [RFC2396] T. Berners-Lee, R. Fielding, L. Masinter, "Uniform Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998. [LOCATE] IETF LDAPext WG, "Discovering LDAP Services with DNS", Zeilenga [Page 4] INTERNET-DRAFT LDAP IDN 17 November 2000 draft-ietf-ldapext-locate-xx.txt (work in progress). 10. Author's Address Kurt D. Zeilenga OpenLDAP Foundation Zeilenga [Page 5]