INTERNET-DRAFT Editor: Kurt D. Zeilenga Intended Category: Standard Track OpenLDAP Foundation Expires in six months 6 February 2006 Obsoletes: RFC 1274 Updates: RFC 2247, RFC 2798 COSINE LDAP/X.500 Schema Status of this Memo This document is intended to be, after appropriate review and revision, submitted to the RFC Editor as a Standard Track document. Distribution of this memo is unlimited. Technical discussion of this document will take place on the IETF LDAPEXT mailing list . Please send editorial comments directly to the author . By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. 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/1id-abstracts.html The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html Copyright (C) The Internet Society (2006). All Rights Reserved. Please see the Full Copyright section near the end of this document for more information. Abstract Zeilenga draft-zeilenga-ldap-cosine-02 [Page 1] INTERNET-DRAFT COSINE Schema 6 February 2006 This document provides a collection of schema elements for use with the Lightweight Directory Access Protocol (LDAP) from the COSINE and Internet X.500 pilot projects. This document obsoletes RFC 1274 and updates RFC 2247 and RFC 2798. Table of Contents Status of this Memo 1 Abstract 2 Table of Contents 1. Background and Intended Use 3 1.1. Relationship with Other Documents 1.2. Terminology and Conventions 2. COSINE Attribute Types 4 2.1. associatedDomain 2.2. associatedName 2.3. buildingName 2.3. co 2.5. documentAuthor 2.6. documentIdentifier 2.7. documentLocation 2.8. documentPublisher 2.9. documentTitle 2.10. documentVersion 2.11. drink 2.12. homePhone 2.13. homePostalAddress 2.14. host 2.16. info 2.17. mail 2.18. manager 2.19. mobile 2.20. organizationalStatus 2.21. pager 2.22. personalTitle 2.23. roomNumber 2.24. secretary 2.26. uniqueIdentifier 2.27. userClass 3. COSINE Object Classes 14 3.1. account 3.2. document 3.3. documentSeries 3.4. domain 3.5. domainRelatedObject 3.6. friendlyCountry Zeilenga draft-zeilenga-ldap-cosine-02 [Page 2] INTERNET-DRAFT COSINE Schema 6 February 2006 3.7. rFC822LocalPart 3.8. room 3.9. simpleSecurityObject 4. Security Considerations 19 5. IANA Considerations 20 6. Acknowledgments 21 7. Editor's Address 8. References A. Changes Since RFC 1274 23 Intellectual Property Rights 24 Full Copyright 1. Background and Intended Use In the late 1980s, X.500 Directory Services were standardised by the CCITT (Commite' Consultatif International de Telegraphique et Telephonique), now a part of the ITU (International Telephone Union). This lead to Directory Service piloting activities in the early 1990s, including the COSINE (Co-operation and Open Systems Interconnection in Europe) PARADISE Project pilot [COSINEpilot] in Europe. Motivated by needs large scale directory pilots, RFC 1274 was published to standardize directory schema and naming architecture for use in the COSINE and other Internet X.500 pilots [RFC1274]. In the years that followed, X.500 Directory Services have evolved to incorporate new capabilities and even new protocols. In particular, the Lightweight Directory Access Protocol (LDAP) [Roadmap] was introduced in the early 1990s [RFC1487], with Version 3 of LDAP introduced in the late 1990s [RFC2251] and subsequently revised in the 2005 [Roadmap]. While much of the material in RFC 1274 has been superceed by subsequently published ITU-T Recommendations and IETF RFCs, many of the schema elements lack standardized schema descriptions for use in modern X.500 and LDAP directory services despite the fact that these schema elements are in wide use today. As the old schema descriptions cannot be used without adaptation, interoperabilty issues may arise due to lack of standardized modern schema descriptions. This document addresses these issues by offering standardized schema descriptions, where needed, for widely-used COSINE schema elements. 1.1. Relationship to Other Documents This document, together with [Schema] and [Syntaxes], obsoletes RFC 1274 in its entirety. [Schema] replaces sections 9.3.1 (Userid) and 9.3.21 (Domain Component) of RFC 1274. [Syntaxes] replaces section Zeilenga draft-zeilenga-ldap-cosine-02 [Page 3] INTERNET-DRAFT COSINE Schema 6 February 2006 9.4 (Generally useful syntaxes) of RFC 1274. This document replaces the remainder of RFC 1274. Appendix A. discusses changes since RFC 1274, as well as why certain schema elements were not brought forward in this revision of the COSINE schema. All elements not brought are to be regarded as Historic. The description of the 'domain' object class provided in this document supercedes that found in RFC 2247. That is, section 3.4 of this document replaces section 5.2 of RFC 2247. Some of schema elements specified here were described in RFC 2798 (inetOrgPerson schema). This document supersedes these descriptions. This document, together with [Schema], replaces section 9.1.3 of RFC 2798. 1.2. Terminology and Conventions 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 BCP 14 [RFC2119]. DIT stands for Directory Information Tree. DN stands for Distinguished Name. DSA stands for Directory System Agent, a server. DSE stands for DSA-Specific Entry. DUA stands for Directory User Agent, a client. These terms are discussed in [Models]. Schema definitions are provided using LDAP description formats [Models]. Definitions provided here are formatted (line wrapped) for readability. 2. COSINE Attribute Types This section details COSINE attribute types for use in LDAP. 2.1. associatedDomain The 'associatedDomain' attribute specifies DNS [RFC1034][RFC2181] host names [RFC1123] which are associated with an object. That is, values of this attribute should conform to the following ABNF: domain = root / label *( DOT label ) Zeilenga draft-zeilenga-ldap-cosine-02 [Page 4] INTERNET-DRAFT COSINE Schema 6 February 2006 root = SPACE label = LETDIG [ *61( LETDIG / HYPHEN ) LETDIG ] LETDIG = %x30-39 / %x41-5A / %x61-7A ; "0" - "9" / "A"-"Z" / "a"-"z" SPACE = %x20 ; space (" ") HYPHEN = %x2D ; hyphen ("-") DOT = %x2E ; period (".") For example, the entry in the DIT with a DN might have an associated domain of "example.com". ( 0.9.2342.19200300.100.1.37 NAME 'associatedDomain' EQUALITY caseIgnoreIA5Match SUBSTR caseIgnoreIA5SubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 ) The IA5String (1.3.6.1.4.1.1466.115.121.1.26) syntax and the 'caseIgnoreIA5Match' and 'caseIgnoreIA5SubstringsMatch' rules are described in [Syntaxes]. It is noted that the directory will not ensure that values of this attribute conform to the production provided above. It is the application responsibility to ensure domains it stores in this attribute are appropriately represented. It is also noted that applications supporting Internationalized Domain Names SHALL use the ToASCII method [RFC3490] to produce