[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 04 05 06 07 08 09 10 11 RFC 4519

INTERNET-DRAFT                                          K. Dally, Editor
Intended Category:  Standard Track                       The MITRE Corp.
Expires 27 August 2002                                  27 February 2002
Obsoletes:  RFC 2256



   A Summary of the X.500(2nd edition) User Schema for use with LDAPv3
                  <draft-ietf-ldapbis-user-schema-02>


   [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
   LDAP (v3) 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 RFC 2026.

   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 27 August 2002                [Page 1]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


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 [KEYWD].








































Dally                   Expires 27 August 2002                  [Page 2]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


                           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  businessCategory                                                  6
3.3  c                                                                 6
3.4  cn                                                                7
3.5  description                                                       7
3.6  destinationIndicator                                              7
3.7  distinguishedName                                                 7
3.8  dnQualifier                                                       8
3.9  enhancedSearchGuide                                               8
3.10 facsimileTelephoneNumber                                          8
3.11 generationQualifier                                               8
3.12 givenName                                                         8
3.13 houseIdentifier                                                   9
3.14 initials                                                          9
3.15 internationalISDNNumber                                           9
3.16 knowledgeInformation                                              9
3.17 l                                                                 9
3.18 member                                                           10
3.19 name                                                             10
3.20 o                                                                10
3.21 objectClass                                                      10
3.22 ou                                                               10
3.23 owner                                                            11
3.24 physicalDeliveryOfficeName                                       11
3.25 postalAddress                                                    11
3.26 postalCode                                                       11
3.27 postOfficeBox                                                    11
3.28 preferredDeliveryMethod                                          12
3.29 presentationAddress                                              12
3.30 protocolInformation                                              12
3.31 registeredAddress                                                12
3.32 roleOccupant                                                     13
3.33 searchGuide                                                      13
3.34 seeAlso                                                          13
3.35 serialNumber                                                     13
3.36 sn                                                               13
3.37 st                                                               13
3.38 street                                                           14
3.39 supportedApplicationContext                                      14
3.40 telephoneNumber                                                  14
3.41 teletexTerminalIdentifier                                        14


Dally                   Expires 27 August 2002                  [Page 3]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


3.42 telexNumber                                                      15
3.43 title                                                            15
3.44 uniqueMember                                                     15
3.45 userPassword                                                     15
3.46 x121Address                                                      16
3.47 x500UniqueIdentifier                                             16

4.  Object Classes                                                    17
4.1  alias                                                            17
4.2  applicationEntity                                                17
4.3  applicationProcess                                               17
4.4  country                                                          18
4.5  device                                                           18
4.6  dSA                                                              18
4.7  groupOfNames                                                     18
4.8  groupOfUniqueNames                                               19
4.9  locality                                                         19
4.10 organization                                                     19
4.11 organizationalPerson                                             20
4.12 organizationalRole                                               20
4.13 organizationalUnit                                               20
4.14 person                                                           21
4.15 residentialPerson                                                21
4.16 top                                                              21

5.  Security Considerations                                           22

6.  Acknowledgements                                                  22

7.  References                                                        23
7.1  Normative                                                        23
7.2  Informative                                                      23

8.  Author's Address                                                  24

Annex A  Change Log                                                   25


















Dally                   Expires 27 August 2002                  [Page 4]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


1. General Issues

   This document references Syntaxes given in Section 3 of [SYNTAX] and
   Matching Rules specified in Section 4 of [SYNTAX].

   The Attribute Type and Object Class definitions are written using the
   ABNF form of AttributeTypeDescription and ObjectClassDescription
   given in [SYNTAX].  Lines have been folded for readability.


2. Source

   The schema definitions in this document are based on those found in
   X.500 [X501], [X509], [X520], and [X521], specifically:

        Sections             Source
        ============         ============
        3.1                  X.501 [X501]
        3.2  - 3.20          X.520 [X520]
        3.21                 X.501 [X501]
        3.22 - 3.44          X.520 [X520]
        3.45                 X.509 [X509]
        3.46 - 3.47          X.520 [X520]
        4.1                  X.501 [X501]
        4.2  - 4.15          X.521 [X521]
        4.16                 X.501 [X501]




























Dally                   Expires 27 August 2002                  [Page 5]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


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 Type is used by the directory
   service if the entry containing this attribute is an alias.  In
   X.501 [X501], this Attribute Type is called aliasedEntryName.

   ( 2.5.4.1 NAME 'aliasedObjectName'
      EQUALITY distinguishedNameMatch
      SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
      SINGLE-VALUE )

   The SYNTAX oid indicates the DN syntax.

3.2  businessCategory

   This Attribute Type 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} )

   The SYNTAX oid indicates the Directory String syntax.

