INTERNET-DRAFT Editor: Kurt D. Zeilenga Intended Category: Standard Track OpenLDAP Foundation Expires in six months 24 October 2004 Obsoletes: RFC 1274 Updates: RFC 2798 LDAP: Additional Schema Elements 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, I accept the provisions of Section 4 of RFC 3667. By submitting this Internet-Draft, I certify that any applicable patent or other IPR claims of which I am aware have been disclosed, or will be disclosed, and any of which I become aware will be disclosed, in accordance with RFC 3668. 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 . The list of Internet-Draft Shadow Directories can be accessed at . Copyright (C) The Internet Society (2004). All Rights Reserved. Please see the Full Copyright section near the end of this document for more information. Abstract Zeilenga draft-zeilenga-ldap-user-schema-07 [Page 1] INTERNET-DRAFT LDAP: Additional Schema Elements 27 September 2004 This document provides a collection of schema elements for use with the Lightweight Directory Access Protocol from COSINE and Internet X.500 pilot projects. Table of Contents (to be expanded by editor) Status of this Memo 1 Abstract Conventions 2 Table of Contents 1. Background and Intended Use 3 2. Terminology and Conventions 3. Attribute Types 3.1. associatedDomain 3.2. associatedName 3.3. buildingName 3.3. co 8 3.5. documentAuthor 3.6. documentIdentifier 3.7. documentLocation 3.8. documentPublisher 9 3.9. documentTitle 3.10. documentVersion 3.11. drink 3.12. homePhone 10 3.13. homePostalAddress 3.14. host 3.16. info 3.17. mail 11 3.18. manager 3.19. mobile 3.20. organizationalStatus 3.21. pager 3.22. personalTitle 3.23. roomNumber 3.24. secretary 13 3.26. uniqueIdentifier 3.27. userClass 14 4. Object Classes 4.1. account 4.2. document 4.3. documentSeries 15 4.4. domainRelatedObject 4.5. friendlyCountry 4.6. rFC822LocalPart 4.7. room 16 4.8. simpleSecurityObject Zeilenga draft-zeilenga-ldap-user-schema-07 [Page 2] INTERNET-DRAFT LDAP: Additional Schema Elements 27 September 2004 5. Security Considerations 6. IANA Considerations 17 7. Acknowledgments 18 8. Author's Address 9. References 19 Full Copyright 20 1. Background and Intended Use This document provides descriptions of additional for schema elements for use with the Lightweight Directory Access Protocol (LDAP) [Roadmap]. The elements were originally introduced for use in the COSINE and Internet X.500 pilot projects [RFC1274]. This document adapts the schema elements for use in modern directory applications, while preserving established syntaxes and semantics. This document, together with RFC 2247 and [Schema], obsoletes RFC 1274. Some of these items were described in the inetOrgPerson [RFC2798] schema. This document supersedes these descriptions. This document, together with [Schema], replaces section 9.1.3 of RFC 2798. 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. 3. Attribute Types This section details attribute types for use in LDAP. 3.1. associatedDomain Zeilenga draft-zeilenga-ldap-user-schema-07 [Page 3] INTERNET-DRAFT LDAP: Additional Schema Elements 27 September 2004 The associatedDomain attribute type specifies DNS domains [RFC1034] which are associated with an object. 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 [RFC1034]. 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