INTERNET-DRAFT K. Dally, Editor Intended Category: Standard Track The MITRE Corp. Expires 20 May 2001 20 November 2001 Obsoletes: RFC 2256 A Summary of the X.500(2nd edition) User Schema for use with LDAPv3 <draft-ietf-ldapbis-user-schema-01> [Editor's note: This Internet-Draft (I-D) is a modified version of the text of RFC 2256, in order to bring it up to date. This action is part of the maintenance activity that is needed in order to progress LDAPv3 to Draft Standard. The changes are described in Annex A of this document. End of Editor's note] 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 a Standard Track document. Distribution of this memo is unlimited. Technical discussion of this document will take place on the IETF LDAP Revision Working Group (LDAPbis) mailing list <ietf-ldapbis@openldap.org>. Please send editorial comments directly to the author <kdally@mitre.org>. 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. Dally Expires 20 May 2002 [Page 1]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 Abstract This document provides an overview of the attribute types and object classes defined by the ISO/IEC JTC1 and ITU-T committees in the IS0/IEC 9594 and X.500 documents, in particular those intended for use by directory clients. This is the most widely used schema for LDAP/X.500 directories, and many other schema definitions for white pages objects use it as a basis. This document does not cover attributes used for the administration of X.500 directory servers, nor does it include attributes defined by other ISO/ITU-T documents. 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 RFC 2119 [6]. Dally Expires 20 May 2002 [Page 2]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 Table of Contents Status of this Memo 1 Abstract 2 1. General Issues 5 2. Source 5 3. Attribute Types 6 3.1 aliasedObjectName 6 3.2 authorityRevocationList 6 3.3 businessCategory 6 3.4 c 7 3.5 cACertificate 7 3.6 certificateRevocationList 7 3.7 cn 7 3.8 crossCertificatePair 7 3.9 deltaRevocationList 8 3.10 description 8 3.11 destinationIndicator 8 3.12 distinguishedName 8 3.13 dmdName 8 3.14 dnQualifier 9 3.15 enhancedSearchGuide 9 3.16 facsimileTelephoneNumber 9 3.17 generationQualifier 9 3.18 givenName 9 3.19 houseIdentifier 10 3.20 initials 10 3.21 internationalISDNNumber 10 3.22 knowledgeInformation 10 3.23 l 10 3.24 member 10 3.25 name 11 3.26 o 11 3.27 objectClass 11 3.28 ou 11 3.29 owner 11 3.30 physicalDeliveryOfficeName 12 3.31 postalAddress 12 3.32 postalCode 12 3.33 postOfficeBox 12 3.34 preferredDeliveryMethod 12 3.35 presentationAddress 13 3.36 protocolInformation 13 3.37 registeredAddress 13 3.38 roleOccupant 13 3.39 searchGuide 13 3.40 seeAlso 14 Dally Expires 20 May 2002 [Page 3]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 3.41 serialNumber 14 3.42 sn 14 3.43 st 14 3.44 street 14 3.45 supportedAlgorithms 14 3.46 supportedApplicationContext 15 3.47 telephoneNumber 15 3.48 teletexTerminalIdentifier 15 3.49 telexNumber 15 3.50 title 15 3.51 uniqueMember 16 3.52 userCertificate 16 3.53 userPassword 16 3.54 x121Address 16 3.55 x500UniqueIdentifier 17 4. Object Classes 18 4.1 alias 18 4.2 applicationEntity 18 4.3 applicationProcess 18 4.4 certificationAuthority 18 4.5 certificationAuthority-V2 19 4.6 country 19 4.7 cRLDistributionPoint 19 4.8 device 19 4.9 dmd 20 4.10 dSA 20 4.11 groupOfNames 20 4.12 groupOfUniqueNames 21 4.13 locality 21 4.14 organization 21 4.15 organizationalPerson 21 4.16 organizationalRole 22 4.17 organizationalUnit 22 4.18 person 23 4.19 residentialPerson 23 4.20 strongAuthenticationUser 23 4.21 top 23 4.22 userSecurityInformation 24 5. Security Considerations 24 6. Acknowledgements 24 7. References 25 8. Author's Address 25 Annex A Change Log 26 Dally Expires 20 May 2002 [Page 4]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 1. General Issues This document references syntaxes given in section 3 of [1]. Matching rules are listed in section 4 of [1]. The attribute type and object class definitions are written using the BNF form of AttributeTypeDescription and ObjectClassDescription given in [1]. Lines have been folded for readability. 2. Source The schema definitions in this document are based on those found in X.500 [2], [3], [4], and [5], specifically: Sections Source ============ ============ 3.1 X.501 [2] 3.2 X.509 [3] 3.3 - 3.4 X.520 [4] 3.5 - 3.6 X.509 [3] 3.7 X.520 [4] 3.8 - 3.9 X.509 [3] 3.10 - 3.44 X.520 [4] 3.45 X.509 [3] 3.46 - 3.51 X.520 [4] 3.52 - 3.53 X.509 [3] 3.54 - 3.55 X.520 [4] 4.1 X.501 [2] 4.2 - 4.3 X.521 [5] 4.4 - 4.5 X.509 [3] 4.6 X.521 [5] 4.7 X.509 [3] 4.8 - 4.19 X.521 [5] 4.20 X.509 [3] 4.21 X.501 [2] 4.22 X.509 [3] Three new attributes: supportedAlgorithms, deltaRevocationList and dmdName, and the new objectClass dmd, which were not specified in X.500 edition 2 (1993), are defined in the X.500 edition 3 (1997)[2, 3, 4, 5] documents. [Editor's note: Should these items be removed so that they are not bringing in a second set of X.500 references. Perhaps they could be put into a non-normative annex with reference to the later X.500 edition. End editor's note.] Dally Expires 20 May 2002 [Page 5]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 3. Attribute Types The attribute types contained in this section hold user information. An LDAP server implementation MUST recognize the objectClass attribute type. There is no requirement that servers implement the following attribute types: knowledgeInformation searchGuide teletexTerminalIdentifier In fact, their use is greatly discouraged. An LDAP server implementation SHOULD recognize the rest of the attribute types described in this section. 3.1 aliasedObjectName The aliasedObjectName attribute is used by the directory service if the entry containing this attribute is an alias. In X.500, this attribute is called aliasedEntryName. ( 2.5.4.1 NAME 'aliasedObjectName' EQUALITY distinguishedNameMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 ; DN SINGLE-VALUE ) 3.2 authorityRevocationList A value of this attribute is a list of CA certificates that are no longer valid. This attribute is to be stored and requested in the binary form, as 'authorityRevocationList;binary'. ( 2.5.4.38 NAME 'authorityRevocationList' SYNTAX 1.3.6.1.4.1.1466.115.121.1.9 ) ; CertificateList 3.3 businessCategory This attribute describes the kind of business performed by an organization. ( 2.5.4.15 NAME 'businessCategory' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{128} ) ; DirectoryString Dally Expires 20 May 2002 [Page 6]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 3.4 c This is the X.500 countryName attribute, which contains a two-letter ISO 3166 country code. ( 2.5.4.6 NAME 'c' SUP name SINGLE-VALUE ) 3.5 cACertificate A value of this attribute is a set of information that is used to establish a traceable chain of authority for issuing user certificates. This attribute is to be stored and requested in the binary form, as 'cACertificate;binary'. ( 2.5.4.37 NAME 'cACertificate' SYNTAX 1.3.6.1.4.1.1466.115.121.1.8 ) ; Certificate 3.6 certificateRevocationList A value of this attribute is a list of user certificates that are no longer valid. This attribute is to be stored and requested in the binary form, as 'certificateRevocationList;binary'. ( 2.5.4.39 NAME 'certificateRevocationList' SYNTAX 1.3.6.1.4.1.1466.115.121.1.9 ) ; CertificateList 3.7 cn This is the X.500 commonName attribute, which contains a name of an object. If the object corresponds to a person, it is typically the person's full name. ( 2.5.4.3 NAME 'cn' SUP name ) 3.8 crossCertificatePair A value of this attribute is a set of two certificates that are used to enable the certificates issued in two security domains to be usable in both domains. This attribute is to be stored and requested in the binary form, as 'crossCertificatePair;binary'. ( 2.5.4.40 NAME 'crossCertificatePair' SYNTAX 1.3.6.1.4.1.1466.115.121.1.10 ) ; CertificatePair Dally Expires 20 May 2002 [Page 7]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 3.9 deltaRevocationList This attribute contains a list of revoked user certificates that is an addition to a previous certificate revocation list. This attribute is to be stored and requested in the binary form, as 'deltaRevocationList;binary'. ( 2.5.4.53 NAME 'deltaRevocationList' SYNTAX 1.3.6.1.4.1.1466.115.121.1.9 ) ; CertificateList 3.10 description This attribute contains a human-readable description of the object. ( 2.5.4.13 NAME 'description' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{1024} ) ; DirectoryString 3.11 destinationIndicator This attribute is used for the telegram service. ( 2.5.4.27 NAME 'destinationIndicator' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.44{128} ) ; PrintableString 3.12 distinguishedName This attribute type is not used as the name of the object itself, but it is instead a base type from which attributes with DN syntax inherit. It is unlikely that values of this type itself will occur in an entry. LDAP server implementations which do not support attribute subtyping need not recognize this attribute in requests. Client implementations MUST NOT assume that LDAP servers are capable of performing attribute subtyping. ( 2.5.4.49 NAME 'distinguishedName' EQUALITY distinguishedNameMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 ) 3.13 dmdName The value of this attribute specifies a directory management domain (DMD), the administrative authority which operates the directory server. Dally Expires 20 May 2002 [Page 8]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 ( 2.5.4.54 NAME 'dmdName' SUP name ) 3.14 dnQualifier The dnQualifier attribute type specifies disambiguating information to add to the relative distinguished name of an entry. It is intended for use when merging data from multiple sources in order to prevent conflicts between entries which would otherwise have the same name. It is recommended that the value of the dnQualifier attribute be the same for all entries from a particular source. ( 2.5.4.46 NAME 'dnQualifier' EQUALITY caseIgnoreMatch ORDERING caseIgnoreOrderingMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.44 ) ; PrintableString 3.2.15 enhancedSearchGuide This attribute is for use by X.500 clients in constructing search filters. ( 2.5.4.47 NAME 'enhancedSearchGuide' SYNTAX 1.3.6.1.4.1.1466.115.121.1.21 ) ; EnhancedGuide 3.16 facsimileTelephoneNumber A value of this attribute is a telephone number for a facsimile terminal (and, optionally, its parameters). ( 2.5.4.23 NAME 'facsimileTelephoneNumber' SYNTAX 1.3.6.1.4.1.1466.115.121.1.22 ) ; FacsimileTelephoneNumber 3.17 generationQualifier The generationQualifier attribute contains the part of the name which typically is the suffix, as in "IIIrd". ( 2.5.4.44 NAME 'generationQualifier' SUP name ) 3.18 givenName The givenName attribute is used to hold the part of a person's name which is not their surname nor middle name. ( 2.5.4.42 NAME 'givenName' SUP name ) Dally Expires 20 May 2002 [Page 9]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 3.19 houseIdentifier This attribute is used to identify a building within a location. ( 2.5.4.51 NAME 'houseIdentifier' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{32768} ) ; DirectoryString 3.20 initials The initials attribute contains the initials of some or all of an individuals names, but not the surname(s). ( 2.5.4.43 NAME 'initials' SUP name ) 3.21 internationalISDNNumber A value of this attribute is an ISDN address, as defined in CCITT Recommendation E.164. ( 2.5.4.25 NAME 'internationalISDNNumber' EQUALITY numericStringMatch SUBSTR numericStringSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{16} ) ; NumericString 3.22 knowledgeInformation This attribute is superseded by the system schema attributes which hold the pointers to other LDAP servers. ( 2.5.4.2 NAME 'knowledgeInformation' EQUALITY caseIgnoreMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{32768} ) ; DirectoryString 3.23 l This is the X.500 localityName attribute, which contains the name of a locality, such as a city, county or other geographic region. ( 2.5.4.7 NAME 'l' SUP name ) 3.24 member A value of this attribute is the Distinguished Name of an object that is on a list or in a group. Dally Expires 20 May 2002 [Page 10]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 ( 2.5.4.31 NAME 'member' SUP distinguishedName ) 3.25 name The name attribute type is the attribute supertype from which string attribute types typically used for naming may be formed. It is unlikely that values of this type itself will occur in an entry. LDAP server implementations which do not support attribute subtyping need not recognize this attribute in requests. Client implementations MUST NOT assume that LDAP servers are capable of performing attribute subtyping. ( 2.5.4.41 NAME 'name' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{32768} ) ; DirectoryString 3.26 o This is the X.500 organizationName attribute, which contains the name of an organization. ( 2.5.4.10 NAME 'o' SUP name ) 3.27 objectClass The values of the objectClass attribute describe the kind of object which an entry represents. The objectClass attribute is present in every entry. ( 2.5.4.0 NAME 'objectClass' EQUALITY objectIdentifierMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.38 ) ; OID 3.28 ou This is the X.500 organizationalUnitName attribute, which contains the name of an organizational unit. ( 2.5.4.11 NAME 'ou' SUP name ) 3.29 owner A value of this attribute is the Distinguished Name of an object that has an ownership responsibility for the object that is owned. Dally Expires 20 May 2002 [Page 11]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 ( 2.5.4.32 NAME 'owner' SUP distinguishedName ) 3.30 physicalDeliveryOfficeName This attribute contains the name that a Postal Service uses to identify a post office. ( 2.5.4.19 NAME 'physicalDeliveryOfficeName' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{128} ) ; DirectoryString 3.31 postalAddress This attribute contains an address used by a Postal Service to perform services for the object. ( 2.5.4.16 NAME 'postalAddress' EQUALITY caseIgnoreListMatch SUBSTR caseIgnoreListSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.41 ) ; PostalAddress 3.32 postalCode This attribute contains a code used by a Postal Service to identify a postal service zone, such as the southern quadrant of a city. ( 2.5.4.17 NAME 'postalCode' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{40} ) ; DirectoryString 3.33 postOfficeBox This attribute contains the number that a Postal Service uses when a customer arranges to receive mail at a box on premises of the Postal Service. ( 2.5.4.18 NAME 'postOfficeBox' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{40} ) ; DirectoryString 3.34 preferredDeliveryMethod This attribute contains an indication of the preferred method of getting a message to the object. Dally Expires 20 May 2002 [Page 12]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 ( 2.5.4.28 NAME 'preferredDeliveryMethod' SYNTAX 1.3.6.1.4.1.1466.115.121.1.14 ; DeliveryMethod SINGLE-VALUE ) 3.35 presentationAddress This attribute contains an OSI presentation address. ( 2.5.4.29 NAME 'presentationAddress' EQUALITY presentationAddressMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.43 ; PresentationAddress SINGLE-VALUE ) 3.36 protocolInformation This attribute is used in conjunction with the presentationAddress attribute, to provide additional information to the OSI network service. ( 2.5.4.48 NAME 'protocolInformation' EQUALITY protocolInformationMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.42 ) ; ProtocolInformation 3.37 registeredAddress This attribute holds a postal address suitable for reception of telegrams or expedited documents, where it is necessary to have the recipient accept delivery. ( 2.5.4.26 NAME 'registeredAddress' SUP postalAddress SYNTAX 1.3.6.1.4.1.1466.115.121.1.41 ) ; PostalAddress 3.38 roleOccupant A value of this attribute is the Distinguished Name of an object (normally a person) that fulfills the responsibilities of a role object. ( 2.5.4.33 NAME 'roleOccupant' SUP distinguishedName ) 3.39 searchGuide This attribute is for use by clients in constructing search filters. It is superseded by enhancedSearchGuide, described above in 3.15. ( 2.5.4.14 NAME 'searchGuide' SYNTAX 1.3.6.1.4.1.1466.115.121.1.25 ) ; Guide Dally Expires 20 May 2002 [Page 13]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 3.40 seeAlso A value of this attribute is the Distinguished Name of an object that is related to the subject object. ( 2.5.4.34 NAME 'seeAlso' SUP distinguishedName ) 3.41 serialNumber This attribute contains the serial number of a device. ( 2.5.4.5 NAME 'serialNumber' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.44{64} ) ; PrintableString 3.42 sn This is the X.500 surname attribute, which contains the family name of a person. ( 2.5.4.4 NAME 'sn' SUP name ) 3.43 st This is the X.500 stateOrProvinceName attribute, which contains the full name of a state or province. ( 2.5.4.8 NAME 'st' SUP name ) 3.44 street This is the X.500 streetAddress attribute, which contains the physical address of the object to which the entry corresponds, such as an address for package delivery. ( 2.5.4.9 NAME 'street' EQUALITY caseIgnoreMatch SUBSTR caseIgnoreSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{128} ) DirectoryString 3.45 supportedAlgorithms This attribute contains the identifiers of cryptographic algorithms that the object implements. This attribute is to be stored and requested in the binary form, as 'supportedAlgorithms;binary'. Dally Expires 20 May 2002 [Page 14]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 ( 2.5.4.52 NAME 'supportedAlgorithms' SYNTAX 1.3.6.1.4.1.1466.115.121.1.49 ) ; SupportedAlgorithm 3.46 supportedApplicationContext This attribute contains the identifiers of OSI application contexts. ( 2.5.4.30 NAME 'supportedApplicationContext' EQUALITY objectIdentifierMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.38 ) ; OID 3.47 telephoneNumber A value of this attribute is a telephone number complying with CCITT Rec. E.123. ( 2.5.4.20 NAME 'telephoneNumber' EQUALITY telephoneNumberMatch SUBSTR telephoneNumberSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.50{32} ) ; TelephoneNumber 3.48 teletexTerminalIdentifier The withdrawal of Rec. F.200 has resulted in the withdrawal of this attribute. ( 2.5.4.22 NAME 'teletexTerminalIdentifier' SYNTAX 1.3.6.1.4.1.1466.115.121.1.51 ) ; TeletexTerminalIdentifier 3.49 telexNumber A value of this attribute is a telex number , country code, and answerback code of a telex terminal. ( 2.5.4.21 NAME 'telexNumber' SYNTAX 1.3.6.1.4.1.1466.115.121.1.52 ) ; TelexNumber 3.50 title This attribute contains the title, such as "Vice President", of a person in their organizational context. The "personalTitle" attribute would be used for a person's title independent of their job function. ( 2.5.4.12 NAME 'title' SUP name ) Dally Expires 20 May 2002 [Page 15]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 3.51 uniqueMember A value of this attribute is the Distinguished Name of an object that is on a list or in a group, where the Relative Distinguished Name of the object includes a value that distinguishs between objects when a distinguished name has been reused. ( 2.5.4.50 NAME 'uniqueMember' EQUALITY uniqueMemberMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.34 ) ; NameAndOptionalUID 3.52 userCertificate A value of this attribute is a set of information that is used to protect business systems, including the directory system and its contents, from a number of threats. The protection is realized by verifying the object is authorized to use the business system for certain purposes. This attribute is to be stored and requested in the binary form, as 'userCertificate;binary'. ( 2.5.4.36 NAME 'userCertificate' SYNTAX 1.3.6.1.4.1.1466.115.121.1.8 ) ; Certificate 3.53 userPassword A value of this attribute is a character string that is known only to the user and the system to which the user has access. ( 2.5.4.35 NAME 'userPassword' EQUALITY octetStringMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.40{128} ) ; OctetString Passwords are stored using an Octet String syntax and are not encrypted. Transfer of cleartext passwords is strongly discouraged where the underlying transport service cannot guarantee confidentiality and may result in disclosure of the password to unauthorized parties. 3.54 x121Address A value of this attribute is a data network address as defined by CCITT Recommendation X.121. ( 2.5.4.24 NAME 'x121Address' EQUALITY numericStringMatch SUBSTR numericStringSubstringsMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{15} ) ; NumericString Dally Expires 20 May 2002 [Page 16]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 3.55 x500UniqueIdentifier The x500UniqueIdentifier attribute is used to distinguish between objects when a distinguished name has been reused. In X.500, this attribute is called uniqueIdentifier. This is a different attribute type from both the "uid" and "uniqueIdentifier" (defined in ??) types. ( 2.5.4.45 NAME 'x500UniqueIdentifier' EQUALITY bitStringMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.6 ) ; BitString Dally Expires 20 May 2002 [Page 17]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 4. Object Classes LDAP servers MUST recognize the object class "top". LDAP servers SHOULD recognize all the other object classes listed here as values of the objectClass attribute. 4.1 alias The alias object class enables more than one Distinguished Name to designate an entry by providing an alias entry. The alias entry contains a pointer to the other entry. The pointer is automatically followed when the alias entry is found in the process of locating the target entry(s) of an operation. ( 2.5.6.1 NAME 'alias' SUP top STRUCTURAL MUST aliasedObjectName ) 4.2 applicationEntity The applicationEntity object class definition is the basis of an entry which represents the interconnection aspects of an application process in a distributed environment. ( 2.5.6.12 NAME 'applicationEntity' SUP top STRUCTURAL MUST ( presentationAddress $ cn ) MAY ( supportedApplicationContext $ seeAlso $ ou $ o $ l $ description ) ) 4.3 applicationProcess The applicationProcess object class definition is the basis of an entry which represents an application executing in a computer system. ( 2.5.6.11 NAME 'applicationProcess' SUP top STRUCTURAL MUST cn MAY ( seeAlso $ ou $ l $ description ) ) 4.4 certificationAuthority The certificationAuthority object class is the collection of attributes that are needed in an entry which represents an issuer of certificates in a security system. Dally Expires 20 May 2002 [Page 18]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 ( 2.5.6.16 NAME 'certificationAuthority' SUP top AUXILIARY MUST ( authorityRevocationList $ certificateRevocationList $ cACertificate ) MAY crossCertificatePair ) 4.5 certificationAuthority-V2 The certificationAuthority-V2 object class adds the deltaRevocationList attribute to the collection in the certificationAuthority object class, as an option. ( 2.5.6.16.2 NAME 'certificationAuthority-V2' SUP certificationAuthority AUXILIARY MAY ( deltaRevocationList ) ) 4.6 country The country object class definition is the basis of an entry which represents a country. ( 2.5.6.2 NAME 'country' SUP top STRUCTURAL MUST c MAY ( searchGuide $ description ) ) 4.7 cRLDistributionPoint The cRLDistributionPoint object class is the basis of an entry which represents a source of certificate revocation lists in a security system. ( 2.5.6.19 NAME 'cRLDistributionPoint' SUP top STRUCTURAL MUST ( cn ) MAY ( certificateRevocationList $ authorityRevocationList $ deltaRevocationList ) ) 4.8 device The device object class is the basis of an entry which represents an appliance or computer or network element. Dally Expires 20 May 2002 [Page 19]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 ( 2.5.6.14 NAME 'device' SUP top STRUCTURAL MUST cn MAY ( serialNumber $ seeAlso $ owner $ ou $ o $ l $ description ) ) 4.9 dmd The dmd object class is the basis of an entry which represents the set of one or more DSAs and zero or more DUAs managed by a single organization, i.e., a Directory Management Domain. ( 2.5.6.20 NAME 'dmd' SUP top STRUCTURAL MUST ( dmdName ) MAY ( userPassword $ searchGuide $ seeAlso $ businessCategory $ x121Address $ registeredAddress $ destinationIndicator $ preferredDeliveryMethod $ telexNumber $ teletexTerminalIdentifier $ telephoneNumber $ internationaliSDNNumber $ facsimileTelephoneNumber $ street $ postOfficeBox $ postalCode $ postalAddress $ physicalDeliveryOfficeName $ st $ l $ description ) ) 4.10 dSA The dSA (Directory System Agent) object class is the basis of an entry which represents a server in a directory system. ( 2.5.6.13 NAME 'dSA' SUP applicationEntity STRUCTURAL MAY knowledgeInformation ) 4.11 groupOfNames The groupOfNames object class is the basis of an entry which represents a set of named objects including information related to the purpose or maintenance of the set. ( 2.5.6.9 NAME 'groupOfNames' SUP top STRUCTURAL MUST ( member $ cn ) MAY ( businessCategory $ seeAlso $ owner $ ou $ o $ description ) ) Dally Expires 20 May 2002 [Page 20]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 4.12 groupOfUniqueNames The groupOfUniqueNames object class is the same as the groupOfNames object class except that the object names are not repeated or reassigned within a set scope. ( 2.5.6.17 NAME 'groupOfUniqueNames' SUP top STRUCTURAL MUST ( uniqueMember $ cn ) MAY ( businessCategory $ seeAlso $ owner $ ou $ o $ description ) ) 4.13 locality The locality object class is the basis of an entry which represents a place in the physical world. ( 2.5.6.3 NAME 'locality' SUP top STRUCTURAL MAY ( street $ seeAlso $ searchGuide $ st $ l $ description ) ) 4.14 organization The organization object class is the basis of an entry which represents a structured group of people. ( 2.5.6.4 NAME 'organization' SUP top STRUCTURAL MUST o MAY ( userPassword $ searchGuide $ seeAlso $ businessCategory $ x121Address $ registeredAddress $ destinationIndicator $ preferredDeliveryMethod $ telexNumber $ teletexTerminalIdentifier $ telephoneNumber $ internationaliSDNNumber $ facsimileTelephoneNumber $ street $ postOfficeBox $ postalCode $ postalAddress $ physicalDeliveryOfficeName $ st $ l $ description ) ) 4.15 organizationalPerson The organizationalPerson object class is the basis of an entry which represents a person in relation to an organization. Dally Expires 20 May 2002 [Page 21]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 ( 2.5.6.7 NAME 'organizationalPerson' SUP person STRUCTURAL MAY ( title $ x121Address $ registeredAddress $ destinationIndicator $ preferredDeliveryMethod $ telexNumber $ teletexTerminalIdentifier $ telephoneNumber $ internationaliSDNNumber $ facsimileTelephoneNumber $ street $ postOfficeBox $ postalCode $ postalAddress $ physicalDeliveryOfficeName $ ou $ st $ l ) ) 4.16 organizationalRole The organizationalRole object class is the basis of an entry which represents a job or function or position in an organization. ( 2.5.6.8 NAME 'organizationalRole' SUP top STRUCTURAL MUST cn MAY ( x121Address $ registeredAddress $ destinationIndicator $ preferredDeliveryMethod $ telexNumber $ teletexTerminalIdentifier $ telephoneNumber $ internationaliSDNNumber $ facsimileTelephoneNumber $ seeAlso $ roleOccupant $ preferredDeliveryMethod $ street $ postOfficeBox $ postalCode $ postalAddress $ physicalDeliveryOfficeName $ ou $ st $ l $ description ) ) 4.17 organizationalUnit The organizationalUnit object class is the basis of an entry which represents a piece of an organization. ( 2.5.6.5 NAME 'organizationalUnit' SUP top STRUCTURAL MUST ou MAY ( userPassword $ searchGuide $ seeAlso $ businessCategory $ x121Address $ registeredAddress $ destinationIndicator $ preferredDeliveryMethod $ telexNumber $ teletexTerminalIdentifier $ telephoneNumber $ internationaliSDNNumber $ facsimileTelephoneNumber $ street $ postOfficeBox $ postalCode $ postalAddress $ physicalDeliveryOfficeName $ st $ l $ description ) ) Dally Expires 20 May 2002 [Page 22]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 4.18 person The person object class is the basis of an entry which represents a human being. ( 2.5.6.6 NAME 'person' SUP top STRUCTURAL MUST ( sn $ cn ) MAY ( userPassword $ telephoneNumber $ seeAlso $ description ) ) 4.19 residentialPerson The residentialPerson object class is the basis of an entry which includes a person's residence in the representation of the person. ( 2.5.6.10 NAME 'residentialPerson' SUP person STRUCTURAL MUST l MAY ( businessCategory $ x121Address $ registeredAddress $ destinationIndicator $ preferredDeliveryMethod $ telexNumber $ teletexTerminalIdentifier $ telephoneNumber $ internationaliSDNNumber $ facsimileTelephoneNumber $ preferredDeliveryMethod $ street $ postOfficeBox $ postalCode $ postalAddress $ physicalDeliveryOfficeName $ st $ l ) ) 4.20 strongAuthenticationUser The strongAuthenticationUser object class adds the userCertificate attribute, as a mandatory attribute, to the collection of attributes in an entry. ( 2.5.6.15 NAME 'strongAuthenticationUser' SUP top AUXILIARY MUST userCertificate ) 4.21 top The top object class is the conceptual beginning of the inheritance hierarchy of object classes. Top guarantees that every entry has the objectClass attribute, which identifies the type of the entry. ( 2.5.6.0 NAME 'top' ABSTRACT MUST objectClass ) Dally Expires 20 May 2002 [Page 23]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 4.22 userSecurityInformation The userSecurityInformation object class adds the supportedAlgorithms attribute, as an optional attribute, to the collection of attributes in an entry. ( 2.5.6.18 NAME 'userSecurityInformation' SUP top AUXILIARY MAY ( supportedAlgorithms ) ) 5. Security Considerations Attributes of directory entries are used to provide descriptive information about the real-world objects they represent, which can be people, organizations or devices. Most countries have privacy laws regarding the publication of information about people. Transfer of cleartext passwords is strongly discouraged where the underlying transport service cannot guarantee confidentiality and may result in disclosure of the password to unauthorized parties. It is required that strong authentication be performed in order to modify directory entries using LDAP. 6. Acknowledgements The definitions, on which this document is based, have been developed by committees for telecommunications and international standards. No new attribute definitions have been added. This document is an update of RFC 2256 by Mark Wahl. RFC 2256 was a product of the IETF ASID Working Group. This document is based upon input of the IETF LDAPBIS working group. The authors wish to thank ___ for their significant contribution to this update. Dally Expires 20 May 2002 [Page 24]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 7. References [1] replacement (draft-ietf-ldapbis-syntaxes-01) for Wahl, M., Coulbeck, A., Howes, T., and S. Kille, "Lightweight X.500 Directory Access Protocol(v3): Attribute Syntax Definitions", RFC 2252, December 1997 [2] The Directory: Models, ITU-T Recommendation X.501, 1995 [3] The Directory: Authentication Framework, ITU-T Recommendation X.509, 1995 [4] The Directory: Selected Attribute Types, ITU-T Recommendation X.520, 1995 [5] The Directory: Selected Object Classes. ITU-T Recommendation X.521, 1995 [6] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, March 1997 8. Author's Address Kathy Dally The MITRE Corp. 1575 Colshire Dr., ms-W650 McLean VA 22102 USA Phone: +1 703 883 6058 Email: kdally@mitre.org Dally Expires 20 May 2002 [Page 25]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 Annex A Change Log This annex lists the changes that have been made from RFC 2256 to this I-D. Changes to RFC 2256 resulting in draft-ietf-ldapbis-user-schema-00.txt: 1. Revision of the Status of this Memo. 2. Dependencies on RFC 1274 have been eliminated. 3. The references to X.500(96) have been expressed in terms of the "edition", rather than the standard date. Note that the version of X.500 which is the basis for this document, is the third edition, which was finalized in 1996, but approved in 1997. 4. The "teletexTerminalNumber" attribute and syntax are marked as obsolete. 5. Removed "The syntax definitions are based on the ISODE "QUIPU" implementation of X.500." from section 6. 6. Added text to 6.1, the octetString syntax, in accordance with X.520. 7. Some of the attribute types MUST be recognized by servers. Also, several attributes are obsolete. Therefore, the various kinds of attribute types have been placed in separate sections: - necessary for the directory to operate (section 3.1) - for holding user information (section 3.2) - superseded or withdrawn (section 3.3). 8. Since "top" may be implicitly specified and "alias" is not abstract, the last sentence in the description of the "objectClass" attribute type, section 3.1.1, has been deleted. The clause that preceded the deleted sentence has been removed, also. 9. Add a description to the definition of the "telephoneNumber" attribute type, section 3.2.17. 10. Add text to mark the "teletexTerminalIdentifier" attribute type as obsolete. Dally Expires 20 May 2002 [Page 26]
INTERNET-DRAFT draft-ietf-ldapbis-user-schema-01 20 November 2001 11. Add a security consideration requiring strong authentication in order to modify directory entries. Changes to draft-ietf-ldapbis-user-schema-00.txt, resulting in draft- ietf-ldapbis-user-schema-01.txt: 12. Delete the conformance requirement for subschema object classes in favor of a statement in [1]. 13. Add a Table of Contents 14. Replace the term "obsolete" with "superseded or withdrawn" 15. Added explanations to many attributes. 16. In the title, correct the X.500 reference to have the second edition as the basis. 17. Throughout this I-D, cleaned up whitespace in the BNF definitions. 18. Removed Section 4, Syntaxes, and Section 6, Matching Rules, (moved to draft-ietf-ldapbis-syntaxes-01.txt). 19. Reorganized Section 3, Attributes, to eliminate grouping attributes according to conformance requirements. Reordered Section 3, Attributes, and Section 4, Object Classes, alphabetically. 20. Added an explanation for each object class. Dally Expires 20 May 2002 [Page 27]