3.3  c

   This is the X.520 [X520] countryName Attribute Type, which contains
   a two-letter ISO 3166 [Codes]country code.

   ( 2.5.4.6 NAME 'c'
      SUP name
      SINGLE-VALUE )


Dally                   Expires 27 August 2002                  [Page 6]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


3.4  cn

   This is the X.520 [X520] commonName Attribute Type, 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.5  description

   This Attribute Type 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} )

   The SYNTAX oid indicates the Directory String syntax.

3.6  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} )

   The SYNTAX oid indicates the Printable String syntax.

3.7  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 )

   The SYNTAX oid indicates the DN syntax.





Dally                   Expires 27 August 2002                  [Page 7]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


3.8  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 )

   The SYNTAX oid indicates the Printable String syntax.

3.9  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 )

   The SYNTAX oid indicates the Enhanced Guide syntax.

3.10  facsimileTelephoneNumber

   A value of this Attribute Type 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 )

   The SYNTAX oid indicates the Facsimile Telephone Number syntax.

3.11  generationQualifier

   The generationQualifier Attribute Type contains the part of a
   person's name which typically is the suffix, as in "IIIrd".

   ( 2.5.4.44 NAME 'generationQualifier'
      SUP name )

3.12 givenName

   The givenName Attribute Type 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 27 August 2002                  [Page 8]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


3.13  houseIdentifier

   This Attribute Type 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} )

   The SYNTAX oid indicates the Directory String syntax.

3.14  initials

   The initials Attribute Type contains the initials of some or all of
   an individuals names, except the surname(s).

    ( 2.5.4.43 NAME 'initials'
      SUP name )

3.15  internationalISDNNumber

   A value of this Attribute Type is an ISDN address, as defined in
   ITU Recommendation E.164 [ISDN].

   ( 2.5.4.25 NAME 'internationalISDNNumber'
      EQUALITY numericStringMatch
      SUBSTR numericStringSubstringsMatch
      SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{16} ) i

   The SYNTAX oid indicates the Numeric String syntax.

3.16  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} )

   The SYNTAX oid indicates the Directory String syntax.

3.17  l

   This is the X.520 [X520] localityName Attribute Type, which contains
   the name of a locality or place, such as a city, county or other
   geographic region.

    ( 2.5.4.7 NAME 'l'
      SUP name )




Dally                   Expires 27 August 2002                  [Page 9]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


3.18  member

   A value of this Attribute Type is the Distinguished Name of an
   object that is on a list or in a group.

   ( 2.5.4.31 NAME 'member'
      SUP distinguishedName )

3.19  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} )

   The SYNTAX oid indicates the Directory String syntax.

3.20  o

   This is the X.520 [X520] organizationName Attribute Type, which
   contains the name of an organization.

   ( 2.5.4.10 NAME 'o'
      SUP name )

3.21 objectClass

   The values of the objectClass Attribute Type 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 )

The SYNTAX oid indicates the OID syntax.

3.22  ou

   This is the X.520 [X520] organizationalUnitName Attribute Type,
   which contains the name of an organizational unit.

    ( 2.5.4.11 NAME 'ou'
      SUP name )


Dally                   Expires 27 August 2002                 [Page 10]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


3.23  owner

   A value of this Attribute Type is the Distinguished Name of an
   object that has an ownership responsibility for the object that
   is owned.

    ( 2.5.4.32 NAME 'owner'
      SUP distinguishedName )

3.24  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} )

   The SYNTAX oid indicates the Directory String syntax.

3.25  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 )

   The SYNTAX oid indicates the Postal Address syntax.

3.26  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} )

   The SYNTAX oid indicates the Directory String syntax.

3.27  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.




Dally                   Expires 27 August 2002                 [Page 11]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


   ( 2.5.4.18 NAME 'postOfficeBox'
      EQUALITY caseIgnoreMatch
      SUBSTR caseIgnoreSubstringsMatch
      SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{40} )

   The SYNTAX oid indicates the Directory String syntax.

3.28  preferredDeliveryMethod

   This attribute contains an indication of the preferred method of
   getting a message to the object.

   ( 2.5.4.28 NAME 'preferredDeliveryMethod'
      SYNTAX 1.3.6.1.4.1.1466.115.121.1.14
      SINGLE-VALUE )

   The SYNTAX oid indicates the Delivery Method syntax.

