draft-ietf-asid-ldapv3schema-x500-03.txt   rfc2256.txt 
Network Working Group M. Wahl Network Working Group M. Wahl
INTERNET-DRAFT Critical Angle Inc. Request for Comments: 2256 Critical Angle Inc.
Expires in six months from 10 Oct. 1997 Category: Standards Track December 1997
A Summary of the X.500(96) User Schema for use with LDAPv3 A Summary of the X.500(96) User Schema for use with LDAPv3
<draft-ietf-asid-ldapv3schema-x500-03.txt>
1. Status of this Memo 1. Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document specifies an Internet standards track protocol for the
documents of the Internet Engineering Task Force (IETF), its areas, and Internet community, and requests discussion and suggestions for
its working groups. Note that other groups may also distribute working improvements. Please refer to the current edition of the "Internet
documents as Internet-Drafts. Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Internet-Drafts are draft documents valid for a maximum of six months Copyright Notice
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."
To learn the current status of any Internet-Draft, please check the Copyright (C) The Internet Society (1997). All Rights Reserved.
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), IESG Note
ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim).
This document describes a directory access protocol that provides
both read and update access. Update access requires secure
authentication, but this document does not mandate implementation of
any satisfactory authentication mechanisms.
In accordance with RFC 2026, section 4.4.1, this specification is
being approved by IESG as a Proposed Standard despite this
limitation, for the following reasons:
a. to encourage implementation and interoperability testing of
these protocols (with or without update access) before they
are deployed, and
b. to encourage deployment and use of these protocols in read-only
applications. (e.g. applications where LDAPv3 is used as
a query language for directories which are updated by some
secure mechanism other than LDAP), and
c. to avoid delaying the advancement and deployment of other Internet
standards-track protocols which require the ability to query, but
not update, LDAPv3 directory servers.
Readers are hereby warned that until mandatory authentication
mechanisms are standardized, clients and servers written according to
this specification which make use of update functionality are
UNLIKELY TO INTEROPERATE, or MAY INTEROPERATE ONLY IF AUTHENTICATION
IS REDUCED TO AN UNACCEPTABLY WEAK LEVEL.
Implementors are hereby discouraged from deploying LDAPv3 clients or
servers which implement the update functionality, until a Proposed
Standard for mandatory authentication in LDAPv3 has been approved and
published as an RFC.
2. Abstract 2. Abstract
This document provides an overview of the attribute types and object This document provides an overview of the attribute types and object
classes defined by the ISO and ITU-T committees in the X.500 classes defined by the ISO and ITU-T committees in the X.500
documents, in particular those intended for use by directory clients. documents, in particular those intended for use by directory clients.
This is the most widely used schema for LDAP/X.500 directories, and 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 many other schema definitions for white pages objects use it as a
basis. This document does not cover attributes used for the basis. This document does not cover attributes used for the
administration of X.500 directory servers, nor does it include administration of X.500 directory servers, nor does it include
attributes defined by other ISO/ITU-T documents. 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].
3. General Issues 3. General Issues
This document references syntaxes given in section 6 of this document This document references syntaxes given in section 6 of this document
and section 6 of [1]. Matching rules are listed in section 8 of this and section 6 of [1]. Matching rules are listed in section 8 of this
document and section 8 of [1]. document and section 8 of [1].
The attribute type and object class definitions are written using the The attribute type and object class definitions are written using the
BNF form of AttributeTypeDescription and ObjectClassDescription given BNF form of AttributeTypeDescription and ObjectClassDescription given
in [1]. Lines have been folded for readability. in [1]. Lines have been folded for readability.
skipping to change at page 3, line 14 skipping to change at page 3, line 45
5.3. knowledgeInformation 5.3. knowledgeInformation
This attribute is no longer used. This attribute is no longer used.
( 2.5.4.2 NAME 'knowledgeInformation' EQUALITY caseIgnoreMatch ( 2.5.4.2 NAME 'knowledgeInformation' EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{32768} ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{32768} )
5.4. cn 5.4. cn
This is the X.500 commonName attribute, which contains a name of This is the X.500 commonName attribute, which contains a name of an
an object. If the object corresponds to a person, it is typically the object. If the object corresponds to a person, it is typically the
person's full name. person's full name.
( 2.5.4.3 NAME 'cn' SUP name ) ( 2.5.4.3 NAME 'cn' SUP name )
5.5. sn 5.5. sn
This is the X.500 surname attribute, which contains the family name of This is the X.500 surname attribute, which contains the family name
a person. of a person.
( 2.5.4.4 NAME 'sn' SUP name ) ( 2.5.4.4 NAME 'sn' SUP name )
5.6. serialNumber 5.6. serialNumber
This attribute contains the serial number of a device. This attribute contains the serial number of a device.
( 2.5.4.5 NAME 'serialNumber' EQUALITY caseIgnoreMatch ( 2.5.4.5 NAME 'serialNumber' EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringsMatch SUBSTR caseIgnoreSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.44{64} ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.44{64} )
skipping to change at page 4, line 33 skipping to change at page 5, line 23
This attribute contains the name of an organizational unit This attribute contains the name of an organizational unit
(organizationalUnitName). (organizationalUnitName).
( 2.5.4.11 NAME 'ou' SUP name ) ( 2.5.4.11 NAME 'ou' SUP name )
5.13. title 5.13. title
This attribute contains the title, such as "Vice President", of a This attribute contains the title, such as "Vice President", of a
person in their organizational context. The "personalTitle" person in their organizational context. The "personalTitle"
attribute would be used for a person's title independent of their attribute would be used for a person's title independent of their job
job function. function.
( 2.5.4.12 NAME 'title' SUP name ) ( 2.5.4.12 NAME 'title' SUP name )
5.14. description 5.14. description
This attribute contains a human-readable description of the object. This attribute contains a human-readable description of the object.
( 2.5.4.13 NAME 'description' EQUALITY caseIgnoreMatch ( 2.5.4.13 NAME 'description' EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringsMatch SUBSTR caseIgnoreSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{1024} ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{1024} )
skipping to change at page 5, line 10 skipping to change at page 5, line 50
5.48. 5.48.
( 2.5.4.14 NAME 'searchGuide' ( 2.5.4.14 NAME 'searchGuide'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.25 ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.25 )
5.16. businessCategory 5.16. businessCategory
This attribute describes the kind of business performed by an This attribute describes the kind of business performed by an
organization. organization.
( 2.5.4.15 NAME 'businessCategory' EQUALITY caseIgnoreMatch ( 2.5.4.15 NAME 'businessCategory' EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringsMatch SUBSTR caseIgnoreSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{128} ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{128} )
5.17. postalAddress 5.17. postalAddress
( 2.5.4.16 NAME 'postalAddress' EQUALITY caseIgnoreListMatch ( 2.5.4.16 NAME 'postalAddress' EQUALITY caseIgnoreListMatch
SUBSTR caseIgnoreListSubstringsMatch SUBSTR caseIgnoreListSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.41 ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.41 )
5.18. postalCode 5.18. postalCode
( 2.5.4.17 NAME 'postalCode' EQUALITY caseIgnoreMatch ( 2.5.4.17 NAME 'postalCode' EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringsMatch SUBSTR caseIgnoreSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{40} ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{40} )
5.19. postOfficeBox 5.19. postOfficeBox
( 2.5.4.18 NAME 'postOfficeBox' EQUALITY caseIgnoreMatch ( 2.5.4.18 NAME 'postOfficeBox' EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringsMatch SUBSTR caseIgnoreSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{40} ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{40} )
5.20. physicalDeliveryOfficeName 5.20. physicalDeliveryOfficeName
( 2.5.4.19 NAME 'physicalDeliveryOfficeName' EQUALITY caseIgnoreMatch ( 2.5.4.19 NAME 'physicalDeliveryOfficeName' EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringsMatch SUBSTR caseIgnoreSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{128} ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{128} )
5.21. telephoneNumber 5.21. telephoneNumber
( 2.5.4.20 NAME 'telephoneNumber' EQUALITY telephoneNumberMatch ( 2.5.4.20 NAME 'telephoneNumber' EQUALITY telephoneNumberMatch
SUBSTR telephoneNumberSubstringsMatch SUBSTR telephoneNumberSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.50{32} ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.50{32} )
5.22. telexNumber 5.22. telexNumber
( 2.5.4.21 NAME 'telexNumber' ( 2.5.4.21 NAME 'telexNumber'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.52 ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.52 )
5.23. teletexTerminalIdentifier 5.23. teletexTerminalIdentifier
( 2.5.4.22 NAME 'teletexTerminalIdentifier' ( 2.5.4.22 NAME 'teletexTerminalIdentifier'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.51 ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.51 )
5.24. facsimileTelephoneNumber 5.24. facsimileTelephoneNumber
( 2.5.4.23 NAME 'facsimileTelephoneNumber' ( 2.5.4.23 NAME 'facsimileTelephoneNumber'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.22 ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.22 )
5.25. x121Address 5.25. x121Address
( 2.5.4.24 NAME 'x121Address' EQUALITY numericStringMatch ( 2.5.4.24 NAME 'x121Address' EQUALITY numericStringMatch
SUBSTR numericStringSubstringsMatch SUBSTR numericStringSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{15} ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{15} )
5.26. internationaliSDNNumber 5.26. internationaliSDNNumber
( 2.5.4.25 NAME 'internationaliSDNNumber' EQUALITY numericStringMatch ( 2.5.4.25 NAME 'internationaliSDNNumber' EQUALITY numericStringMatch
SUBSTR numericStringSubstringsMatch SUBSTR numericStringSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{16} ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.36{16} )
5.27. registeredAddress 5.27. registeredAddress
This attribute holds a postal address suitable for reception of This attribute holds a postal address suitable for reception of
telegrams or expedited documents, where it is necessary to have the telegrams or expedited documents, where it is necessary to have the
recipient accept delivery. recipient accept delivery.
( 2.5.4.26 NAME 'registeredAddress' SUP postalAddress ( 2.5.4.26 NAME 'registeredAddress' SUP postalAddress
SYNTAX 1.3.6.1.4.1.1466.115.121.1.41 ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.41 )
skipping to change at page 8, line 17 skipping to change at page 9, line 36
This attribute is to be stored and requested in the binary form, as This attribute is to be stored and requested in the binary form, as
'crossCertificatePair;binary'. 'crossCertificatePair;binary'.
( 2.5.4.40 NAME 'crossCertificatePair' ( 2.5.4.40 NAME 'crossCertificatePair'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.10 ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.10 )
5.42. name 5.42. name
The name attribute type is the attribute supertype from which string The name attribute type is the attribute supertype from which string
attribute types typically used for naming may be formed. It is attribute types typically used for naming may be formed. It is
unlikely that values of this type itself will occur in an entry. unlikely that values of this type itself will occur in an entry. LDAP
LDAP server implementations which do not support attribute subtyping server implementations which do not support attribute subtyping need
need not recognize this attribute in requests. Client not recognize this attribute in requests. Client implementations
implementations MUST NOT assume that LDAP servers are capable of MUST NOT assume that LDAP servers are capable of performing attribute
performing attribute subtyping. subtyping.
( 2.5.4.41 NAME 'name' EQUALITY caseIgnoreMatch ( 2.5.4.41 NAME 'name' EQUALITY caseIgnoreMatch
SUBSTR caseIgnoreSubstringsMatch SUBSTR caseIgnoreSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{32768} ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.15{32768} )
5.43. givenName 5.43. givenName
The givenName attribute is used to hold the part of a person's name The givenName attribute is used to hold the part of a person's name
which is not their surname nor middle name. which is not their surname nor middle name.
skipping to change at page 9, line 7 skipping to change at page 10, line 31
The x500UniqueIdentifier attribute is used to distinguish between The x500UniqueIdentifier attribute is used to distinguish between
objects when a distinguished name has been reused. This is a objects when a distinguished name has been reused. This is a
different attribute type from both the "uid" and "uniqueIdentifier" different attribute type from both the "uid" and "uniqueIdentifier"
types. types.
( 2.5.4.45 NAME 'x500UniqueIdentifier' EQUALITY bitStringMatch ( 2.5.4.45 NAME 'x500UniqueIdentifier' EQUALITY bitStringMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.6 ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.6 )
5.47. dnQualifier 5.47. dnQualifier
The dnQualifier attribute type specifies disambiguating information to The dnQualifier attribute type specifies disambiguating information
add to the relative distinguished name of an entry. It is intended to add to the relative distinguished name of an entry. It is
for use when merging data from multiple sources in order to prevent intended for use when merging data from multiple sources in order to
conflicts between entries which would otherwise have the same name. prevent conflicts between entries which would otherwise have the same
It is recommended that the value of the dnQualifier attribute be the name. It is recommended that the value of the dnQualifier attribute
same for all entries from a particular source. be the same for all entries from a particular source.
( 2.5.4.46 NAME 'dnQualifier' EQUALITY caseIgnoreMatch ( 2.5.4.46 NAME 'dnQualifier' EQUALITY caseIgnoreMatch
ORDERING caseIgnoreOrderingMatch SUBSTR caseIgnoreSubstringsMatch ORDERING caseIgnoreOrderingMatch SUBSTR caseIgnoreSubstringsMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.44 ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.44 )
5.48. enhancedSearchGuide 5.48. enhancedSearchGuide
This attribute is for use by X.500 clients in constructing search This attribute is for use by X.500 clients in constructing search
filters. filters.
skipping to change at page 9, line 42 skipping to change at page 11, line 21
( 2.5.4.48 NAME 'protocolInformation' ( 2.5.4.48 NAME 'protocolInformation'
EQUALITY protocolInformationMatch EQUALITY protocolInformationMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.42 ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.42 )
5.50. distinguishedName 5.50. distinguishedName
This attribute type is not used as the name of the object itself, but 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 it is instead a base type from which attributes with DN syntax
inherit. inherit.
It is unlikely that values of this type itself will occur in an entry. It is unlikely that values of this type itself will occur in an
LDAP server implementations which do not support attribute subtyping entry. LDAP server implementations which do not support attribute
need not recognize this attribute in requests. Client subtyping need not recognize this attribute in requests. Client
implementations MUST NOT assume that LDAP servers are capable of implementations MUST NOT assume that LDAP servers are capable of
performing attribute subtyping. performing attribute subtyping.
( 2.5.4.49 NAME 'distinguishedName' EQUALITY distinguishedNameMatch ( 2.5.4.49 NAME 'distinguishedName' EQUALITY distinguishedNameMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.12 )
5.51. uniqueMember 5.51. uniqueMember
( 2.5.4.50 NAME 'uniqueMember' EQUALITY uniqueMemberMatch ( 2.5.4.50 NAME 'uniqueMember' EQUALITY uniqueMemberMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.34 ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.34 )
skipping to change at page 10, line 31 skipping to change at page 12, line 15
5.54. deltaRevocationList 5.54. deltaRevocationList
This attribute is to be stored and requested in the binary form, as This attribute is to be stored and requested in the binary form, as
'deltaRevocationList;binary'. 'deltaRevocationList;binary'.
( 2.5.4.53 NAME 'deltaRevocationList' ( 2.5.4.53 NAME 'deltaRevocationList'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.9 ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.9 )
5.55. dmdName 5.55. dmdName
The value of this attribute specifies a directory management The value of this attribute specifies a directory management domain
domain (DMD), the administrative authority which operates the (DMD), the administrative authority which operates the directory
directory server. server.
( 2.5.4.54 NAME 'dmdName' SUP name ) ( 2.5.4.54 NAME 'dmdName' SUP name )
6. Syntaxes 6. Syntaxes
Servers SHOULD recognize the syntaxes defined in this section. Servers SHOULD recognize the syntaxes defined in this section. Each
Each syntax begins with a sample value of the ldapSyntaxes attribute syntax begins with a sample value of the ldapSyntaxes attribute which
which defines the OBJECT IDENTIFIER of the syntax. The descriptions defines the OBJECT IDENTIFIER of the syntax. The descriptions of
of syntax names are not carried in protocol, and are not guaranteed syntax names are not carried in protocol, and are not guaranteed to
to be unique. be unique.
6.1. Delivery Method 6.1. Delivery Method
( 1.3.6.1.4.1.1466.115.121.1.14 DESC 'Delivery Method' ) ( 1.3.6.1.4.1.1466.115.121.1.14 DESC 'Delivery Method' )
Values in this syntax are encoded according to the following BNF: Values in this syntax are encoded according to the following BNF:
delivery-value = pdm / ( pdm whsp "$" whsp delivery-value ) delivery-value = pdm / ( pdm whsp "$" whsp delivery-value )
pdm = "any" / "mhs" / "physical" / "telex" / "teletex" / pdm = "any" / "mhs" / "physical" / "telex" / "teletex" /
skipping to change at page 11, line 11 skipping to change at page 12, line 50
Example: Example:
telephone telephone
6.2. Enhanced Guide 6.2. Enhanced Guide
( 1.3.6.1.4.1.1466.115.121.1.21 DESC 'Enhanced Guide' ) ( 1.3.6.1.4.1.1466.115.121.1.21 DESC 'Enhanced Guide' )
Values in this syntax are encoded according to the following BNF: Values in this syntax are encoded according to the following BNF:
EnhancedGuide = woid whsp "#" whsp criteria whsp "#" whsp subset EnhancedGuide = woid whsp "#" whsp criteria whsp "#" whsp subset
subset = "baseobject" / "oneLevel" / "wholeSubtree" subset = "baseobject" / "oneLevel" / "wholeSubtree"
The criteria production is defined in the Guide syntax below. The criteria production is defined in the Guide syntax below. This
This syntax has been added subsequent to RFC 1778. syntax has been added subsequent to RFC 1778.
Example: Example:
person#(sn)#oneLevel person#(sn)#oneLevel
6.3. Guide 6.3. Guide
( 1.3.6.1.4.1.1466.115.121.1.25 DESC 'Guide' ) ( 1.3.6.1.4.1.1466.115.121.1.25 DESC 'Guide' )
Values in this syntax are encoded according to the following BNF: Values in this syntax are encoded according to the following BNF:
guide-value = [ object-class "#" ] criteria guide-value = [ object-class "#" ] criteria
object-class = woid object-class = woid
criteria = criteria-item / criteria-set / ( "!" criteria ) criteria = criteria-item / criteria-set / ( "!" criteria )
criteria-set = ( [ "(" ] criteria "&" criteria-set [ ")" ] ) / criteria-set = ( [ "(" ] criteria "&" criteria-set [ ")" ] ) /
( [ "(" ] criteria "|" criteria-set [ ")" ] ) ( [ "(" ] criteria "|" criteria-set [ ")" ] )
criteria-item = [ "(" ] attributetype "$" match-type [ ")" ] criteria-item = [ "(" ] attributetype "$" match-type [ ")" ]
match-type = "EQ" / "SUBSTR" / "GE" / "LE" / "APPROX" match-type = "EQ" / "SUBSTR" / "GE" / "LE" / "APPROX"
This syntax should not be used for defining new attributes. This syntax should not be used for defining new attributes.
6.4. Octet String 6.4. Octet String
( 1.3.6.1.4.1.1466.115.121.1.40 DESC 'Octet String' ) ( 1.3.6.1.4.1.1466.115.121.1.40 DESC 'Octet String' )
Values in this syntax are encoded as octet strings. Values in this syntax are encoded as octet strings.
Example: Example:
skipping to change at page 12, line 14 skipping to change at page 14, line 4
6.5. Teletex Terminal Identifier 6.5. Teletex Terminal Identifier
( 1.3.6.1.4.1.1466.115.121.1.51 DESC 'Teletex Terminal Identifier' ) ( 1.3.6.1.4.1.1466.115.121.1.51 DESC 'Teletex Terminal Identifier' )
Values in this syntax are encoded according to the following BNF: Values in this syntax are encoded according to the following BNF:
teletex-id = ttx-term 0*("$" ttx-param) teletex-id = ttx-term 0*("$" ttx-param)
ttx-term = printablestring ttx-term = printablestring
ttx-param = ttx-key ":" ttx-value ttx-param = ttx-key ":" ttx-value
ttx-key = "graphic" / "control" / "misc" / "page" / "private" ttx-key = "graphic" / "control" / "misc" / "page" / "private"
ttx-value = octetstring ttx-value = octetstring
In the above, the first printablestring is the encoding of the In the above, the first printablestring is the encoding of the first
first portion of the teletex terminal identifier to be encoded, and portion of the teletex terminal identifier to be encoded, and the
the subsequent 0 or more octetstrings are subsequent portions subsequent 0 or more octetstrings are subsequent portions of the
of the teletex terminal identifier. teletex terminal identifier.
6.6. Telex Number 6.6. Telex Number
( 1.3.6.1.4.1.1466.115.121.1.52 DESC 'Telex Number' ) ( 1.3.6.1.4.1.1466.115.121.1.52 DESC 'Telex Number' )
Values in this syntax are encoded according to the following BNF: Values in this syntax are encoded according to the following BNF:
telex-number = actual-number "$" country "$" answerback telex-number = actual-number "$" country "$" answerback
actual-number = printablestring actual-number = printablestring
country = printablestring country = printablestring
answerback = printablestring answerback = printablestring
In the above, actual-number is the syntactic representation of the In the above, actual-number is the syntactic representation of the
number portion of the TELEX number being encoded, country is the number portion of the TELEX number being encoded, country is the
TELEX country code, and answerback is the answerback code of a TELEX country code, and answerback is the answerback code of a TELEX
TELEX terminal. terminal.
6.7. Supported Algorithm 6.7. Supported Algorithm
( 1.3.6.1.4.1.1466.115.121.1.49 DESC 'Supported Algorithm' ) ( 1.3.6.1.4.1.1466.115.121.1.49 DESC 'Supported Algorithm' )
No printable representation of values of the supportedAlgorithms No printable representation of values of the supportedAlgorithms
attribute is defined in this document. Clients which wish to store attribute is defined in this document. Clients which wish to store
and retrieve this attribute MUST use "supportedAlgorithms;binary", in and retrieve this attribute MUST use "supportedAlgorithms;binary", in
which the value is transferred as a binary encoding. which the value is transferred as a binary encoding.
7. Object Classes 7. Object Classes
LDAP servers MUST recognize the object classes "top" and "subschema". LDAP servers MUST recognize the object classes "top" and "subschema".
LDAP servers SHOULD recognize all the other object classes listed here LDAP servers SHOULD recognize all the other object classes listed
as values of the objectClass attribute. here as values of the objectClass attribute.
7.1. top 7.1. top
( 2.5.6.0 NAME 'top' ABSTRACT MUST objectClass ) ( 2.5.6.0 NAME 'top' ABSTRACT MUST objectClass )
7.2. alias 7.2. alias
( 2.5.6.1 NAME 'alias' SUP top STRUCTURAL MUST aliasedObjectName ) ( 2.5.6.1 NAME 'alias' SUP top STRUCTURAL MUST aliasedObjectName )
7.3. country 7.3. country
( 2.5.6.2 NAME 'country' SUP top STRUCTURAL MUST c ( 2.5.6.2 NAME 'country' SUP top STRUCTURAL MUST c
MAY ( searchGuide $ description ) ) MAY ( searchGuide $ description ) )
7.4. locality 7.4. locality
( 2.5.6.3 NAME 'locality' SUP top STRUCTURAL ( 2.5.6.3 NAME 'locality' SUP top STRUCTURAL
MAY ( street $ seeAlso $ searchGuide $ st $ l $ description ) ) MAY ( street $ seeAlso $ searchGuide $ st $ l $ description ) )
7.5. organization 7.5. organization
( 2.5.6.4 NAME 'organization' SUP top STRUCTURAL MUST o ( 2.5.6.4 NAME 'organization' SUP top STRUCTURAL MUST o
MAY ( userPassword $ searchGuide $ seeAlso $ businessCategory $ MAY ( userPassword $ searchGuide $ seeAlso $ businessCategory $
x121Address $ registeredAddress $ destinationIndicator $ x121Address $ registeredAddress $ destinationIndicator $
preferredDeliveryMethod $ telexNumber $ teletexTerminalIdentifier $ preferredDeliveryMethod $ telexNumber $ teletexTerminalIdentifier $
telephoneNumber $ internationaliSDNNumber $ telephoneNumber $ internationaliSDNNumber $
facsimileTelephoneNumber $ facsimileTelephoneNumber $
street $ postOfficeBox $ postalCode $ postalAddress $ street $ postOfficeBox $ postalCode $ postalAddress $
physicalDeliveryOfficeName $ st $ l $ description ) ) physicalDeliveryOfficeName $ st $ l $ description ) )
7.6. organizationalUnit 7.6. organizationalUnit
( 2.5.6.5 NAME 'organizationalUnit' SUP top STRUCTURAL MUST ou ( 2.5.6.5 NAME 'organizationalUnit' SUP top STRUCTURAL MUST ou
MAY ( userPassword $ searchGuide $ seeAlso $ businessCategory $ MAY ( userPassword $ searchGuide $ seeAlso $ businessCategory $
x121Address $ registeredAddress $ destinationIndicator $ x121Address $ registeredAddress $ destinationIndicator $
preferredDeliveryMethod $ telexNumber $ teletexTerminalIdentifier $ preferredDeliveryMethod $ telexNumber $ teletexTerminalIdentifier $
telephoneNumber $ internationaliSDNNumber $ telephoneNumber $ internationaliSDNNumber $
facsimileTelephoneNumber $ facsimileTelephoneNumber $
street $ postOfficeBox $ postalCode $ postalAddress $ street $ postOfficeBox $ postalCode $ postalAddress $
physicalDeliveryOfficeName $ st $ l $ description ) ) physicalDeliveryOfficeName $ st $ l $ description ) )
7.7. person 7.7. person
( 2.5.6.6 NAME 'person' SUP top STRUCTURAL MUST ( sn $ cn ) ( 2.5.6.6 NAME 'person' SUP top STRUCTURAL MUST ( sn $ cn )
MAY ( userPassword $ telephoneNumber $ seeAlso $ description ) ) MAY ( userPassword $ telephoneNumber $ seeAlso $ description ) )
7.8. organizationalPerson 7.8. organizationalPerson
( 2.5.6.7 NAME 'organizationalPerson' SUP person STRUCTURAL ( 2.5.6.7 NAME 'organizationalPerson' SUP person STRUCTURAL
MAY ( title $ x121Address $ registeredAddress $ MAY ( title $ x121Address $ registeredAddress $
destinationIndicator $ destinationIndicator $
preferredDeliveryMethod $ telexNumber $ teletexTerminalIdentifier $ preferredDeliveryMethod $ telexNumber $ teletexTerminalIdentifier $
telephoneNumber $ internationaliSDNNumber $ telephoneNumber $ internationaliSDNNumber $
facsimileTelephoneNumber $ facsimileTelephoneNumber $
street $ postOfficeBox $ postalCode $ postalAddress $ street $ postOfficeBox $ postalCode $ postalAddress $
physicalDeliveryOfficeName $ ou $ st $ l ) ) physicalDeliveryOfficeName $ ou $ st $ l ) )
7.9. organizationalRole 7.9. organizationalRole
( 2.5.6.8 NAME 'organizationalRole' SUP top STRUCTURAL MUST cn ( 2.5.6.8 NAME 'organizationalRole' SUP top STRUCTURAL MUST cn
MAY ( x121Address $ registeredAddress $ destinationIndicator $ MAY ( x121Address $ registeredAddress $ destinationIndicator $
preferredDeliveryMethod $ telexNumber $ teletexTerminalIdentifier $ preferredDeliveryMethod $ telexNumber $ teletexTerminalIdentifier $
telephoneNumber $ internationaliSDNNumber $ telephoneNumber $ internationaliSDNNumber $
facsimileTelephoneNumber $ facsimileTelephoneNumber $
seeAlso $ roleOccupant $ preferredDeliveryMethod $ street $ seeAlso $ roleOccupant $ preferredDeliveryMethod $ street $
postOfficeBox $ postalCode $ postalAddress $ postOfficeBox $ postalCode $ postalAddress $
physicalDeliveryOfficeName $ ou $ st $ l $ description ) ) physicalDeliveryOfficeName $ ou $ st $ l $ description ) )
7.10. groupOfNames 7.10. groupOfNames
( 2.5.6.9 NAME 'groupOfNames' SUP top STRUCTURAL MUST ( member $ cn ) ( 2.5.6.9 NAME 'groupOfNames' SUP top STRUCTURAL MUST ( member $ cn )
MAY ( businessCategory $ seeAlso $ owner $ ou $ o $ description ) ) MAY ( businessCategory $ seeAlso $ owner $ ou $ o $ description ) )
7.11. residentialPerson 7.11. residentialPerson
( 2.5.6.10 NAME 'residentialPerson' SUP person STRUCTURAL MUST l ( 2.5.6.10 NAME 'residentialPerson' SUP person STRUCTURAL MUST l
MAY ( businessCategory $ x121Address $ registeredAddress $ MAY ( businessCategory $ x121Address $ registeredAddress $
destinationIndicator $ preferredDeliveryMethod $ telexNumber $ destinationIndicator $ preferredDeliveryMethod $ telexNumber $
teletexTerminalIdentifier $ telephoneNumber $ teletexTerminalIdentifier $ telephoneNumber $
internationaliSDNNumber $ internationaliSDNNumber $
facsimileTelephoneNumber $ preferredDeliveryMethod $ street $ facsimileTelephoneNumber $ preferredDeliveryMethod $ street $
postOfficeBox $ postalCode $ postalAddress $ postOfficeBox $ postalCode $ postalAddress $
physicalDeliveryOfficeName $ st $ l ) ) physicalDeliveryOfficeName $ st $ l ) )
7.12. applicationProcess 7.12. applicationProcess
( 2.5.6.11 NAME 'applicationProcess' SUP top STRUCTURAL MUST cn ( 2.5.6.11 NAME 'applicationProcess' SUP top STRUCTURAL MUST cn
MAY ( seeAlso $ ou $ l $ description ) ) MAY ( seeAlso $ ou $ l $ description ) )
7.13. applicationEntity 7.13. applicationEntity
( 2.5.6.12 NAME 'applicationEntity' SUP top STRUCTURAL ( 2.5.6.12 NAME 'applicationEntity' SUP top STRUCTURAL
MUST ( presentationAddress $ cn ) MUST ( presentationAddress $ cn )
MAY ( supportedApplicationContext $ seeAlso $ ou $ o $ l $ MAY ( supportedApplicationContext $ seeAlso $ ou $ o $ l $
description ) ) description ) )
7.14. dSA 7.14. dSA
( 2.5.6.13 NAME 'dSA' SUP applicationEntity STRUCTURAL ( 2.5.6.13 NAME 'dSA' SUP applicationEntity STRUCTURAL
MAY knowledgeInformation ) MAY knowledgeInformation )
7.15. device 7.15. device
( 2.5.6.14 NAME 'device' SUP top STRUCTURAL MUST cn ( 2.5.6.14 NAME 'device' SUP top STRUCTURAL MUST cn
MAY ( serialNumber $ seeAlso $ owner $ ou $ o $ l $ description ) ) MAY ( serialNumber $ seeAlso $ owner $ ou $ o $ l $ description ) )
7.16. strongAuthenticationUser 7.16. strongAuthenticationUser
( 2.5.6.15 NAME 'strongAuthenticationUser' SUP top AUXILIARY ( 2.5.6.15 NAME 'strongAuthenticationUser' SUP top AUXILIARY
MUST userCertificate ) MUST userCertificate )
7.17. certificationAuthority 7.17. certificationAuthority
( 2.5.6.16 NAME 'certificationAuthority' SUP top AUXILIARY ( 2.5.6.16 NAME 'certificationAuthority' SUP top AUXILIARY
MUST ( authorityRevocationList $ certificateRevocationList $ MUST ( authorityRevocationList $ certificateRevocationList $
cACertificate ) MAY crossCertificatePair ) cACertificate ) MAY crossCertificatePair )
7.18. groupOfUniqueNames 7.18. groupOfUniqueNames
( 2.5.6.17 NAME 'groupOfUniqueNames' SUP top STRUCTURAL ( 2.5.6.17 NAME 'groupOfUniqueNames' SUP top STRUCTURAL
MUST ( uniqueMember $ cn ) MUST ( uniqueMember $ cn )
MAY ( businessCategory $ seeAlso $ owner $ ou $ o $ description ) ) MAY ( businessCategory $ seeAlso $ owner $ ou $ o $ description ) )
7.19. userSecurityInformation 7.19. userSecurityInformation
( 2.5.6.18 NAME 'userSecurityInformation' SUP top AUXILIARY ( 2.5.6.18 NAME 'userSecurityInformation' SUP top AUXILIARY
MAY ( supportedAlgorithms ) ) MAY ( supportedAlgorithms ) )
7.20. certificationAuthority-V2 7.20. certificationAuthority-V2
( 2.5.6.16.2 NAME 'certificationAuthority-V2' SUP ( 2.5.6.16.2 NAME 'certificationAuthority-V2' SUP
certificationAuthority certificationAuthority
AUXILIARY MAY ( deltaRevocationList ) ) AUXILIARY MAY ( deltaRevocationList ) )
7.21. cRLDistributionPoint 7.21. cRLDistributionPoint
( 2.5.6.19 NAME 'cRLDistributionPoint' SUP top STRUCTURAL ( 2.5.6.19 NAME 'cRLDistributionPoint' SUP top STRUCTURAL
MUST ( cn ) MAY ( certificateRevocationList $ MUST ( cn ) MAY ( certificateRevocationList $
authorityRevocationList $ authorityRevocationList $
deltaRevocationList ) ) deltaRevocationList ) )
7.22. dmd 7.22. dmd
( 2.5.6.20 NAME 'dmd' SUP top STRUCTURAL MUST ( dmdName ) ( 2.5.6.20 NAME 'dmd' SUP top STRUCTURAL MUST ( dmdName )
MAY ( userPassword $ searchGuide $ seeAlso $ businessCategory $ MAY ( userPassword $ searchGuide $ seeAlso $ businessCategory $
x121Address $ registeredAddress $ destinationIndicator $ x121Address $ registeredAddress $ destinationIndicator $
preferredDeliveryMethod $ telexNumber $ teletexTerminalIdentifier $ preferredDeliveryMethod $ telexNumber $ teletexTerminalIdentifier $
telephoneNumber $ internationaliSDNNumber $ telephoneNumber $ internationaliSDNNumber $
facsimileTelephoneNumber $ facsimileTelephoneNumber $
street $ postOfficeBox $ postalCode $ postalAddress $ street $ postOfficeBox $ postalCode $ postalAddress $
physicalDeliveryOfficeName $ st $ l $ description ) ) physicalDeliveryOfficeName $ st $ l $ description ) )
8. Matching Rules 8. Matching Rules
Servers MAY implement additional matching rules. Servers MAY implement additional matching rules.
8.1. octetStringMatch 8.1. octetStringMatch
Servers which implement the extensibleMatch filter SHOULD allow Servers which implement the extensibleMatch filter SHOULD allow the
the matching rule listed in this section to be used in the matching rule listed in this section to be used in the
extensibleMatch. In general these servers SHOULD allow matching extensibleMatch. In general these servers SHOULD allow matching
rules to be used with all attribute types known to the server, when rules to be used with all attribute types known to the server, when
the assertion syntax of the matching rule is the same as the value the assertion syntax of the matching rule is the same as the value
syntax of the attribute. syntax of the attribute.
( 2.5.13.17 NAME 'octetStringMatch' ( 2.5.13.17 NAME 'octetStringMatch'
SYNTAX 1.3.6.1.4.1.1466.115.121.1.40 ) SYNTAX 1.3.6.1.4.1.1466.115.121.1.40 )
9. Security Considerations 9. Security Considerations
Attributes of directory entries are used to provide descriptive Attributes of directory entries are used to provide descriptive
information about the real-world objects they represent, which can information about the real-world objects they represent, which can be
be people, organizations or devices. Most countries have privacy people, organizations or devices. Most countries have privacy laws
laws regarding the publication of information about people. regarding the publication of information about people.
Transfer of cleartext passwords are strongly discouraged where the Transfer of cleartext passwords are strongly discouraged where the
underlying transport service cannot guarantee confidentiality and may underlying transport service cannot guarantee confidentiality and may
result in disclosure of the password to unauthorized parties. result in disclosure of the password to unauthorized parties.
10. Acknowledgements 10. Acknowledgements
The definitions on which this document have been developed by The definitions on which this document have been developed by
committees for telecommunications and international standards. committees for telecommunications and international standards. No
No new attribute definitions have been added. The syntax definitions new attribute definitions have been added. The syntax definitions
are based on the ISODE "QUIPU" implementation of X.500. are based on the ISODE "QUIPU" implementation of X.500.
11. Bibliography 11. Bibliography
[1] M. Wahl, A. Coulbeck, T. Howes, S. Kille, [1] Wahl, M., Coulbeck, A., Howes, T., and S. Kille,
"Lightweight X.500 Directory Access Protocol Attribute Syntax "Lightweight X.500 Directory Access Protocol (v3): Attribute
Definitions", INTERNET-DRAFT Syntax Definitions", RFC 2252, December 1997.
<draft-ietf-asid-ldapv3-attributes-08.txt>, October 1997.
[2] The Directory: Models. ITU-T Recommendation X.501, 1996. [2] The Directory: Models. ITU-T Recommendation X.501, 1996.
[3] The Directory: Authentication Framework. ITU-T Recommendation [3] The Directory: Authentication Framework. ITU-T Recommendation
X.509, 1996. X.509, 1996.
[4] The Directory: Selected Attribute Types. ITU-T Recommendation [4] The Directory: Selected Attribute Types. ITU-T Recommendation
X.520, 1996. X.520, 1996.
[5] The Directory: Selected Object Classes. ITU-T Recommendation [5] The Directory: Selected Object Classes. ITU-T Recommendation
X.521, 1996. X.521, 1996.
[6] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", RFC 2119, March 1997.
12. Author's Address 12. Author's Address
Mark Wahl Mark Wahl
Critical Angle Inc. Critical Angle Inc.
4815 West Braker Lane #502-385 4815 West Braker Lane #502-385
Austin, TX 78759 Austin, TX 78759
USA USA
Phone: +1 512 372 3160 Phone: +1 512 372 3160
EMail: M.Wahl@critical-angle.com EMail: M.Wahl@critical-angle.com
13. Full Copyright Statement
Copyright (C) The Internet Society (1997). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 69 change blocks. 
196 lines changed or deleted 231 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/