3.29  presentationAddress

   This attribute contains an OSI presentation layer address.

   ( 2.5.4.29 NAME 'presentationAddress'
      EQUALITY presentationAddressMatch
      SYNTAX 1.3.6.1.4.1.1466.115.121.1.43
      SINGLE-VALUE )

The SYNTAX oid indicates the Presentation Address syntax.

3.30  protocolInformation

   This Attribute Type is used in conjunction with the
   presentationAddress Attribute Type, 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 )

The SYNTAX oid indicates the Protocol Information syntax.

3.31 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 )

   The SYNTAX oid indicates the Postal Address syntax.


Dally                   Expires 27 August 2002                 [Page 12]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


3.32  roleOccupant

   A value of this Attribute Type 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.33  searchGuide

   This Attribute Type is for use by clients in constructing search
   filters.  It is superseded by enhancedSearchGuide, described above
   in section 3.9.

   ( 2.5.4.14 NAME 'searchGuide'
      SYNTAX 1.3.6.1.4.1.1466.115.121.1.25 )  ; Guide

The SYNTAX oid indicates the Guide syntax.

3.34  seeAlso

   A value of this Attribute Type is the Distinguished Name of an
   object that is related to the subject object.

    ( 2.5.4.34 NAME 'seeAlso'
      SUP distinguishedName )

3.35  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} )

   The SYNTAX oid indicates the Printable String syntax.

3.36  sn

   This is the X.520 [X520] surname Attribute Type, which contains the
   family name of a person.

   ( 2.5.4.4 NAME 'sn'
      SUP name )

3.37  st

   This is the X.520 [X520] stateOrProvinceName attribute, which
   contains the full name of a state or province.



Dally                   Expires 27 August 2002                 [Page 14]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


   ( 2.5.4.8 NAME 'st'
      SUP name )

3.44 street

   This is the X.520 [X520] 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} )

   The SYNTAX oid indicates the Directory String syntax.

3.39  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 )

   The SYNTAX oid indicates the OID syntax.

3.40  telephoneNumber

   A value of this Attribute Type is a telephone number complying with
   ITU Recommendation E.123 [E123].

   ( 2.5.4.20 NAME 'telephoneNumber'
     EQUALITY telephoneNumberMatch
     SUBSTR telephoneNumberSubstringsMatch
     SYNTAX 1.3.6.1.4.1.1466.115.121.1.50{32} )  ; TelephoneNumber

   The SYNTAX oid indicates the Telephone Number syntax.

3.41  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 )

   The SYNTAX oid indicates the Teletex Terminal Identifier syntax.






Dally                   Expires 27 August 2002                 [Page 14]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


3.42  telexNumber

   A value of this Attribute Type 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 )

   The SYNTAX oid indicates the Telex Number syntax.

3.43  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 )

3.44  uniqueMember

   A value of this Attribute Type 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 )

The SYNTAX oid indicates the Name and Optional UID syntax.

3.45  userPassword

   A value of this Attribute Type 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} )

   The SYNTAX oid indicates the Octet String syntax.

   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.





Dally                   Expires 27 August 2002                 [Page 15]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


3.46  x121Address

   A value of this Attribute Type is a data network address as defined
   by ITU Recommendation X.121 [X121].

   ( 2.5.4.24 NAME 'x121Address'
      EQUALITY numericStringMatch
      SUBSTR numericStringSubstringsMatch
      SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{15} )

   The SYNTAX oid indicates the Numeric String syntax.

3.55 x500UniqueIdentifier

   The x500UniqueIdentifier Attribute Type is used to distinguish
   between objects when a distinguished name has been reused.  In X.520
   [X520], this Attribute Type is called uniqueIdentifier.  This is a
   different Attribute Type from both the "uid" and "uniqueIdentifier"
   Attribute Types.

   ( 2.5.4.45 NAME 'x500UniqueIdentifier'
      EQUALITY bitStringMatch
      SYNTAX 1.3.6.1.4.1.1466.115.121.1.6 )

   The SYNTAX oid indicates the Bit String syntax.





























Dally                   Expires 27 August 2002                 [Page 16]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


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 ) )




Dally                   Expires 27 August 2002                 [Page 17]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


4.4  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.5  device

   The device Object Class is the basis of an entry which represents
   an appliance or computer or network element.

   ( 2.5.6.14 NAME 'device'
      SUP top
      STRUCTURAL
      MUST cn
      MAY ( serialNumber $
            seeAlso $
            owner $
            ou $
            o $
            l $
            description ) )

4.6  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.7  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 $


Dally                   Expires 27 August 2002                 [Page 18]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


            owner $
            ou $
            o $
            description ) )

4.8  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.9  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.10  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 $


Dally                   Expires 27 August 2002                 [Page 19]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


            street $ postOfficeBox $ postalCode $
            postalAddress $ physicalDeliveryOfficeName $ st $
            l $ description ) )

4.11  organizationalPerson

   The organizationalPerson Object Class is the basis of an entry which
   represents a person in relation to an organization.

   ( 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.12  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.13  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 27 August 2002                 [Page 20]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


4.14  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.15  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.16  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 27 August 2002                 [Page 21]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


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.

   Several X.500 Attribute Types and Object Classes, such as, the
   userCertificate Attribute Type or the certificationAuthority Object
   Class, are used to include key-based security information in
   directory entries.  The Attribute Types are:

      authorityRevocationList
      cACertificate
      certificateRevocationList
      crossCertificatePair
      deltaRevocationList
      supportedAlgorithms
      userCertificate

   The Object Classes are:

      certificationAuthority
      certificationAuthority-V2
      cRLDistributionPoint
      strongAuthenticationUser
      userSecurityInformation

   These Attribute Types and Object Classes are specified for LDAP by
   the PKIX Working Group, and so, are not included in this document.

   The BNF notation in RFC 1778 [Syn String] for User Certificate,
   Authority Revocation List, and Certificate Pair are not recommended
   to be used.


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.



Dally                   Expires 27 August 2002                 [Page 22]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


   This document is based upon input of the IETF LDAPBIS working group.
   The author wishes to thank S. Legg and K. Zeilenga for their
   significant contribution to this update.


7.  References

7.1  Normative

   [Codes]  ISO 3166, "Codes for the representation of names
      of countries".

   [E123]  Notation for national and international telephone numbers,
      ITU-T Recommendation E.123, 1988

   [ISDN]  The international public telecommunication numbering plan,
      ITU-T Recommendation E.164, 1997

   [KEYWD] Bradner, S., "Key words for use in RFCs to Indicate
      Requirement Levels", RFC 2119, March 1997

   [SYNTAX] replacement (draft-ietf-ldapbis-syntaxes-02) for Wahl, M.,
       Coulbeck, A., Howes, T., and S. Kille, "Lightweight X.500
       Directory Access Protocol(v3):  Attribute Syntax Definitions",
       RFC 2252, December 1997

   [X121] International numbering plan for public data networks,
      ITU-T Recommendation X.121, 1996

   [X501] The Directory:  Models, ITU-T Recommendation X.501, 1995

   [X509] The Directory:  Authentication Framework, ITU-T Recommendation
      X.509, 1995

   [X520] The Directory: Selected Attribute Types, ITU-T Recommendation
      X.520, 1995

   [X521] The Directory: Selected Object Classes.  ITU-T Recommendation
      X.521, 1995

7.2  Informative

   [Syn String]  Howes, T., Kille, S., Yeong, W., Robbins, C., "The
      String Representation of Standard Attribute Syntaxes", RFC 1778,
      March 1995.









Dally                   Expires 27 August 2002                 [Page 23]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


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 27 August 2002                 [Page 24]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


                          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 27 August 2002                 [Page 25]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


      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 [SYNTAX].

      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.

   Changes to draft-ietf-ldapbis-user-schema-01.txt, resulting in draft-
   ietf-ldapbis-user-schema-02.txt:

      21. Removed the certificate-related Attribute Types:
             authorityRevocationList,
             cACertificate,
             certificateRevocationList,
             crossCertificatePair,
             deltaRevocationList,
             supportedAlgorithms, and
             userCertificate.

          Removed the certificate-related Object Classes:
             certificationAuthority,
             certificationAuthority-V2,
             cRLDistributionPoint,
             strongAuthenticationUser, and
             userSecurityInformation

          Noted in the Security Considerations (Section 7) that they
          are covered in PKIX WG documents.


Dally                   Expires 27 August 2002                 [Page 26]

INTERNET-DRAFT      draft-ietf-ldapbis-user-schema-02   27 February 2002


      22. Removed the dmdName Attribute Type and dmd Object Class
          because they are not in the version of X.500 which
          is referenced.

      23. Removed embedded comments from the ABNF productions
          throughout the document.

      24. Cleaned up the references;  adopted word instead of number
          tags;  split Section 7 into normative and informative
          subsections.












































Dally                   Expires 27 August 2002                 [Page 27]


Html markup produced by rfcmarkup 1.109, available from https://tools.ietf.org/tools/rfcmarkup/