draft-ietf-ldapbis-protocol-05.txt   draft-ietf-ldapbis-protocol-06.txt 
Internet-Draft Editor: J. Sermersheim Internet-Draft Editor: J. Sermersheim
Intended Category: Standard Track Novell, Inc Intended Category: Standard Track Novell, Inc
Document: draft-ietf-ldapbis-protocol-05.txt October 2001 Document: draft-ietf-ldapbis-protocol-06.txt January 2002
Obsoletes: RFC 2251 Obsoletes: RFC 2251
Lightweight Directory Access Protocol (v3) Lightweight Directory Access Protocol (v3)
1. Status of this Memo 1. Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of [RFC2026]. all provisions of Section 10 of [RFC2026].
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at line 44 skipping to change at line 44
1. Status of this Memo..............................................1 1. Status of this Memo..............................................1
2. Abstract.........................................................2 2. Abstract.........................................................2
3. Models...........................................................3 3. Models...........................................................3
3.1. Protocol Model.................................................3 3.1. Protocol Model.................................................3
3.2. Data Model.....................................................4 3.2. Data Model.....................................................4
3.2.1. Attributes of Entries........................................4 3.2.1. Attributes of Entries........................................4
3.2.2. Subschema Entries and Subentries.............................6 3.2.2. Subschema Entries and Subentries.............................6
3.3. Relationship to X.500..........................................7 3.3. Relationship to X.500..........................................7
3.4. Server-specific Data Requirements..............................7 3.4. Server-specific Data Requirements..............................7
4. Elements of Protocol.............................................7 4. Elements of Protocol.............................................8
4.1. Common Elements................................................8 4.1. Common Elements................................................8
4.1.1. Message Envelope.............................................8 4.1.1. Message Envelope.............................................8
4.1.1.1. Message ID.................................................9 4.1.1.1. Message ID.................................................9
4.1.2. String Types.................................................9 4.1.2. String Types.................................................9
4.1.3. Distinguished Name and Relative Distinguished Name..........10 4.1.3. Distinguished Name and Relative Distinguished Name..........10
4.1.4. Attribute Type..............................................10 4.1.4. Attribute Type..............................................10
4.1.5. Attribute Description.......................................11 4.1.5. Attribute Description.......................................11
4.1.5.1. Binary Option.............................................12 4.1.5.1. Binary Option.............................................13
4.1.6. Attribute Value.............................................13 4.1.6. Attribute Value.............................................13
Sermersheim Internet-Draft - Expires July 2002 Page 1
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
4.1.7. Attribute Value Assertion...................................13 4.1.7. Attribute Value Assertion...................................14
4.1.8. Attribute...................................................14 4.1.8. Attribute...................................................14
4.1.9. Matching Rule Identifier....................................14 4.1.9. Matching Rule Identifier....................................15
4.1.10. Result Message.............................................14 4.1.10. Result Message.............................................15
4.1.11. Referral...................................................16 4.1.11. Referral...................................................17
4.1.12. Controls...................................................17 4.1.12. Controls...................................................18
4.2. Bind Operation................................................18 4.2. Bind Operation................................................19
4.2.1. Sequencing of the Bind Request..............................19 4.2.1. Sequencing of the Bind Request..............................20
4.2.2. Authentication and Other Security Services..................20 4.2.2. Authentication and Other Security Services..................21
4.2.3. Bind Response...............................................20 4.2.3. Bind Response...............................................21
4.3. Unbind Operation..............................................21 4.3. Unbind Operation..............................................22
4.4. Unsolicited Notification......................................22 4.4. Unsolicited Notification......................................22
4.4.1. Notice of Disconnection.....................................22 4.4.1. Notice of Disconnection.....................................23
4.5. Search Operation..............................................23 4.5. Search Operation..............................................23
4.5.1. Search Request..............................................23 4.5.1. Search Request..............................................24
4.5.2. Search Result...............................................27 4.5.2. Search Result...............................................27
4.5.3. Continuation References in the Search Result................28 4.5.3. Continuation References in the Search Result................28
4.6. Modify Operation..............................................29 4.6. Modify Operation..............................................30
4.7. Add Operation.................................................31 4.7. Add Operation.................................................31
4.8. Delete Operation..............................................32 4.8. Delete Operation..............................................32
4.9. Modify DN Operation...........................................32 4.9. Modify DN Operation...........................................33
4.10. Compare Operation............................................33 4.10. Compare Operation............................................34
4.11. Abandon Operation............................................34 4.11. Abandon Operation............................................35
4.12. Extended Operation...........................................35 4.12. Extended Operation...........................................35
5. Protocol Element Encodings and Transfer.........................35 5. Protocol Element Encodings and Transfer.........................36
5.1. Protocol Encoding.............................................35 5.1. Protocol Encoding.............................................36
5.2. Transfer Protocols............................................36 5.2. Transfer Protocols............................................36
5.2.1. Transmission Control Protocol (TCP).........................36 5.2.1. Transmission Control Protocol (TCP).........................36
6. Implementation Guidelines.......................................36 6. Implementation Guidelines.......................................37
6.1. Server Implementations........................................36 6.1. Server Implementations........................................37
6.2. Client Implementations........................................36 6.2. Client Implementations........................................37
7. Security Considerations.........................................36 7. Security Considerations.........................................37
8. Acknowledgements................................................37 8. Acknowledgements................................................38
9. Bibliography....................................................37 9. Bibliography....................................................38
10. Editor's Address...............................................38 10. Editor's Address...............................................39
Appendix A - Complete ASN.1 Definition.............................39 Appendix A - Complete ASN.1 Definition.............................40
Appendix B - Change History........................................44 Appendix B - Change History........................................45
B.1 Changes made to RFC 2251:......................................44 B.1 Changes made to RFC 2251:......................................45
B.2 Changes made to draft-ietf-ldapbis-protocol-00.txt:............44 B.2 Changes made to draft-ietf-ldapbis-protocol-00.txt:............45
B.3 Changes made to draft-ietf-ldapbis-protocol-01.txt:............45 B.3 Changes made to draft-ietf-ldapbis-protocol-01.txt:............46
B.4 Changes made to draft-ietf-ldapbis-protocol-02.txt:............45 B.4 Changes made to draft-ietf-ldapbis-protocol-02.txt:............46
B.5 Changes made to draft-ietf-ldapbis-protocol-03.txt:............47 B.5 Changes made to draft-ietf-ldapbis-protocol-03.txt:............48
Appendix C - Outstanding Work Items................................49 B.6 Changes made to draft-ietf-ldapbis-protocol-04.txt:............50
B.7 Changes made to draft-ietf-ldapbis-protocol-05.txt:............50
Appendix C - Outstanding Work Items................................50
2. Abstract 2. Abstract
The protocol described in this document is designed to provide access The protocol described in this document is designed to provide access
to directories supporting the [X.500] models, while not incurring the to directories supporting the [X.500] models, while not incurring the
resource requirements of the X.500 Directory Access Protocol (DAP). resource requirements of the X.500 Directory Access Protocol (DAP).
This protocol is specifically targeted at management applications and This protocol is specifically targeted at management applications and
browser applications that provide read/write interactive access to browser applications that provide read/write interactive access to
directories. When used with a directory supporting the X.500
protocols, it is intended to be a complement to the X.500 DAP.
Sermersheim Internet-Draft - Expires July 2002 Page 2
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
directories. When used with a directory supporting the X.500
protocols, it is intended to be a complement to the X.500 DAP.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", and "MAY" in this document are "SHOULD", "SHOULD NOT", "RECOMMENDED", and "MAY" in this document are
to be interpreted as described in [RFC2119]. to be interpreted as described in [RFC2119].
Key aspects of this version of LDAP are: Key aspects of this version of LDAP are:
- All protocol elements of LDAPv2 [RFC1777] are supported. The - All protocol elements of LDAPv2 [RFC1777] are supported. The
protocol is carried directly over TCP or other transport, protocol is carried directly over TCP or other transport,
bypassing much of the session/presentation overhead of X.500 DAP. bypassing much of the session/presentation overhead of X.500 DAP.
skipping to change at line 164 skipping to change at line 169
errors to the requesting client. errors to the requesting client.
In keeping with the goal of easing the costs associated with use of In keeping with the goal of easing the costs associated with use of
the directory, it is an objective of this protocol to minimize the the directory, it is an objective of this protocol to minimize the
complexity of clients so as to facilitate widespread deployment of complexity of clients so as to facilitate widespread deployment of
applications capable of using the directory. applications capable of using the directory.
Note that although servers are required to return responses whenever Note that although servers are required to return responses whenever
such responses are defined in the protocol, there is no requirement such responses are defined in the protocol, there is no requirement
for synchronous behavior on the part of either clients or servers. for synchronous behavior on the part of either clients or servers.
Sermersheim Internet-Draft - Expires July 2002 Page 3
Lightweight Directory Access Protocol Version 3
Requests and responses for multiple operations may be exchanged Requests and responses for multiple operations may be exchanged
between a client and server in any order, provided the client between a client and server in any order, provided the client
eventually receives a response for every request that requires one. eventually receives a response for every request that requires one.
Lightweight Directory Access Protocol Version 3
In LDAP versions 1 and 2, no provision was made for protocol servers In LDAP versions 1 and 2, no provision was made for protocol servers
returning referrals to clients. However, for improved performance and returning referrals to clients. However, for improved performance and
distribution, this version of the protocol permits servers to return distribution, this version of the protocol permits servers to return
to clients, referrals to other servers. This allows servers to to clients, referrals to other servers. This allows servers to
offload the work of contacting other servers to progress operations. offload the work of contacting other servers to progress operations.
Note that the core protocol operations defined in this document can Note that the core protocol operations defined in this document can
be mapped to a strict subset of the X.500(1997) directory abstract be mapped to a strict subset of the X.500(1997) directory abstract
service, so it can be cleanly provided by the DAP. However there is service, so it can be cleanly provided by the DAP. However there is
not a one-to-one mapping between LDAP protocol operations and DAP not a one-to-one mapping between LDAP protocol operations and DAP
skipping to change at line 219 skipping to change at line 226
The largest collection of entries, starting at an entry that is The largest collection of entries, starting at an entry that is
mastered by a particular server, and including all its subordinates mastered by a particular server, and including all its subordinates
and their subordinates, down to the entries which are mastered by and their subordinates, down to the entries which are mastered by
different servers, is termed a naming context. The root of the DIT is different servers, is termed a naming context. The root of the DIT is
a DSA-specific Entry (DSE) and not part of any naming context: each a DSA-specific Entry (DSE) and not part of any naming context: each
server has different attribute values in the root DSE. (DSA is an server has different attribute values in the root DSE. (DSA is an
X.500 term for the directory server). X.500 term for the directory server).
3.2.1. Attributes of Entries 3.2.1. Attributes of Entries
Sermersheim Internet-Draft - Expires July 2002 Page 4
Lightweight Directory Access Protocol Version 3
Entries consist of a set of attributes. An attribute is a description Entries consist of a set of attributes. An attribute is a description
(a type and zero or more options) with one or more associated values. (a type and zero or more options) with one or more associated values.
The attribute type governs whether the attribute can have multiple The attribute type governs whether the attribute can have multiple
values, the syntax and matching rules used to construct and compare values, the syntax and matching rules used to construct and compare
Lightweight Directory Access Protocol Version 3
values of that attribute, and other functions. Options indicate modes values of that attribute, and other functions. Options indicate modes
of transfer and other functions. of transfer and other functions.
An example of an attribute is "mail". There may be one or more values An example of an attribute is "mail". There may be one or more values
of this attribute, they must be IA5 (ASCII) strings, and they are of this attribute, they must be IA5 (ASCII) strings, and they are
case insensitive (e.g. "foo@bar.com" will match "FOO@BAR.COM"). case insensitive (e.g. "foo@bar.com" will match "FOO@BAR.COM").
Schema is the collection of attribute type definitions, object class Schema is the collection of attribute type definitions, object class
definitions and other information which a server uses to determine definitions and other information which a server uses to determine
how to match a filter or attribute value assertion (in a compare how to match a filter or attribute value assertion (in a compare
skipping to change at line 253 skipping to change at line 260
the system and user schema determine the permitted attributes of an the system and user schema determine the permitted attributes of an
entry. Values of this attribute may be modified by clients, but the entry. Values of this attribute may be modified by clients, but the
objectClass attribute cannot be removed. Servers may restrict the objectClass attribute cannot be removed. Servers may restrict the
modifications of this attribute to prevent the basic structural class modifications of this attribute to prevent the basic structural class
of the entry from being changed (e.g. one cannot change a person into of the entry from being changed (e.g. one cannot change a person into
a country). When creating an entry or adding an objectClass value to a country). When creating an entry or adding an objectClass value to
an entry, all superclasses of the named classes are implicitly added an entry, all superclasses of the named classes are implicitly added
as well if not already present, and the client must supply values for as well if not already present, and the client must supply values for
any mandatory attributes of new superclasses. any mandatory attributes of new superclasses.
Some attributes, termed operational attributes, are used by servers Some attributes, termed operational attributes (as defined in Section
for administering the directory system itself. They are not returned 12.4.1 of [X.501]), are used by servers for administering the
in search results unless explicitly requested by name. Attributes directory system itself. They are not returned in search results
which are not operational, such as "mail", will have their schema and unless explicitly requested by name. Attributes which are not
syntax constraints enforced by servers, but servers will generally operational, such as "mail", will have their schema and syntax
not make use of their values. constraints enforced by servers, but servers will generally not make
use of their values.
Servers MUST NOT permit clients to add attributes to an entry unless Servers MUST NOT permit clients to add attributes to an entry unless
those attributes are permitted by the object class definitions, the those attributes are permitted by the object class definitions, the
schema controlling that entry (specified in the subschema see schema controlling that entry (specified in the subschema see
below), or are operational attributes known to that server and used below), or are operational attributes known to that server and used
for administrative purposes. Note that there is a particular for administrative purposes. Note that there is a particular
objectClass 'extensibleObject' defined in [RFC2252] which permits all objectClass 'extensibleObject' defined in [RFC2252] which permits all
user attributes to be present in an entry. user attributes to be present in an entry.
Entries MAY contain, among others, the following operational Entries MAY contain, among others, the following operational
attributes, defined in [RFC2252]. These attributes are maintained attributes, defined in [RFC2252]. These attributes are maintained
automatically by the server and are not modifiable by clients: automatically by the server and are not modifiable by clients:
- creatorsName: the Distinguished Name of the user who added this - creatorsName: the Distinguished Name of the user who added this
entry to the directory. entry to the directory.
Sermersheim Internet-Draft - Expires July 2002 Page 5
Lightweight Directory Access Protocol Version 3
- createTimestamp: the time this entry was added to the directory. - createTimestamp: the time this entry was added to the directory.
- modifiersName: the Distinguished Name of the user who last - modifiersName: the Distinguished Name of the user who last
modified this entry. modified this entry.
Lightweight Directory Access Protocol Version 3
- modifyTimestamp: the time this entry was last modified. - modifyTimestamp: the time this entry was last modified.
- subschemaSubentry: the Distinguished Name of the subschema entry - subschemaSubentry: the Distinguished Name of the subschema entry
(or subentry) which controls the schema for this entry. (or subentry) which controls the schema for this entry.
3.2.2. Subschema Entries and Subentries 3.2.2. Subschema Entries and Subentries
Subschema entries are used for administering information about the Subschema entries are used for administering information about the
directory schema, in particular the object classes and attribute directory schema, in particular the object classes and attribute
types supported by directory servers. A single subschema entry types supported by directory servers. A single subschema entry
skipping to change at line 330 skipping to change at line 339
These are defined in [RFC2252]. Other attributes MAY be present in These are defined in [RFC2252]. Other attributes MAY be present in
subschema entries, to reflect additional supported capabilities. subschema entries, to reflect additional supported capabilities.
These include matchingRules, matchingRuleUse, dITStructureRules, These include matchingRules, matchingRuleUse, dITStructureRules,
dITContentRules, nameForms and ldapSyntaxes. dITContentRules, nameForms and ldapSyntaxes.
Servers SHOULD provide the attributes createTimestamp and Servers SHOULD provide the attributes createTimestamp and
modifyTimestamp in subschema entries, in order to allow clients to modifyTimestamp in subschema entries, in order to allow clients to
maintain their caches of schema information. maintain their caches of schema information.
Sermersheim Internet-Draft - Expires July 2002 Page 6
Lightweight Directory Access Protocol Version 3
Clients MUST only retrieve attributes from a subschema entry by Clients MUST only retrieve attributes from a subschema entry by
requesting a base object search of the entry, where the search filter requesting a base object search of the entry, where the search filter
is "(objectClass=subschema)". This will allow LDAPv3 servers which is "(objectClass=subschema)". This will allow LDAPv3 servers which
gateway to X.500(93) to detect that subentry information is being gateway to X.500(93) to detect that subentry information is being
requested. requested.
Lightweight Directory Access Protocol Version 3
3.3. Relationship to X.500 3.3. Relationship to X.500
This document defines LDAP in terms of X.500 as an X.500 access This document defines LDAP in terms of X.500 as an X.500 access
mechanism. An LDAP server MUST act in accordance with the X.500(1993) mechanism. An LDAP server MUST act in accordance with the X.500(1993)
series of ITU recommendations when providing the service. However, it series of ITU recommendations when providing the service. However, it
is not required that an LDAP server make use of any X.500 protocols is not required that an LDAP server make use of any X.500 protocols
in providing this service, e.g. LDAP can be mapped onto any other in providing this service, e.g. LDAP can be mapped onto any other
directory system so long as the X.500 data and service model as used directory system so long as the X.500 data and service model as used
in LDAP is not violated in the LDAP interface. in LDAP is not violated in the LDAP interface.
skipping to change at line 387 skipping to change at line 397
- supportedSASLMechanisms: list of supported SASL security features. - supportedSASLMechanisms: list of supported SASL security features.
- supportedLDAPVersion: LDAP versions implemented by the server. - supportedLDAPVersion: LDAP versions implemented by the server.
If the server does not master entries and does not know the locations If the server does not master entries and does not know the locations
of schema information, the subschemaSubentry attribute is not present of schema information, the subschemaSubentry attribute is not present
in the root DSE. If the server masters directory entries under one or in the root DSE. If the server masters directory entries under one or
more schema rules, the schema for each entry is found by reading the more schema rules, the schema for each entry is found by reading the
subschemaSubentry attribute for that entry. subschemaSubentry attribute for that entry.
Sermersheim Internet-Draft - Expires July 2002 Page 7
Lightweight Directory Access Protocol Version 3
4. Elements of Protocol 4. Elements of Protocol
The LDAP protocol is described using Abstract Syntax Notation 1 The LDAP protocol is described using Abstract Syntax Notation 1
(ASN.1) [X.680], and is transferred using a subset of ASN.1 Basic (ASN.1) [X.680], and is transferred using a subset of ASN.1 Basic
Encoding Rules [X.690]. In order to support future extensions to this Encoding Rules [X.690]. In order to support future extensions to this
Lightweight Directory Access Protocol Version 3
protocol, clients and servers MUST ignore elements of SEQUENCE protocol, clients and servers MUST ignore elements of SEQUENCE
encodings whose tags they do not recognize. Section 5.1 specifies how encodings whose tags they do not recognize. Section 5.1 specifies how
the protocol is encoded and transferred. the protocol is encoded and transferred.
Note that unlike X.500, each change to the LDAP protocol other than Note that unlike X.500, each change to the LDAP protocol other than
through the extension mechanisms will have a different version through the extension mechanisms will have a different version
number. A client will indicate the version it supports as part of the number. A client will indicate the version it supports as part of the
bind request, described in section 4.2. If a client has not sent a bind request, described in section 4.2. If a client has not sent a
bind, the server MUST assume that version 3 or later is supported in bind, the server MUST assume that version 3 or later is supported in
the client (since version 2 required that the client bind first). the client (since version 2 required that the client bind first).
skipping to change at line 443 skipping to change at line 453
searchResRef SearchResultReference, searchResRef SearchResultReference,
modifyRequest ModifyRequest, modifyRequest ModifyRequest,
modifyResponse ModifyResponse, modifyResponse ModifyResponse,
addRequest AddRequest, addRequest AddRequest,
addResponse AddResponse, addResponse AddResponse,
delRequest DelRequest, delRequest DelRequest,
delResponse DelResponse, delResponse DelResponse,
modDNRequest ModifyDNRequest, modDNRequest ModifyDNRequest,
modDNResponse ModifyDNResponse, modDNResponse ModifyDNResponse,
compareRequest CompareRequest, compareRequest CompareRequest,
Sermersheim Internet-Draft - Expires July 2002 Page 8
Lightweight Directory Access Protocol Version 3
compareResponse CompareResponse, compareResponse CompareResponse,
abandonRequest AbandonRequest, abandonRequest AbandonRequest,
extendedReq ExtendedRequest, extendedReq ExtendedRequest,
extendedResp ExtendedResponse }, extendedResp ExtendedResponse },
controls [0] Controls OPTIONAL } controls [0] Controls OPTIONAL }
Lightweight Directory Access Protocol Version 3
MessageID ::= INTEGER (0 .. maxInt) MessageID ::= INTEGER (0 .. maxInt)
maxInt INTEGER ::= 2147483647 -- (2^^31 - 1) -- maxInt INTEGER ::= 2147483647 -- (2^^31 - 1) --
The function of the LDAPMessage is to provide an envelope containing The function of the LDAPMessage is to provide an envelope containing
common fields required in all protocol exchanges. At this time the common fields required in all protocol exchanges. At this time the
only common fields are the message ID and the controls. only common fields are the message ID and the controls.
If the server receives a PDU from the client in which the LDAPMessage If the server receives a PDU from the client in which the LDAPMessage
SEQUENCE tag cannot be recognized, the messageID cannot be parsed, SEQUENCE tag cannot be recognized, the messageID cannot be parsed,
skipping to change at line 499 skipping to change at line 511
A client MUST NOT reuse the message id of an abandonRequest or of the A client MUST NOT reuse the message id of an abandonRequest or of the
abandoned operation until it has received a response from the server abandoned operation until it has received a response from the server
for another request invoked subsequent to the abandonRequest, as the for another request invoked subsequent to the abandonRequest, as the
abandonRequest itself does not have a response. abandonRequest itself does not have a response.
4.1.2. String Types 4.1.2. String Types
The LDAPString is a notational convenience to indicate that, although The LDAPString is a notational convenience to indicate that, although
strings of LDAPString type encode as OCTET STRING types, the strings of LDAPString type encode as OCTET STRING types, the
Sermersheim Internet-Draft - Expires July 2002 Page 9
Lightweight Directory Access Protocol Version 3
[ISO10646] character set (a superset of Unicode) is used, encoded [ISO10646] character set (a superset of Unicode) is used, encoded
following the UTF-8 algorithm [RFC2044]. Note that in the UTF-8 following the UTF-8 algorithm [RFC2044]. Note that in the UTF-8
algorithm characters which are the same as ASCII (0x0000 through algorithm characters which are the same as ASCII (0x0000 through
0x007F) are represented as that same ASCII character in a single 0x007F) are represented as that same ASCII character in a single
byte. The other byte values are used to form a variable-length byte. The other byte values are used to form a variable-length
encoding of an arbitrary character. encoding of an arbitrary character.
Lightweight Directory Access Protocol Version 3
LDAPString ::= OCTET STRING LDAPString ::= OCTET STRING
The LDAPOID is a notational convenience to indicate that the The LDAPOID is a notational convenience to indicate that the
permitted value of this string is a (UTF-8 encoded) dotted-decimal permitted value of this string is a (UTF-8 encoded) dotted-decimal
representation of an OBJECT IDENTIFIER. representation of an OBJECT IDENTIFIER.
LDAPOID ::= OCTET STRING LDAPOID ::= OCTET STRING
A value of LDAPOID is defined by the following ABNF [RFC2234]: A value of LDAPOID is defined by the following ABNF [RFC2234]:
skipping to change at line 555 skipping to change at line 569
LDAPDN ::= LDAPString LDAPDN ::= LDAPString
RelativeLDAPDN ::= LDAPString RelativeLDAPDN ::= LDAPString
Only Attribute Types can be present in a relative distinguished name Only Attribute Types can be present in a relative distinguished name
component--the options of Attribute Descriptions (next section) MUST component--the options of Attribute Descriptions (next section) MUST
NOT be used in specifying distinguished names. NOT be used in specifying distinguished names.
4.1.4. Attribute Type 4.1.4. Attribute Type
Sermersheim Internet-Draft - Expires July 2002 Page 10
Lightweight Directory Access Protocol Version 3
An AttributeType takes on as its value the textual string associated An AttributeType takes on as its value the textual string associated
with that AttributeType in its specification. with that AttributeType in its specification.
AttributeType ::= LDAPString AttributeType ::= LDAPString
Lightweight Directory Access Protocol Version 3
Each attribute type has a unique OBJECT IDENTIFIER which has been Each attribute type has a unique OBJECT IDENTIFIER which has been
assigned to it. This identifier may be written as defined by ldapOID assigned to it. This identifier may be written as defined by ldapOID
in section 4.1.2. in section 4.1.2.
A specification may also assign one or more textual names for an A specification may also assign one or more textual names for an
attribute type. These names MUST begin with a letter, and only attribute type. These names MUST begin with a letter, and only
contain ASCII letters, digit characters and hyphens. They are case contain ASCII letters, digit characters and hyphens. They are case
insensitive. These ASCII characters are identical to ISO 10646 insensitive. These ASCII characters are identical to ISO 10646
characters whose UTF-8 encoding is a single byte between 0x00 and characters whose UTF-8 encoding is a single byte between 0x00 and
0x7F. 0x7F.
skipping to change at line 598 skipping to change at line 613
and other information associated with attribute types. and other information associated with attribute types.
Some attribute type names which are used in this version of LDAP are Some attribute type names which are used in this version of LDAP are
described in [RFC2252]. Servers may implement additional attribute described in [RFC2252]. Servers may implement additional attribute
types. types.
4.1.5. Attribute Description 4.1.5. Attribute Description
An AttributeDescription is a superset of the definition of the An AttributeDescription is a superset of the definition of the
AttributeType. It has the same ASN.1 definition, but allows AttributeType. It has the same ASN.1 definition, but allows
additional options to be specified. They are also case insensitive. additional options to be specified. The entire AttributeDescription
is case insensitive.
AttributeDescription ::= LDAPString AttributeDescription ::= LDAPString
A value of AttributeDescription is based on the following ABNF: A value of AttributeDescription is based on the following ABNF:
attributeDescription = attributeType options attributeDescription = attributeType options
attributeType = AttributeType attributeType = AttributeType
; as described in Section 4.1.4 ; as described in Section 4.1.4
options = *( SEMICOLON options ) options = *( SEMICOLON options )
Sermersheim Internet-Draft - Expires July 2002 Page 11
Lightweight Directory Access Protocol Version 3
option = 1*opt-char option = 1*opt-char
opt-char = ALPHA / DIGIT / HYPHEN opt-char = ALPHA / DIGIT / HYPHEN
SEMICOLON = %x3B ; ";" SEMICOLON = %x3B ; ";"
Lightweight Directory Access Protocol Version 3
ALPHA = %x41-5A / %x61-7A ; A-Z / a-z ALPHA = %x41-5A / %x61-7A ; A-Z / a-z
HYPHEN = %x2D ; "-" HYPHEN = %x2D ; "-"
Examples of valid AttributeDescription: Examples of valid AttributeDescription:
cn cn
userCertificate;binary userCertificate;binary
One option, "binary", is defined in this document. Additional options Not all options can be associated with attributes held in the
may be defined in IETF standards-track and experimental RFCs. Options directory. A server will treat an AttributeDescription with any
beginning with "x-" are reserved for private experiments. Though any options it does not implement as unrecognized. The order in which
option or set of options could be associated with any AttributeType, options appear in the list MUST NOT be used to impart any semantic
the server support for certain combinations may be restricted by meaning. Servers MUST treat any two AttributeDescription with the
attribute type, syntaxes, or other factors. same AttributeType and options as equivalent.
An AttributeDescription with one or more options is treated as a An attribute description that contains mutually exclusive options
subtype of the attribute type without any options. Options MAY be shall be treated as unrecognized. That is, "cn;binary;gser" (where
mutually exclusive. An AttributeDescription with mutually exclusive "binary" and "gser" are mutually exclusive) is to be treated as an
options is treated as an undefined attribute type. Implementations unrecognized attribute.
MUST generate the <options> list sorted in ascending order, and
servers MUST treat any two AttributeDescription with the same There are multiple kinds of attribute description options. The LDAP
AttributeType and options as equivalent. A server will treat an technical specification details two kinds: tagging options (such as
AttributeDescription with any options it does not implement as an language tag options) and transfer options (such as ;binary). Other
unrecognized attribute type. documents may detail other kinds.
Tagging options can be held in the directory and are never mutually
exclusive. An attribute with N tagging options is considered a direct
subtype of all attributes of the same type and all but one of the N
options. If the type has a supertype, then the attribute is also
considered a direct subtype of the attribute of the supertype and the
N tagging options. That is, cn;lang_de;lang_en is considered a direct
subtype of cn;lang_de, cn;lang_en, and name;lang_de;lang_en (cn is a
subtype of name).
Transfer options are not held in the directory, they only affect the
encoding used to transfer values. The absence of a transfer option
implies the native encoding. Transfer options are mutually exclusive.
Specifying a transfer option when requesting attributes to be
returned in a SearchRequest causes that encoding to be used for that
attribute and its subtypes. That is, requesting name;binary requests
the attribute name and its subtypes (e.g., cn, sn, cn;lang_en, etc.)
be returned using binary transfer.
When specifying return attributes for a SearchRequest, clients SHOULD
avoid requesting the return of attributes related to each other in
the attribute subtyping hierarchy with different transfer encodings.
Sermersheim Internet-Draft - Expires July 2002 Page 12
Lightweight Directory Access Protocol Version 3
For example, requesting name;lang_en;binary and cn should be avoided
as it ambiguous as to how cn;lang_en is to be transferred. In such
cases, the server's behavior is undefined (the server can return the
values in either, neither, or both encodings).
Other documents may specify other kinds of options. These documents
must detail how new kinds of options relate to tagging and transfer
options. In particular, the document must describe how the options
relation to the attribute subtyping hierarchy.
One transfer option, "binary", is defined in this document.
Additional options may be defined in IETF standards-track and
experimental RFCs. Options beginning with "x-" are reserved for
private experiments.
The data type "AttributeDescriptionList" describes a list of 0 or The data type "AttributeDescriptionList" describes a list of 0 or
more attribute types. (A list of zero elements has special more attribute types. (A list of zero elements has special
significance in the Search request.) significance in the Search request.)
AttributeDescriptionList ::= SEQUENCE OF AttributeDescriptionList ::= SEQUENCE OF
AttributeDescription AttributeDescription
4.1.5.1. Binary Option 4.1.5.1. Binary Option
If the "binary" option is present in an AttributeDescription, it If the "binary" option is present in an AttributeDescription, it
overrides any string-based encoding representation defined for that overrides the native encoding representation defined for that
attribute in [RFC2252]. Instead the attribute is to be transferred as attribute in [RFC2252]. Instead the attribute is to be transferred as
a binary value encoded using the Basic Encoding Rules [X.690]. The a binary value encoded using the Basic Encoding Rules [X.690]. The
syntax of the binary value is an ASN.1 data type definition which is syntax of the binary value is an ASN.1 data type definition, which is
referenced by the "SYNTAX" part of the attribute type definition. referenced by the "SYNTAX" part of the attribute type definition.
The presence or absence of the "binary" option only affects the The presence or absence of the "binary" option only affects the
transfer of attribute values in protocol; servers store any transfer of attribute values in protocol; servers store any
particular attribute in a single format. If a client requests that a particular attribute in a single format. If a client requests that a
server return an attribute in the binary format, but the server server return an attribute in the binary format, but the server
cannot generate that format, the server MUST treat this attribute cannot generate that format, the server MUST treat this attribute
type as an unrecognized attribute type. Similarly, clients MUST NOT type as an unrecognized attribute type. Similarly, clients MUST NOT
expect servers to return an attribute in binary format if the client expect servers to return an attribute in binary format if the client
requested that attribute by name without the "binary" option. requested that attribute by name without the "binary" option.
This option is intended to be used with attributes whose syntax is a This option is intended to be used with attributes whose syntax is a
complex ASN.1 data type, and the structure of values of that type is complex ASN.1 data type, and the structure of values of that type is
Lightweight Directory Access Protocol Version 3
needed by clients. Examples of this kind of syntax are "Certificate" needed by clients. Examples of this kind of syntax are "Certificate"
and "CertificateList". and "CertificateList".
4.1.6. Attribute Value 4.1.6. Attribute Value
A field of type AttributeValue is an OCTET STRING containing an A field of type AttributeValue is an OCTET STRING containing an
encoded value of an AttributeValue data type. The value is string encoded value of an AttributeValue data type. The value is encoded
encoded unless an option specifying the transfer encoding is present according to its native encoding definition, unless an option
in the companion AttributeDescription to this AttributeValue (e.g. specifying the transfer encoding is present in the companion
"binary"). Multiple options specifying transfer encoding MUST NOT be AttributeDescription to the AttributeValue (e.g. "binary").
present.
The definition of string encodings for different syntaxes and types Sermersheim Internet-Draft - Expires July 2002 Page 13
may be found in other documents, and in particular [RFC2252]. Lightweight Directory Access Protocol Version 3
The native encoding definitions for different syntaxes and attribute
types may be found in other documents, and in particular [RFC2252].
At the time of this writing, there is only one AttributeDescription At the time of this writing, there is only one AttributeDescription
option used to specify transfer encoding--"binary", described in option used to specify transfer encoding--"binary", described in
section 4.1.5.1. section 4.1.5.1.
AttributeValue ::= OCTET STRING AttributeValue ::= OCTET STRING
Note that there is no defined limit on the size of this encoding; Note that there is no defined limit on the size of this encoding;
thus protocol values may include multi-megabyte attributes (e.g. thus protocol values may include multi-megabyte attributes (e.g.
photographs). photographs).
Attributes may be defined which have arbitrary and non-printable Attributes may be defined which have arbitrary and non-printable
syntax. Implementations MUST NEITHER simply display nor attempt to syntax. Implementations MUST NOT display nor attempt to decode as
decode as ASN.1 a value if its syntax is not known. The ASN.1, a value if its syntax is not known. The implementation may
implementation may attempt to discover the subschema of the source attempt to discover the subschema of the source entry, and retrieve
entry, and retrieve the values of attributeTypes from it. the values of attributeTypes from it.
Clients MUST NOT send attribute values in a request which are not Clients MUST NOT send attribute values in a request that are not
valid according to the syntax defined for the attributes. valid according to the syntax defined for the attributes.
4.1.7. Attribute Value Assertion 4.1.7. Attribute Value Assertion
The AttributeValueAssertion type definition is similar to the one in The AttributeValueAssertion type definition is similar to the one in
the X.500 directory standards. It contains an attribute description the X.500 directory standards. It contains an attribute description
and a matching rule assertion value suitable for that type. and a matching rule assertion value suitable for that type.
AttributeValueAssertion ::= SEQUENCE { AttributeValueAssertion ::= SEQUENCE {
attributeDesc AttributeDescription, attributeDesc AttributeDescription,
assertionValue AssertionValue } assertionValue AssertionValue }
AssertionValue ::= OCTET STRING AssertionValue ::= OCTET STRING
If an option specifying the transfer encoding is present in If an option specifying the transfer encoding is present in
attributeDesc, the assertionValue is encoded as specified by the attributeDesc, the assertionValue is encoded as specified by the
option. For example, if the "binary" option is present in the option. For example, if the "binary" option is present in the
attributeDesc, the AssertionValue is BER encoded. attributeDesc, the AssertionValue is BER encoded.
For all the string-valued user attributes described in [5], the For all the string-valued user attributes described in [RFC2252], the
assertion value syntax is the same as the value syntax. Clients may assertion value syntax is the same as the value syntax. Clients may
Lightweight Directory Access Protocol Version 3
use attribute values as assertion values in compare requests and use attribute values as assertion values in compare requests and
search filters. search filters.
Note however that the assertion syntax may be different from the Note however that the assertion syntax may be different from the
value syntax for other attributes or for non-equality matching rules. value syntax for other attributes or for non-equality matching rules.
These may have an assertion syntax which contains only part of the These may have an assertion syntax which contains only part of the
value. See section 20.2.1.8 of [X.501] for examples. value. See section 20.2.1.8 of [X.501] for examples.
4.1.8. Attribute 4.1.8. Attribute
An attribute consists of a type and one or more values of that type. An attribute consists of a type and one or more values of that type.
(Though attributes MUST have at least one value when stored, due to (Though attributes MUST have at least one value when stored, due to
access control restrictions the set may be empty when transferred access control restrictions the set may be empty when transferred
Sermersheim Internet-Draft - Expires July 2002 Page 14
Lightweight Directory Access Protocol Version 3
from the server to the client. This is described in section 4.5.2, from the server to the client. This is described in section 4.5.2,
concerning the PartialAttributeList type.) concerning the PartialAttributeList type.)
Attribute ::= SEQUENCE { Attribute ::= SEQUENCE {
type AttributeDescription, type AttributeDescription,
vals SET OF AttributeValue } vals SET OF AttributeValue }
Each attribute value is distinct in the set (no duplicates). The Each attribute value is distinct in the set (no duplicates). The
order of attribute values within the vals set is undefined and order of attribute values within the vals set is undefined and
implementation-dependent, and MUST NOT be relied upon. implementation-dependent, and MUST NOT be relied upon.
skipping to change at line 785 skipping to change at line 842
information is given in section 4.5 of [RFC2252]. information is given in section 4.5 of [RFC2252].
4.1.10. Result Message 4.1.10. Result Message
The LDAPResult is the construct used in this protocol to return The LDAPResult is the construct used in this protocol to return
success or failure indications from servers to clients. To various success or failure indications from servers to clients. To various
requests, servers will return responses of LDAPResult or responses requests, servers will return responses of LDAPResult or responses
containing the components of LDAPResponse to indicate the final containing the components of LDAPResponse to indicate the final
status of a protocol operation request. status of a protocol operation request.
Lightweight Directory Access Protocol Version 3
LDAPResult ::= SEQUENCE { LDAPResult ::= SEQUENCE {
resultCode ENUMERATED { resultCode ENUMERATED {
success (0), success (0),
operationsError (1), operationsError (1),
protocolError (2), protocolError (2),
timeLimitExceeded (3), timeLimitExceeded (3),
sizeLimitExceeded (4), sizeLimitExceeded (4),
compareFalse (5), compareFalse (5),
compareTrue (6), compareTrue (6),
authMethodNotSupported (7), authMethodNotSupported (7),
strongAuthRequired (8), strongAuthRequired (8),
-- 9 reserved -- -- 9 reserved --
referral (10), referral (10),
Sermersheim Internet-Draft - Expires July 2002 Page 15
Lightweight Directory Access Protocol Version 3
adminLimitExceeded (11), adminLimitExceeded (11),
unavailableCriticalExtension (12), unavailableCriticalExtension (12),
confidentialityRequired (13), confidentialityRequired (13),
saslBindInProgress (14), saslBindInProgress (14),
noSuchAttribute (16), noSuchAttribute (16),
undefinedAttributeType (17), undefinedAttributeType (17),
inappropriateMatching (18), inappropriateMatching (18),
constraintViolation (19), constraintViolation (19),
attributeOrValueExists (20), attributeOrValueExists (20),
invalidAttributeSyntax (21), invalidAttributeSyntax (21),
skipping to change at line 840 skipping to change at line 899
objectClassModsProhibited (69), objectClassModsProhibited (69),
-- 70 reserved for CLDAP -- -- 70 reserved for CLDAP --
affectsMultipleDSAs (71), affectsMultipleDSAs (71),
-- 72-79 unused -- -- 72-79 unused --
other (80) }, other (80) },
-- 81-90 reserved for APIs -- -- 81-90 reserved for APIs --
matchedDN LDAPDN, matchedDN LDAPDN,
errorMessage LDAPString, errorMessage LDAPString,
referral [3] Referral OPTIONAL } referral [3] Referral OPTIONAL }
Lightweight Directory Access Protocol Version 3
All the result codes with the exception of success, compareFalse and All the result codes with the exception of success, compareFalse and
compareTrue are to be treated as meaning the operation could not be compareTrue are to be treated as meaning the operation could not be
completed in its entirety. completed in its entirety.
Most of the result codes are based on problem indications from X.511 Most of the result codes are based on problem indications from X.511
error data types. Result codes from 16 to 21 indicate an error data types. Result codes from 16 to 21 indicate an
AttributeProblem, codes 32, 33, 34 and 36 indicate a NameProblem, AttributeProblem, codes 32, 33, 34 and 36 indicate a NameProblem,
codes 48, 49 and 50 indicate a SecurityProblem, codes 51 to 54 codes 48, 49 and 50 indicate a SecurityProblem, codes 51 to 54
indicate a ServiceProblem, and codes 64 to 69 and 71 indicates an indicate a ServiceProblem, and codes 64 to 69 and 71 indicates an
UpdateProblem. UpdateProblem.
If a client receives a result code which is not listed above, it is If a client receives a result code which is not listed above, it is
to be treated as an unknown error condition. to be treated as an unknown error condition.
Sermersheim Internet-Draft - Expires July 2002 Page 16
Lightweight Directory Access Protocol Version 3
The errorMessage field of this construct may, at the server's option, The errorMessage field of this construct may, at the server's option,
be used to return a string containing a textual, human-readable be used to return a string containing a textual, human-readable
(terminal control and page formatting characters should be avoided) (terminal control and page formatting characters should be avoided)
error diagnostic. As this error diagnostic is not standardized, error diagnostic. As this error diagnostic is not standardized,
implementations MUST NOT rely on the values returned. If the server implementations MUST NOT rely on the values returned. If the server
chooses not to return a textual diagnostic, the errorMessage field of chooses not to return a textual diagnostic, the errorMessage field of
the LDAPResult type MUST contain a zero length string. the LDAPResult type MUST contain a zero length string.
For result codes of noSuchObject, aliasProblem, invalidDNSyntax and For result codes of noSuchObject, aliasProblem, invalidDNSyntax and
aliasDereferencingProblem, the matchedDN field is set to the name of aliasDereferencingProblem, the matchedDN field is set to the name of
skipping to change at line 896 skipping to change at line 956
in which the search scope spans multiple naming contexts, and several in which the search scope spans multiple naming contexts, and several
different servers would need to be contacted to complete the different servers would need to be contacted to complete the
operation. Instead, continuation references, described in section operation. Instead, continuation references, described in section
4.5.3, are returned. 4.5.3, are returned.
Referral ::= SEQUENCE OF LDAPURL -- one or more Referral ::= SEQUENCE OF LDAPURL -- one or more
LDAPURL ::= LDAPString -- limited to characters permitted in LDAPURL ::= LDAPString -- limited to characters permitted in
-- URLs -- URLs
Lightweight Directory Access Protocol Version 3
If the client wishes to progress the operation, it MUST follow the If the client wishes to progress the operation, it MUST follow the
referral by contacting one of the servers. If multiple URLs are referral by contacting one of the servers. If multiple URLs are
present, the client assumes that any URL may be used to progress the present, the client assumes that any URL may be used to progress the
operation. operation.
URLs for servers implementing the LDAP protocol are written according URLs for servers implementing the LDAP protocol are written according
to [RFC2255]. If an alias was dereferenced, the <dn> part of the URL to [RFC2255]. If an alias was dereferenced, the <dn> part of the URL
MUST be present, with the new target object name. If the <dn> part is MUST be present, with the new target object name. If the <dn> part is
present, the client MUST use this name in its next request to present, the client MUST use this name in its next request to
progress the operation, and if it is not present the client will use progress the operation, and if it is not present the client will use
the same name as in the original request. Some servers (e.g. the same name as in the original request. Some servers (e.g.
participating in distributed indexing) may provide a different filter participating in distributed indexing) may provide a different filter
in a referral for a search operation. If the filter part of the URL in a referral for a search operation. If the filter part of the URL
is present in an LDAPURL, the client MUST use this filter in its next is present in an LDAPURL, the client MUST use this filter in its next
Sermersheim Internet-Draft - Expires July 2002 Page 17
Lightweight Directory Access Protocol Version 3
request to progress this search, and if it is not present the client request to progress this search, and if it is not present the client
MUST use the same filter as it used for that search. Other aspects of MUST use the same filter as it used for that search. Other aspects of
the new request may be the same or different as the request which the new request may be the same or different as the request which
generated the referral. generated the referral.
Note that UTF-8 characters appearing in a DN or search filter may not Note that UTF-8 characters appearing in a DN or search filter may not
be legal for URLs (e.g. spaces) and MUST be escaped using the % be legal for URLs (e.g. spaces) and MUST be escaped using the %
method in [RFC2396]. method in [RFC2396].
Other kinds of URLs may be returned, so long as the operation could Other kinds of URLs may be returned, so long as the operation could
skipping to change at line 952 skipping to change at line 1014
control accompanies one of the following requests: bindRequest, control accompanies one of the following requests: bindRequest,
searchRequest, modifyRequest, addRequest, delRequest, modDNRequest, searchRequest, modifyRequest, addRequest, delRequest, modDNRequest,
compareRequest, or extendedReq. The use of the criticality field for compareRequest, or extendedReq. The use of the criticality field for
a control that is part of any other operation is ignored and treated a control that is part of any other operation is ignored and treated
as FALSE. as FALSE.
If the server recognizes the control type and it is appropriate for If the server recognizes the control type and it is appropriate for
the operation, the server will make use of the control when the operation, the server will make use of the control when
performing the operation. performing the operation.
Lightweight Directory Access Protocol Version 3
If the server does not recognize the control type or it is not If the server does not recognize the control type or it is not
appropriate for the operation, and the criticality field is TRUE, the appropriate for the operation, and the criticality field is TRUE, the
server MUST NOT perform the operation, and MUST instead return the server MUST NOT perform the operation, and MUST instead return the
resultCode unavailableCriticalExtension. resultCode unavailableCriticalExtension.
If the control is unrecognized or inappropriate but the criticality If the control is unrecognized or inappropriate but the criticality
field is FALSE, the server MUST ignore the control. field is FALSE, the server MUST ignore the control.
The controlValue contains any information associated with the The controlValue contains any information associated with the
control, and its format is defined for the control. Implementations control, and its format is defined for the control. Implementations
MUST be prepared to handle arbitrary contents of the controlValue MUST be prepared to handle arbitrary contents of the controlValue
octet string, including zero bytes. It is absent only if there is no octet string, including zero bytes. It is absent only if there is no
value information which is associated with a control of its type. value information which is associated with a control of its type.
Sermersheim Internet-Draft - Expires July 2002 Page 18
Lightweight Directory Access Protocol Version 3
This document does not define any controls. Controls may be defined This document does not define any controls. Controls may be defined
in other documents. The definition of a control consists of: in other documents. The definition of a control consists of:
- the OBJECT IDENTIFIER assigned to the control, - the OBJECT IDENTIFIER assigned to the control,
- whether the control is always noncritical, always critical, or - whether the control is always noncritical, always critical, or
critical at the client's option, critical at the client's option,
- the format of the controlValue contents of the control. - the format of the controlValue contents of the control.
skipping to change at line 1008 skipping to change at line 1071
SaslCredentials ::= SEQUENCE { SaslCredentials ::= SEQUENCE {
mechanism LDAPString, mechanism LDAPString,
credentials OCTET STRING OPTIONAL } credentials OCTET STRING OPTIONAL }
Parameters of the Bind Request are: Parameters of the Bind Request are:
- version: A version number indicating the version of the protocol - version: A version number indicating the version of the protocol
to be used in this protocol session. This document describes to be used in this protocol session. This document describes
version 3 of the LDAP protocol. Note that there is no version version 3 of the LDAP protocol. Note that there is no version
negotiation, and the client just sets this parameter to the negotiation, and the client just sets this parameter to the
Lightweight Directory Access Protocol Version 3
version it desires. If the client requests protocol version 2, a version it desires. If the client requests protocol version 2, a
server that supports the version 2 protocol as described in server that supports the version 2 protocol as described in
[RFC1777] will not return any v3-specific protocol fields. (Note [RFC1777] will not return any v3-specific protocol fields. (Note
that not all LDAP servers will support protocol version 2, since that not all LDAP servers will support protocol version 2, since
they may be unable to generate the attribute syntaxes associated they may be unable to generate the attribute syntaxes associated
with version 2.) with version 2.)
- name: The name of the directory object that the client wishes to - name: The name of the directory object that the client wishes to
bind as. This field may take on a null value (a zero length bind as. This field may take on a null value (a zero length
string) for the purposes of anonymous binds, when authentication string) for the purposes of anonymous binds, when authentication
has been performed at a lower layer, or when using SASL has been performed at a lower layer, or when using SASL
credentials with a mechanism that includes the name in the credentials with a mechanism that includes the name in the
credentials. Server behavior is undefined when the name is a null credentials. Server behavior is undefined when the name is a null
value, simple authentication is used, and a password is specified. value, simple authentication is used, and a password is specified.
Sermersheim Internet-Draft - Expires July 2002 Page 19
Lightweight Directory Access Protocol Version 3
Note that the server SHOULD NOT perform any alias dereferencing in Note that the server SHOULD NOT perform any alias dereferencing in
determining the object to bind as. determining the object to bind as.
- authentication: information used to authenticate the name, if any, - authentication: information used to authenticate the name, if any,
provided in the Bind Request. provided in the Bind Request.
Upon receipt of a Bind Request, a protocol server will authenticate Upon receipt of a Bind Request, a protocol server will authenticate
the requesting client, if necessary. The server will then return a the requesting client, if necessary. The server will then return a
Bind Response to the client indicating the status of the Bind Response to the client indicating the status of the
authentication. authentication.
skipping to change at line 1066 skipping to change at line 1130
abort a negotiation if it wishes to try again with the same SASL abort a negotiation if it wishes to try again with the same SASL
mechanism. mechanism.
Unlike LDAP v2, the client need not send a Bind Request in the first Unlike LDAP v2, the client need not send a Bind Request in the first
PDU of the connection. The client may request any operations and the PDU of the connection. The client may request any operations and the
server MUST treat these as anonymous. If the server requires that the server MUST treat these as anonymous. If the server requires that the
client bind before browsing or modifying the directory, the server client bind before browsing or modifying the directory, the server
MAY reject a request other than binding, unbinding or an extended MAY reject a request other than binding, unbinding or an extended
request with the "operationsError" result. request with the "operationsError" result.
Lightweight Directory Access Protocol Version 3
If the client did not bind before sending a request and receives an If the client did not bind before sending a request and receives an
operationsError, it may then send a Bind Request. If this also fails operationsError, it may then send a Bind Request. If this also fails
or the client chooses not to bind on the existing connection, it will or the client chooses not to bind on the existing connection, it will
close the connection, reopen it and begin again by first sending a close the connection, reopen it and begin again by first sending a
PDU with a Bind Request. This will aid in interoperating with servers PDU with a Bind Request. This will aid in interoperating with servers
implementing other versions of LDAP. implementing other versions of LDAP.
Clients MAY send multiple bind requests on a connection to change Clients MAY send multiple bind requests on a connection to change
their credentials. A subsequent bind process has the effect of their credentials. A subsequent bind process has the effect of
abandoning all operations outstanding on the connection. (This abandoning all operations outstanding on the connection. (This
simplifies server implementation.) Authentication from earlier binds simplifies server implementation.) Authentication from earlier binds
are subsequently ignored, and so if the bind fails, the connection are subsequently ignored, and so if the bind fails, the connection
will be treated as anonymous. If a SASL transfer encryption or will be treated as anonymous. If a SASL transfer encryption or
Sermersheim Internet-Draft - Expires July 2002 Page 20
Lightweight Directory Access Protocol Version 3
integrity mechanism has been negotiated, and that mechanism does not integrity mechanism has been negotiated, and that mechanism does not
support the changing of credentials from one identity to another, support the changing of credentials from one identity to another,
then the client MUST instead establish a new connection. then the client MUST instead establish a new connection.
4.2.2. Authentication and Other Security Services 4.2.2. Authentication and Other Security Services
The simple authentication option provides minimal authentication The simple authentication option provides minimal authentication
facilities, with the contents of the authentication field consisting facilities, with the contents of the authentication field consisting
only of a cleartext password. Note that the use of cleartext only of a cleartext password. Note that the use of cleartext
passwords is not recommended over open networks when the underlying passwords is not recommended over open networks when the underlying
skipping to change at line 1121 skipping to change at line 1187
The client can request that the server use authentication information The client can request that the server use authentication information
from a lower layer protocol by using the SASL EXTERNAL mechanism. from a lower layer protocol by using the SASL EXTERNAL mechanism.
4.2.3. Bind Response 4.2.3. Bind Response
The Bind Response is defined as follows. The Bind Response is defined as follows.
BindResponse ::= [APPLICATION 1] SEQUENCE { BindResponse ::= [APPLICATION 1] SEQUENCE {
COMPONENTS OF LDAPResult, COMPONENTS OF LDAPResult,
Lightweight Directory Access Protocol Version 3
serverSaslCreds [7] OCTET STRING OPTIONAL } serverSaslCreds [7] OCTET STRING OPTIONAL }
BindResponse consists simply of an indication from the server of the BindResponse consists simply of an indication from the server of the
status of the client's request for authentication. status of the client's request for authentication.
If the bind was successful, the resultCode will be success, otherwise If the bind was successful, the resultCode will be success, otherwise
it will be one of: it will be one of:
- operationsError: server encountered an internal error. - operationsError: server encountered an internal error.
- protocolError: unrecognized version number or incorrect PDU - protocolError: unrecognized version number or incorrect PDU
structure. structure.
- authMethodNotSupported: unrecognized SASL mechanism name. - authMethodNotSupported: unrecognized SASL mechanism name.
Sermersheim Internet-Draft - Expires July 2002 Page 21
Lightweight Directory Access Protocol Version 3
- strongAuthRequired: the server requires authentication be - strongAuthRequired: the server requires authentication be
performed with a SASL mechanism. performed with a SASL mechanism.
- referral: this server cannot accept this bind and the client - referral: this server cannot accept this bind and the client
should try another. should try another.
- saslBindInProgress: the server requires the client to send a new - saslBindInProgress: the server requires the client to send a new
bind request, with the same sasl mechanism, to continue the bind request, with the same sasl mechanism, to continue the
authentication process. authentication process.
skipping to change at line 1179 skipping to change at line 1245
communicating, or to perform "challenge-response" authentication. If communicating, or to perform "challenge-response" authentication. If
the client bound with the password choice, or the SASL mechanism does the client bound with the password choice, or the SASL mechanism does
not require the server to return information to the client, then this not require the server to return information to the client, then this
field is not to be included in the result. field is not to be included in the result.
4.3. Unbind Operation 4.3. Unbind Operation
The function of the Unbind Operation is to terminate a protocol The function of the Unbind Operation is to terminate a protocol
session. The Unbind Operation is defined as follows: session. The Unbind Operation is defined as follows:
Lightweight Directory Access Protocol Version 3
UnbindRequest ::= [APPLICATION 2] NULL UnbindRequest ::= [APPLICATION 2] NULL
The Unbind Operation has no response defined. Upon transmission of an The Unbind Operation has no response defined. Upon transmission of an
UnbindRequest, a protocol client may assume that the protocol session UnbindRequest, a protocol client may assume that the protocol session
is terminated. Upon receipt of an UnbindRequest, a protocol server is terminated. Upon receipt of an UnbindRequest, a protocol server
may assume that the requesting client has terminated the session and may assume that the requesting client has terminated the session and
that all outstanding requests may be discarded, and may close the that all outstanding requests may be discarded, and may close the
connection. connection.
4.4. Unsolicited Notification 4.4. Unsolicited Notification
An unsolicited notification is an LDAPMessage sent from the server to An unsolicited notification is an LDAPMessage sent from the server to
the client which is not in response to any LDAPMessage received by the client which is not in response to any LDAPMessage received by
Sermersheim Internet-Draft - Expires July 2002 Page 22
Lightweight Directory Access Protocol Version 3
the server. It is used to signal an extraordinary condition in the the server. It is used to signal an extraordinary condition in the
server or in the connection between the client and the server. The server or in the connection between the client and the server. The
notification is of an advisory nature, and the server will not expect notification is of an advisory nature, and the server will not expect
any response to be returned from the client. any response to be returned from the client.
The unsolicited notification is structured as an LDAPMessage in which The unsolicited notification is structured as an LDAPMessage in which
the messageID is 0 and protocolOp is of the extendedResp form. The the messageID is 0 and protocolOp is of the extendedResp form. The
responseName field of the ExtendedResponse is present. The LDAPOID responseName field of the ExtendedResponse is present. The LDAPOID
value MUST be unique for this notification, and not be used in any value MUST be unique for this notification, and not be used in any
other situation. other situation.
skipping to change at line 1233 skipping to change at line 1301
The following resultCode values are to be used in this notification: The following resultCode values are to be used in this notification:
- protocolError: The server has received data from the client in - protocolError: The server has received data from the client in
which the LDAPMessage structure could not be parsed. which the LDAPMessage structure could not be parsed.
- strongAuthRequired: The server has detected that an established - strongAuthRequired: The server has detected that an established
underlying security association protecting communication between underlying security association protecting communication between
the client and server has unexpectedly failed or been compromised. the client and server has unexpectedly failed or been compromised.
Lightweight Directory Access Protocol Version 3
- unavailable: This server will stop accepting new connections and - unavailable: This server will stop accepting new connections and
operations on all existing connections, and be unavailable for an operations on all existing connections, and be unavailable for an
extended period of time. The client may make use of an alternative extended period of time. The client may make use of an alternative
server. server.
After sending this notice, the server MUST close the connection. After sending this notice, the server MUST close the connection.
After receiving this notice, the client MUST NOT transmit any further After receiving this notice, the client MUST NOT transmit any further
on the connection, and may abruptly close the connection. on the connection, and may abruptly close the connection.
4.5. Search Operation 4.5. Search Operation
The Search Operation allows a client to request that a search be The Search Operation allows a client to request that a search be
performed on its behalf by a server. This can be used to read performed on its behalf by a server. This can be used to read
attributes from a single entry, from entries immediately below a attributes from a single entry, from entries immediately below a
particular entry, or a whole subtree of entries. particular entry, or a whole subtree of entries.
Sermersheim Internet-Draft - Expires July 2002 Page 23
Lightweight Directory Access Protocol Version 3
4.5.1. Search Request 4.5.1. Search Request
The Search Request is defined as follows: The Search Request is defined as follows:
SearchRequest ::= [APPLICATION 3] SEQUENCE { SearchRequest ::= [APPLICATION 3] SEQUENCE {
baseObject LDAPDN, baseObject LDAPDN,
scope ENUMERATED { scope ENUMERATED {
baseObject (0), baseObject (0),
singleLevel (1), singleLevel (1),
wholeSubtree (2) }, wholeSubtree (2) },
skipping to change at line 1289 skipping to change at line 1358
lessOrEqual [6] AttributeValueAssertion, lessOrEqual [6] AttributeValueAssertion,
present [7] AttributeDescription, present [7] AttributeDescription,
approxMatch [8] AttributeValueAssertion, approxMatch [8] AttributeValueAssertion,
extensibleMatch [9] MatchingRuleAssertion } extensibleMatch [9] MatchingRuleAssertion }
SubstringFilter ::= SEQUENCE { SubstringFilter ::= SEQUENCE {
type AttributeDescription, type AttributeDescription,
-- at least one must be present, -- at least one must be present,
-- initial and final can occur at most once -- initial and final can occur at most once
substrings SEQUENCE OF CHOICE { substrings SEQUENCE OF CHOICE {
Lightweight Directory Access Protocol Version 3
initial [0] AssertionValue, initial [0] AssertionValue,
any [1] AssertionValue, any [1] AssertionValue,
final [2] AssertionValue } } final [2] AssertionValue } }
MatchingRuleAssertion ::= SEQUENCE { MatchingRuleAssertion ::= SEQUENCE {
matchingRule [1] MatchingRuleId OPTIONAL, matchingRule [1] MatchingRuleId OPTIONAL,
type [2] AttributeDescription OPTIONAL, type [2] AttributeDescription OPTIONAL,
matchValue [3] AssertionValue, matchValue [3] AssertionValue,
dnAttributes [4] BOOLEAN DEFAULT FALSE } dnAttributes [4] BOOLEAN DEFAULT FALSE }
Parameters of the Search Request are: Parameters of the Search Request are:
- baseObject: An LDAPDN that is the base object entry relative to - baseObject: An LDAPDN that is the base object entry relative to
which the search is to be performed. which the search is to be performed.
Sermersheim Internet-Draft - Expires July 2002 Page 24
Lightweight Directory Access Protocol Version 3
- scope: An indicator of the scope of the search to be performed. - scope: An indicator of the scope of the search to be performed.
The semantics of the possible values of this field are identical The semantics of the possible values of this field are identical
to the semantics of the scope field in the X.511 Search Operation. to the semantics of the scope field in the X.511 Search Operation.
- derefAliases: An indicator as to how alias objects (as defined in - derefAliases: An indicator as to how alias objects (as defined in
X.501) are to be handled in searching. The semantics of the X.501) are to be handled in searching. The semantics of the
possible values of this field are: possible values of this field are:
neverDerefAliases: do not dereference aliases in searching neverDerefAliases: do not dereference aliases in searching
or in locating the base object of the search; or in locating the base object of the search;
skipping to change at line 1346 skipping to change at line 1415
seconds) allowed for a search. A value of 0 in this field seconds) allowed for a search. A value of 0 in this field
indicates that no client-requested time limit restrictions are in indicates that no client-requested time limit restrictions are in
effect for the search. effect for the search.
- typesOnly: An indicator as to whether search results will contain - typesOnly: An indicator as to whether search results will contain
both attribute types and values, or just attribute types. Setting both attribute types and values, or just attribute types. Setting
this field to TRUE causes only attribute types (no values) to be this field to TRUE causes only attribute types (no values) to be
returned. Setting this field to FALSE causes both attribute types returned. Setting this field to FALSE causes both attribute types
and values to be returned. and values to be returned.
Lightweight Directory Access Protocol Version 3
- filter: A filter that defines the conditions that must be - filter: A filter that defines the conditions that must be
fulfilled in order for the search to match a given entry. fulfilled in order for the search to match a given entry.
The 'and', 'or' and 'not' choices can be used to form combinations The 'and', 'or' and 'not' choices can be used to form combinations
of filters. At least one filter element MUST be present in an of filters. At least one filter element MUST be present in an
'and' or 'or' choice. The others match against individual 'and' or 'or' choice. The others match against individual
attribute values of entries in the scope of the search. attribute values of entries in the scope of the search.
(Implementor's note: the 'not' filter is an example of a tagged (Implementor's note: the 'not' filter is an example of a tagged
choice in an implicitly-tagged module. In BER this is treated as choice in an implicitly-tagged module. In BER this is treated as
if the tag was explicit.) if the tag was explicit.)
A server MUST evaluate filters according to the three-valued logic A server MUST evaluate filters according to the three-valued logic
of X.511 (1993) section 7.8.1. In summary, a filter is evaluated of X.511 (1993) section 7.8.1. In summary, a filter is evaluated
to either "TRUE", "FALSE" or "Undefined". If the filter evaluates to either "TRUE", "FALSE" or "Undefined". If the filter evaluates
to TRUE for a particular entry, then the attributes of that entry to TRUE for a particular entry, then the attributes of that entry
Sermersheim Internet-Draft - Expires July 2002 Page 25
Lightweight Directory Access Protocol Version 3
are returned as part of the search result (subject to any are returned as part of the search result (subject to any
applicable access control restrictions). If the filter evaluates applicable access control restrictions). If the filter evaluates
to FALSE or Undefined, then the entry is ignored for the search. to FALSE or Undefined, then the entry is ignored for the search.
A filter of the "and" choice is TRUE if all the filters in the SET A filter of the "and" choice is TRUE if all the filters in the SET
OF evaluate to TRUE, FALSE if at least one filter is FALSE, and OF evaluate to TRUE, FALSE if at least one filter is FALSE, and
otherwise Undefined. A filter of the "or" choice is FALSE if all otherwise Undefined. A filter of the "or" choice is FALSE if all
of the filters in the SET OF evaluate to FALSE, TRUE if at least of the filters in the SET OF evaluate to FALSE, TRUE if at least
one filter is TRUE, and Undefined otherwise. A filter of the "not" one filter is TRUE, and Undefined otherwise. A filter of the "not"
choice is TRUE if the filter being negated is FALSE, FALSE if it choice is TRUE if the filter being negated is FALSE, FALSE if it
skipping to change at line 1402 skipping to change at line 1473
otherwise the filter item is undefined. If the dnAttributes field otherwise the filter item is undefined. If the dnAttributes field
is set to TRUE, the match is applied against all the attributes in is set to TRUE, the match is applied against all the attributes in
an entry's distinguished name as well, and also evaluates to TRUE an entry's distinguished name as well, and also evaluates to TRUE
if there is at least one attribute in the distinguished name for if there is at least one attribute in the distinguished name for
which the filter item evaluates to TRUE. (Editors note: The which the filter item evaluates to TRUE. (Editors note: The
dnAttributes field is present so that there does not need to be dnAttributes field is present so that there does not need to be
multiple versions of generic matching rules such as for word multiple versions of generic matching rules such as for word
matching, one to apply to entries and another to apply to entries matching, one to apply to entries and another to apply to entries
and dn attributes as well). and dn attributes as well).
Lightweight Directory Access Protocol Version 3
A filter item evaluates to Undefined when the server would not be A filter item evaluates to Undefined when the server would not be
able to determine whether the assertion value matches an entry. If able to determine whether the assertion value matches an entry. If
an attribute description in an equalityMatch, substrings, an attribute description in an equalityMatch, substrings,
greaterOrEqual, lessOrEqual, approxMatch or extensibleMatch filter greaterOrEqual, lessOrEqual, approxMatch or extensibleMatch filter
is not recognized by the server, a matching rule id in the is not recognized by the server, a matching rule id in the
extensibleMatch is not recognized by the server, the assertion extensibleMatch is not recognized by the server, the assertion
value cannot be parsed, or the type of filtering requested is not value cannot be parsed, or the type of filtering requested is not
implemented, then the filter is Undefined. Thus for example if a implemented, then the filter is Undefined. Thus for example if a
server did not recognize the attribute type shoeSize, a filter of server did not recognize the attribute type shoeSize, a filter of
(shoeSize=*) would evaluate to FALSE, and the filters (shoeSize=*) would evaluate to FALSE, and the filters
(shoeSize=12), (shoeSize>=12) and (shoeSize<=12) would evaluate to (shoeSize=12), (shoeSize>=12) and (shoeSize<=12) would evaluate to
Undefined. Undefined.
Servers MUST NOT return errors if attribute descriptions or Servers MUST NOT return errors if attribute descriptions or
matching rule ids are not recognized, or assertion values cannot matching rule ids are not recognized, or assertion values cannot
Sermersheim Internet-Draft - Expires July 2002 Page 26
Lightweight Directory Access Protocol Version 3
be parsed. More details of filter processing are given in section be parsed. More details of filter processing are given in section
7.8 of [X.511]. 7.8 of [X.511].
- attributes: A list of the attributes to be returned from each - attributes: A list of the attributes to be returned from each
entry which matches the search filter. There are two special entry which matches the search filter. There are two special
values which may be used: an empty list with no attributes, and values which may be used: an empty list with no attributes, and
the attribute description string "*". Both of these signify that the attribute description string "*". Both of these signify that
all user attributes are to be returned. (The "*" allows the all user attributes are to be returned. (The "*" allows the client
client to request all user attributes in addition to specific to request all user attributes in addition to specific operational
operational attributes). attributes).
Attributes MUST be named at most once in the list, and are Attributes MUST be named at most once in the list, and are
returned at most once in an entry. If there are attribute returned at most once in an entry. If there are attribute
descriptions in the list which are not recognized, they are descriptions in the list which are not recognized, they are
ignored by the server. ignored by the server.
If the client does not want any attributes returned, it can If the client does not want any attributes returned, it can
specify a list containing only the attribute with OID "1.1". This specify a list containing only the attribute with OID "1.1". This
OID was chosen arbitrarily and does not correspond to any OID was chosen arbitrarily and does not correspond to any
attribute in use. attribute in use.
skipping to change at line 1458 skipping to change at line 1531
Note that an X.500 "list"-like operation can be emulated by the Note that an X.500 "list"-like operation can be emulated by the
client requesting a one-level LDAP search operation with a filter client requesting a one-level LDAP search operation with a filter
checking for the presence of the objectClass attribute, and that an checking for the presence of the objectClass attribute, and that an
X.500 "read"-like operation can be emulated by a base object LDAP X.500 "read"-like operation can be emulated by a base object LDAP
search operation with the same filter. A server which provides a search operation with the same filter. A server which provides a
gateway to X.500 is not required to use the Read or List operations, gateway to X.500 is not required to use the Read or List operations,
although it may choose to do so, and if it does, it must provide the although it may choose to do so, and if it does, it must provide the
same semantics as the X.500 search operation. same semantics as the X.500 search operation.
Lightweight Directory Access Protocol Version 3
4.5.2. Search Result 4.5.2. Search Result
The results of the search attempted by the server upon receipt of a The results of the search attempted by the server upon receipt of a
Search Request are returned in Search Responses, which are LDAP Search Request are returned in Search Responses, which are LDAP
messages containing either SearchResultEntry, SearchResultReference, messages containing either SearchResultEntry, SearchResultReference,
or SearchResultDone data types. or SearchResultDone data types.
SearchResultEntry ::= [APPLICATION 4] SEQUENCE { SearchResultEntry ::= [APPLICATION 4] SEQUENCE {
objectName LDAPDN, objectName LDAPDN,
attributes PartialAttributeList } attributes PartialAttributeList }
PartialAttributeList ::= SEQUENCE OF SEQUENCE { PartialAttributeList ::= SEQUENCE OF SEQUENCE {
type AttributeDescription, type AttributeDescription,
vals SET OF AttributeValue } vals SET OF AttributeValue }
-- implementors should note that the PartialAttributeList may -- implementors should note that the PartialAttributeList may
Sermersheim Internet-Draft - Expires July 2002 Page 27
Lightweight Directory Access Protocol Version 3
-- have zero elements (if none of the attributes of that entry -- have zero elements (if none of the attributes of that entry
-- were requested, or could be returned), and that the vals set -- were requested, or could be returned), and that the vals set
-- may also have zero elements (if types only was requested, or -- may also have zero elements (if types only was requested, or
-- all values were excluded from the result.) -- all values were excluded from the result.)
SearchResultReference ::= [APPLICATION 19] SEQUENCE OF LDAPURL SearchResultReference ::= [APPLICATION 19] SEQUENCE OF LDAPURL
-- at least one LDAPURL element must be present -- at least one LDAPURL element must be present
SearchResultDone ::= [APPLICATION 5] LDAPResult SearchResultDone ::= [APPLICATION 5] LDAPResult
skipping to change at line 1514 skipping to change at line 1589
attributes is subject to access control and other administrative attributes is subject to access control and other administrative
policy. Some attributes may be returned in binary format (indicated policy. Some attributes may be returned in binary format (indicated
by the AttributeDescription in the response having the "binary" by the AttributeDescription in the response having the "binary"
option present). option present).
Some attributes may be constructed by the server and appear in a Some attributes may be constructed by the server and appear in a
SearchResultEntry attribute list, although they are not stored SearchResultEntry attribute list, although they are not stored
attributes of an entry. Clients MUST NOT assume that all attributes attributes of an entry. Clients MUST NOT assume that all attributes
can be modified, even if permitted by access control. can be modified, even if permitted by access control.
Lightweight Directory Access Protocol Version 3
4.5.3. Continuation References in the Search Result 4.5.3. Continuation References in the Search Result
If the server was able to locate the entry referred to by the If the server was able to locate the entry referred to by the
baseObject but was unable to search all the entries in the scope at baseObject but was unable to search all the entries in the scope at
and under the baseObject, the server may return one or more and under the baseObject, the server may return one or more
SearchResultReference entries, each containing a reference to another SearchResultReference entries, each containing a reference to another
set of servers for continuing the operation. A server MUST NOT return set of servers for continuing the operation. A server MUST NOT return
any SearchResultReference if it has not located the baseObject and any SearchResultReference if it has not located the baseObject and
thus has not searched any entries; in this case it would return a thus has not searched any entries; in this case it would return a
SearchResultDone containing a referral resultCode. SearchResultDone containing a referral resultCode.
In the absence of indexing information provided to a server from In the absence of indexing information provided to a server from
servers holding subordinate naming contexts, SearchResultReference servers holding subordinate naming contexts, SearchResultReference
responses are not affected by search filters and are always returned responses are not affected by search filters and are always returned
when in scope. when in scope.
Sermersheim Internet-Draft - Expires July 2002 Page 28
Lightweight Directory Access Protocol Version 3
The SearchResultReference is of the same data type as the Referral. The SearchResultReference is of the same data type as the Referral.
URLs for servers implementing the LDAP protocol are written according URLs for servers implementing the LDAP protocol are written according
to [RFC2255]. The <dn> part MUST be present in the URL, with the new to [RFC2255]. The <dn> part MUST be present in the URL, with the new
target object name. The client MUST use this name in its next target object name. The client MUST use this name in its next
request. Some servers (e.g. part of a distributed index exchange request. Some servers (e.g. part of a distributed index exchange
system) may provide a different filter in the URLs of the system) may provide a different filter in the URLs of the
SearchResultReference. If the filter part of the URL is present in an SearchResultReference. If the filter part of the URL is present in an
LDAP URL, the client MUST use the new filter in its next request to LDAP URL, the client MUST use the new filter in its next request to
progress the search, and if the filter part is absent the client will progress the search, and if the filter part is absent the client will
use again the same filter. Other aspects of the new search request use again the same filter. Other aspects of the new search request
skipping to change at line 1570 skipping to change at line 1646
"O=MNN,C=WW" and the entry "CN=Manager,O=MNN,C=WW". It knows that "O=MNN,C=WW" and the entry "CN=Manager,O=MNN,C=WW". It knows that
either LDAP-capable servers (hostb) or (hostc) hold either LDAP-capable servers (hostb) or (hostc) hold
"OU=People,O=MNN,C=WW" (one is the master and the other server a "OU=People,O=MNN,C=WW" (one is the master and the other server a
shadow), and that LDAP-capable server (hostd) holds the subtree shadow), and that LDAP-capable server (hostd) holds the subtree
"OU=Roles,O=MNN,C=WW". If a subtree search of "O=MNN,C=WW" is "OU=Roles,O=MNN,C=WW". If a subtree search of "O=MNN,C=WW" is
requested to the contacted server, it may return the following: requested to the contacted server, it may return the following:
SearchResultEntry for O=MNN,C=WW SearchResultEntry for O=MNN,C=WW
SearchResultEntry for CN=Manager,O=MNN,C=WW SearchResultEntry for CN=Manager,O=MNN,C=WW
SearchResultReference { SearchResultReference {
Lightweight Directory Access Protocol Version 3
ldap://hostb/OU=People,O=MNN,C=WW ldap://hostb/OU=People,O=MNN,C=WW
ldap://hostc/OU=People,O=MNN,C=WW ldap://hostc/OU=People,O=MNN,C=WW
} }
SearchResultReference { SearchResultReference {
ldap://hostd/OU=Roles,O=MNN,C=WW ldap://hostd/OU=Roles,O=MNN,C=WW
} }
SearchResultDone (success) SearchResultDone (success)
Client implementors should note that when following a Client implementors should note that when following a
SearchResultReference, additional SearchResultReference may be SearchResultReference, additional SearchResultReference may be
generated. Continuing the example, if the client contacted the server generated. Continuing the example, if the client contacted the server
(hostb) and issued the search for the subtree "OU=People,O=MNN,C=WW", (hostb) and issued the search for the subtree "OU=People,O=MNN,C=WW",
the server might respond as follows: the server might respond as follows:
SearchResultEntry for OU=People,O=MNN,C=WW SearchResultEntry for OU=People,O=MNN,C=WW
Sermersheim Internet-Draft - Expires July 2002 Page 29
Lightweight Directory Access Protocol Version 3
SearchResultReference { SearchResultReference {
ldap://hoste/OU=Managers,OU=People,O=MNN,C=WW ldap://hoste/OU=Managers,OU=People,O=MNN,C=WW
} }
SearchResultReference { SearchResultReference {
ldap://hostf/OU=Consultants,OU=People,O=MNN,C=WW ldap://hostf/OU=Consultants,OU=People,O=MNN,C=WW
} }
SearchResultDone (success) SearchResultDone (success)
If the contacted server does not hold the base object for the search, If the contacted server does not hold the base object for the search,
then it will return a referral to the client. For example, if the then it will return a referral to the client. For example, if the
skipping to change at line 1626 skipping to change at line 1703
delete (1), delete (1),
replace (2) }, replace (2) },
modification AttributeTypeAndValues } } modification AttributeTypeAndValues } }
AttributeTypeAndValues ::= SEQUENCE { AttributeTypeAndValues ::= SEQUENCE {
type AttributeDescription, type AttributeDescription,
vals SET OF AttributeValue } vals SET OF AttributeValue }
Parameters of the Modify Request are: Parameters of the Modify Request are:
Lightweight Directory Access Protocol Version 3
- object: The object to be modified. The value of this field - object: The object to be modified. The value of this field
contains the DN of the entry to be modified. The server will not contains the DN of the entry to be modified. The server will not
perform any alias dereferencing in determining the object to be perform any alias dereferencing in determining the object to be
modified. modified.
- modification: A list of modifications to be performed on the - modification: A list of modifications to be performed on the
entry. The entire list of entry modifications MUST be performed in entry. The entire list of entry modifications MUST be performed in
the order they are listed, as a single atomic operation. While the order they are listed, as a single atomic operation. While
individual modifications may violate the directory schema, the individual modifications may violate the directory schema, the
resulting entry after the entire list of modifications is resulting entry after the entire list of modifications is
performed MUST conform to the requirements of the directory performed MUST conform to the requirements of the directory
schema. The values that may be taken on by the 'operation' field schema. The values that may be taken on by the 'operation' field
in each modification construct have the following semantics in each modification construct have the following semantics
respectively: respectively:
Sermersheim Internet-Draft - Expires July 2002 Page 30
Lightweight Directory Access Protocol Version 3
add: add values listed to the given attribute, creating the add: add values listed to the given attribute, creating the
attribute if necessary; attribute if necessary;
delete: delete values listed from the given attribute, delete: delete values listed from the given attribute,
removing the entire attribute if no values are listed, or removing the entire attribute if no values are listed, or
if all current values of the attribute are listed for if all current values of the attribute are listed for
deletion; deletion;
replace: replace all existing values of the given attribute replace: replace all existing values of the given attribute
with the new values listed, creating the attribute if it with the new values listed, creating the attribute if it
skipping to change at line 1682 skipping to change at line 1760
performed if the Modify Response indicates successful completion of performed if the Modify Response indicates successful completion of
the Modify Operation. If the connection fails, whether the the Modify Operation. If the connection fails, whether the
modification occurred or not is indeterminate. modification occurred or not is indeterminate.
The Modify Operation cannot be used to remove from an entry any of The Modify Operation cannot be used to remove from an entry any of
its distinguished values, those values which form the entry's its distinguished values, those values which form the entry's
relative distinguished name. An attempt to do so will result in the relative distinguished name. An attempt to do so will result in the
server returning the error notAllowedOnRDN. The Modify DN Operation server returning the error notAllowedOnRDN. The Modify DN Operation
described in section 4.9 is used to rename an entry. described in section 4.9 is used to rename an entry.
Lightweight Directory Access Protocol Version 3
If an equality match filter has not been defined for an attribute If an equality match filter has not been defined for an attribute
type, clients MUST NOT attempt to add or delete individual values of type, clients MUST NOT attempt to add or delete individual values of
that attribute from an entry using the "add" or "delete" form of a that attribute from an entry using the "add" or "delete" form of a
modification, and MUST instead use the "replace" form. modification, and MUST instead use the "replace" form.
Note that due to the simplifications made in LDAP, there is not a Note that due to the simplifications made in LDAP, there is not a
direct mapping of the modifications in an LDAP ModifyRequest onto the direct mapping of the modifications in an LDAP ModifyRequest onto the
EntryModifications of a DAP ModifyEntry operation, and different EntryModifications of a DAP ModifyEntry operation, and different
implementations of LDAP-DAP gateways may use different means of implementations of LDAP-DAP gateways may use different means of
representing the change. If successful, the final effect of the representing the change. If successful, the final effect of the
operations on the entry MUST be identical. operations on the entry MUST be identical.
4.7. Add Operation 4.7. Add Operation
Sermersheim Internet-Draft - Expires July 2002 Page 31
Lightweight Directory Access Protocol Version 3
The Add Operation allows a client to request the addition of an entry The Add Operation allows a client to request the addition of an entry
into the directory. The Add Request is defined as follows: into the directory. The Add Request is defined as follows:
AddRequest ::= [APPLICATION 8] SEQUENCE { AddRequest ::= [APPLICATION 8] SEQUENCE {
entry LDAPDN, entry LDAPDN,
attributes AttributeList } attributes AttributeList }
AttributeList ::= SEQUENCE OF SEQUENCE { AttributeList ::= SEQUENCE OF SEQUENCE {
type AttributeDescription, type AttributeDescription,
vals SET OF AttributeValue } vals SET OF AttributeValue }
skipping to change at line 1737 skipping to change at line 1816
"C=US" entry did exist, then the server would return the error "C=US" entry did exist, then the server would return the error
noSuchObject with the matchedDN field containing "C=US". If the noSuchObject with the matchedDN field containing "C=US". If the
parent entry exists but is not in a naming context held by the parent entry exists but is not in a naming context held by the
server, the server SHOULD return a referral to the server holding the server, the server SHOULD return a referral to the server holding the
parent entry. parent entry.
Servers implementations SHOULD NOT restrict where entries can be Servers implementations SHOULD NOT restrict where entries can be
located in the directory. Some servers MAY allow the administrator to located in the directory. Some servers MAY allow the administrator to
restrict the classes of entries which can be added to the directory. restrict the classes of entries which can be added to the directory.
Lightweight Directory Access Protocol Version 3
Upon receipt of an Add Request, a server will attempt to perform the Upon receipt of an Add Request, a server will attempt to perform the
add requested. The result of the add attempt will be returned to the add requested. The result of the add attempt will be returned to the
client in the Add Response, defined as follows: client in the Add Response, defined as follows:
AddResponse ::= [APPLICATION 9] LDAPResult AddResponse ::= [APPLICATION 9] LDAPResult
A response of success indicates that the new entry is present in the A response of success indicates that the new entry is present in the
directory. directory.
4.8. Delete Operation 4.8. Delete Operation
The Delete Operation allows a client to request the removal of an The Delete Operation allows a client to request the removal of an
entry from the directory. The Delete Request is defined as follows: entry from the directory. The Delete Request is defined as follows:
DelRequest ::= [APPLICATION 10] LDAPDN DelRequest ::= [APPLICATION 10] LDAPDN
Sermersheim Internet-Draft - Expires July 2002 Page 32
Lightweight Directory Access Protocol Version 3
The Delete Request consists of the Distinguished Name of the entry to The Delete Request consists of the Distinguished Name of the entry to
be deleted. Note that the server will not dereference aliases while be deleted. Note that the server will not dereference aliases while
resolving the name of the target entry to be removed, and that only resolving the name of the target entry to be removed, and that only
leaf entries (those with no subordinate entries) can be deleted with leaf entries (those with no subordinate entries) can be deleted with
this operation. this operation.
The result of the delete attempted by the server upon receipt of a The result of the delete attempted by the server upon receipt of a
Delete Request is returned in the Delete Response, defined as Delete Request is returned in the Delete Response, defined as
follows: follows:
skipping to change at line 1794 skipping to change at line 1874
Parameters of the Modify DN Request are: Parameters of the Modify DN Request are:
- entry: the Distinguished Name of the entry to be changed. This - entry: the Distinguished Name of the entry to be changed. This
entry may or may not have subordinate entries. Note that the entry may or may not have subordinate entries. Note that the
server will not dereference any aliases in locating the entry to server will not dereference any aliases in locating the entry to
be changed. be changed.
- newrdn: the RDN that will form the leftmost component of the new - newrdn: the RDN that will form the leftmost component of the new
name of the entry. name of the entry.
Lightweight Directory Access Protocol Version 3
- deleteoldrdn: a boolean parameter that controls whether the old - deleteoldrdn: a boolean parameter that controls whether the old
RDN attribute values are to be retained as attributes of the RDN attribute values are to be retained as attributes of the
entry, or deleted from the entry. entry, or deleted from the entry.
- newSuperior: if present, this is the Distinguished Name of the - newSuperior: if present, this is the Distinguished Name of the
entry which becomes the immediate superior of the existing entry. entry which becomes the immediate superior of the existing entry.
The result of the name change attempted by the server upon receipt of The result of the name change attempted by the server upon receipt of
a Modify DN Request is returned in the Modify DN Response, defined as a Modify DN Request is returned in the Modify DN Response, defined as
follows: follows:
ModifyDNResponse ::= [APPLICATION 13] LDAPResult ModifyDNResponse ::= [APPLICATION 13] LDAPResult
Sermersheim Internet-Draft - Expires July 2002 Page 33
Lightweight Directory Access Protocol Version 3
Upon receipt of a ModifyDNRequest, a server will attempt to perform Upon receipt of a ModifyDNRequest, a server will attempt to perform
the name change. The result of the name change attempt will be the name change. The result of the name change attempt will be
returned to the client in the Modify DN Response. returned to the client in the Modify DN Response.
For example, if the entry named in the "entry" parameter was "cn=John For example, if the entry named in the "entry" parameter was "cn=John
Smith,c=US", the newrdn parameter was "cn=John Cougar Smith", and the Smith,c=US", the newrdn parameter was "cn=John Cougar Smith", and the
newSuperior parameter was absent, then this operation would attempt newSuperior parameter was absent, then this operation would attempt
to rename the entry to be "cn=John Cougar Smith,c=US". If there was to rename the entry to be "cn=John Cougar Smith,c=US". If there was
already an entry with that name, the operation would fail with error already an entry with that name, the operation would fail with error
code entryAlreadyExists. code entryAlreadyExists.
skipping to change at line 1850 skipping to change at line 1931
CompareRequest ::= [APPLICATION 14] SEQUENCE { CompareRequest ::= [APPLICATION 14] SEQUENCE {
entry LDAPDN, entry LDAPDN,
ava AttributeValueAssertion } ava AttributeValueAssertion }
Parameters of the Compare Request are: Parameters of the Compare Request are:
- entry: the name of the entry to be compared with. Note that the - entry: the name of the entry to be compared with. Note that the
server SHOULD NOT dereference any aliases in locating the entry to server SHOULD NOT dereference any aliases in locating the entry to
be compared with. be compared with.
Lightweight Directory Access Protocol Version 3
- ava: the assertion with which an attribute in the entry is to be - ava: the assertion with which an attribute in the entry is to be
compared. compared.
The result of the compare attempted by the server upon receipt of a The result of the compare attempted by the server upon receipt of a
Compare Request is returned in the Compare Response, defined as Compare Request is returned in the Compare Response, defined as
follows: follows:
CompareResponse ::= [APPLICATION 15] LDAPResult CompareResponse ::= [APPLICATION 15] LDAPResult
Upon receipt of a Compare Request, a server will attempt to perform Upon receipt of a Compare Request, a server will attempt to perform
the requested comparison. The result of the comparison will be the requested comparison. The result of the comparison will be
returned to the client in the Compare Response. Note that errors and returned to the client in the Compare Response. Note that errors and
the result of comparison are all returned in the same construct. the result of comparison are all returned in the same construct.
Sermersheim Internet-Draft - Expires July 2002 Page 34
Lightweight Directory Access Protocol Version 3
Note that some directory systems may establish access controls which Note that some directory systems may establish access controls which
permit the values of certain attributes (such as userPassword) to be permit the values of certain attributes (such as userPassword) to be
compared but not read. In a search result, it may be that an compared but not read. In a search result, it may be that an
attribute of that type would be returned, but with an empty set of attribute of that type would be returned, but with an empty set of
values. values.
4.11. Abandon Operation 4.11. Abandon Operation
The function of the Abandon Operation is to allow a client to request The function of the Abandon Operation is to allow a client to request
that the server abandon an outstanding operation. The Abandon Request that the server abandon an outstanding operation. The Abandon Request
skipping to change at line 1905 skipping to change at line 1987
Clients MUST NOT send abandon requests for the same operation Clients MUST NOT send abandon requests for the same operation
multiple times, and MUST also be prepared to receive results from multiple times, and MUST also be prepared to receive results from
operations it has abandoned (since these may have been in transit operations it has abandoned (since these may have been in transit
when the abandon was requested). when the abandon was requested).
Servers MUST discard abandon requests for message IDs they do not Servers MUST discard abandon requests for message IDs they do not
recognize, for operations which cannot be abandoned, and for recognize, for operations which cannot be abandoned, and for
operations which have already been abandoned. operations which have already been abandoned.
Lightweight Directory Access Protocol Version 3
4.12. Extended Operation 4.12. Extended Operation
An extension mechanism has been added in this version of LDAP, in An extension mechanism has been added in this version of LDAP, in
order to allow additional operations to be defined for services not order to allow additional operations to be defined for services not
available elsewhere in this protocol, for instance digitally signed available elsewhere in this protocol, for instance digitally signed
operations and results. operations and results.
The extended operation allows clients to make requests and receive The extended operation allows clients to make requests and receive
responses with predefined syntaxes and semantics. These may be responses with predefined syntaxes and semantics. These may be
defined in RFCs or be private to particular implementations. Each defined in RFCs or be private to particular implementations. Each
request MUST have a unique OBJECT IDENTIFIER assigned to it. request MUST have a unique OBJECT IDENTIFIER assigned to it.
ExtendedRequest ::= [APPLICATION 23] SEQUENCE { ExtendedRequest ::= [APPLICATION 23] SEQUENCE {
requestName [0] LDAPOID, requestName [0] LDAPOID,
Sermersheim Internet-Draft - Expires July 2002 Page 35
Lightweight Directory Access Protocol Version 3
requestValue [1] OCTET STRING OPTIONAL } requestValue [1] OCTET STRING OPTIONAL }
The requestName is a dotted-decimal representation of the OBJECT The requestName is a dotted-decimal representation of the OBJECT
IDENTIFIER corresponding to the request. The requestValue is IDENTIFIER corresponding to the request. The requestValue is
information in a form defined by that request, encapsulated inside an information in a form defined by that request, encapsulated inside an
OCTET STRING. OCTET STRING.
The server will respond to this with an LDAPMessage containing the The server will respond to this with an LDAPMessage containing the
ExtendedResponse. ExtendedResponse.
skipping to change at line 1960 skipping to change at line 2044
following additional restrictions are placed on BER-encodings of LDAP following additional restrictions are placed on BER-encodings of LDAP
protocol elements: protocol elements:
(1) Only the definite form of length encoding will be used. (1) Only the definite form of length encoding will be used.
(2) OCTET STRING values will be encoded in the primitive form only. (2) OCTET STRING values will be encoded in the primitive form only.
(3) If the value of a BOOLEAN type is true, the encoding MUST have (3) If the value of a BOOLEAN type is true, the encoding MUST have
its contents octets set to hex "FF". its contents octets set to hex "FF".
Lightweight Directory Access Protocol Version 3
(4) If a value of a type is its default value, it MUST be absent. (4) If a value of a type is its default value, it MUST be absent.
Only some BOOLEAN and INTEGER types have default values in this Only some BOOLEAN and INTEGER types have default values in this
protocol definition. protocol definition.
These restrictions do not apply to ASN.1 types encapsulated inside of These restrictions do not apply to ASN.1 types encapsulated inside of
OCTET STRING values, such as attribute values, unless otherwise OCTET STRING values, such as attribute values, unless otherwise
noted. noted.
5.2. Transfer Protocols 5.2. Transfer Protocols
This protocol is designed to run over connection-oriented, reliable This protocol is designed to run over connection-oriented, reliable
transports, with all 8 bits in an octet being significant in the data transports, with all 8 bits in an octet being significant in the data
stream. stream.
5.2.1. Transmission Control Protocol (TCP) 5.2.1. Transmission Control Protocol (TCP)
Sermersheim Internet-Draft - Expires July 2002 Page 36
Lightweight Directory Access Protocol Version 3
The encoded LDAPMessage PDUs are mapped directly onto the TCP The encoded LDAPMessage PDUs are mapped directly onto the TCP
bytestream. It is recommended that server implementations running bytestream. It is recommended that server implementations running
over the TCP MAY provide a protocol listener on the assigned port, over the TCP MAY provide a protocol listener on the assigned port,
389. Servers may instead provide a listener on a different port 389. Servers may instead provide a listener on a different port
number. Clients MUST support contacting servers on any valid TCP number. Clients MUST support contacting servers on any valid TCP
port. port.
6. Implementation Guidelines 6. Implementation Guidelines
This document describes an Internet protocol. This document describes an Internet protocol.
skipping to change at line 2016 skipping to change at line 2101
assume that servers support any particular schemas beyond those assume that servers support any particular schemas beyond those
referenced in section 6.1. Different schemas can have different referenced in section 6.1. Different schemas can have different
attribute types with the same names. The client can retrieve the attribute types with the same names. The client can retrieve the
subschema entries referenced by the subschemaSubentry attribute in subschema entries referenced by the subschemaSubentry attribute in
the server's root DSE or in entries held by the server. the server's root DSE or in entries held by the server.
7. Security Considerations 7. Security Considerations
When used with a connection-oriented transport, this version of the When used with a connection-oriented transport, this version of the
protocol provides facilities for the LDAP v2 authentication protocol provides facilities for the LDAP v2 authentication
Lightweight Directory Access Protocol Version 3
mechanism, simple authentication using a cleartext password, as well mechanism, simple authentication using a cleartext password, as well
as any SASL mechanism [RFC2222]. SASL allows for integrity and as any SASL mechanism [RFC2222]. SASL allows for integrity and
privacy services to be negotiated. privacy services to be negotiated.
It is also permitted that the server can return its credentials to It is also permitted that the server can return its credentials to
the client, if it chooses to do so. the client, if it chooses to do so.
Use of cleartext password is strongly discouraged where the Use of cleartext password is 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.
When used with SASL, it should be noted that the name field of the When used with SASL, it should be noted that the name field of the
BindRequest is not protected against modification. Thus if the BindRequest is not protected against modification. Thus if the
distinguished name of the client (an LDAPDN) is agreed through the distinguished name of the client (an LDAPDN) is agreed through the
Sermersheim Internet-Draft - Expires July 2002 Page 37
Lightweight Directory Access Protocol Version 3
negotiation of the credentials, it takes precedence over any value in negotiation of the credentials, it takes precedence over any value in
the unprotected name field. the unprotected name field.
Implementations which cache attributes and entries obtained via LDAP Implementations which cache attributes and entries obtained via LDAP
MUST ensure that access controls are maintained if that information MUST ensure that access controls are maintained if that information
is to be provided to multiple clients, since servers may have access is to be provided to multiple clients, since servers may have access
control policies which prevent the return of entries or attributes in control policies which prevent the return of entries or attributes in
search results except to particular authenticated clients. For search results except to particular authenticated clients. For
example, caches could serve result information only to the client example, caches could serve result information only to the client
whose request caused it to be in the cache. whose request caused it to be in the cache.
skipping to change at line 2074 skipping to change at line 2160
[X.680] ITU-T Rec. X.680, "Abstract Syntax Notation One (ASN.1) - [X.680] ITU-T Rec. X.680, "Abstract Syntax Notation One (ASN.1) -
Specification of Basic Notation", 1994. Specification of Basic Notation", 1994.
[X.690] ITU-T Rec. X.690, "Specification of ASN.1 encoding rules: [X.690] ITU-T Rec. X.690, "Specification of ASN.1 encoding rules:
Basic, Canonical, and Distinguished Encoding Rules", 1994. Basic, Canonical, and Distinguished Encoding Rules", 1994.
[RFC1777] Yeong, W., Howes, T., and S. Kille, "Lightweight Directory [RFC1777] Yeong, W., Howes, T., and S. Kille, "Lightweight Directory
Access Protocol", RFC 1777, March 1995. Access Protocol", RFC 1777, March 1995.
Lightweight Directory Access Protocol Version 3
[RFC1823] Howes, T., and M. Smith, "The LDAP Application Program [RFC1823] Howes, T., and M. Smith, "The LDAP Application Program
Interface", RFC 1823, August 1995. Interface", RFC 1823, August 1995.
[RFC2044] Yergeau, F., "UTF-8, a transformation format of Unicode [RFC2044] Yergeau, F., "UTF-8, a transformation format of Unicode
and ISO 10646", RFC 2044, October 1996. and ISO 10646", RFC 2044, October 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997. Requirement Levels", RFC 2119, March 1997.
[RFC2222] Meyers, J., "Simple Authentication and Security Layer", [RFC2222] Meyers, J., "Simple Authentication and Security Layer",
RFC 2222, October 1997. RFC 2222, October 1997.
Sermersheim Internet-Draft - Expires July 2002 Page 38
Lightweight Directory Access Protocol Version 3
[RFC2234] Crocker, D., and P. Overell, "Augmented BNF for Syntax [RFC2234] Crocker, D., and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997. Specifications: ABNF", RFC 2234, November 1997.
[RFC2252] Wahl, M., Coulbeck, A., Howes, T., and S. Kille, [RFC2252] Wahl, M., Coulbeck, A., Howes, T., and S. Kille,
"Lightweight Directory Access Protocol (v3): Attribute "Lightweight Directory Access Protocol (v3): Attribute
Syntax Definitions", RFC 2252, December 1997. Syntax Definitions", RFC 2252, December 1997.
[RFC2253] Kille, S., Wahl, M., and T. Howes, "Lightweight Directory [RFC2253] Kille, S., Wahl, M., and T. Howes, "Lightweight Directory
Access Protocol (v3): UTF-8 String Representation of Access Protocol (v3): UTF-8 String Representation of
Distinguished Names", RFC 2253, December 1997. Distinguished Names", RFC 2253, December 1997.
skipping to change at line 2122 skipping to change at line 2209
10. Editor's Address 10. Editor's Address
Jim Sermersheim Jim Sermersheim
Novell, Inc. Novell, Inc.
1800 South Novell Place 1800 South Novell Place
Provo, Utah 84606, USA Provo, Utah 84606, USA
jimse@novell.com jimse@novell.com
+1 801 861-3088 +1 801 861-3088
Sermersheim Internet-Draft - Expires July 2002 Page 39
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
Appendix A - Complete ASN.1 Definition Appendix A - Complete ASN.1 Definition
Lightweight-Directory-Access-Protocol-V3 DEFINITIONS Lightweight-Directory-Access-Protocol-V3 DEFINITIONS
IMPLICIT TAGS ::= IMPLICIT TAGS ::=
BEGIN BEGIN
LDAPMessage ::= SEQUENCE { LDAPMessage ::= SEQUENCE {
skipping to change at line 2179 skipping to change at line 2267
AttributeDescription ::= LDAPString AttributeDescription ::= LDAPString
AttributeDescriptionList ::= SEQUENCE OF AttributeDescriptionList ::= SEQUENCE OF
AttributeDescription AttributeDescription
AttributeValue ::= OCTET STRING AttributeValue ::= OCTET STRING
AttributeValueAssertion ::= SEQUENCE { AttributeValueAssertion ::= SEQUENCE {
Sermersheim Internet-Draft - Expires July 2002 Page 40
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
attributeDesc AttributeDescription, attributeDesc AttributeDescription,
assertionValue AssertionValue } assertionValue AssertionValue }
AssertionValue ::= OCTET STRING AssertionValue ::= OCTET STRING
Attribute ::= SEQUENCE { Attribute ::= SEQUENCE {
type AttributeDescription, type AttributeDescription,
vals SET OF AttributeValue } vals SET OF AttributeValue }
skipping to change at line 2236 skipping to change at line 2325
unavailable (52), unavailable (52),
unwillingToPerform (53), unwillingToPerform (53),
loopDetect (54), loopDetect (54),
-- 55-63 unused -- -- 55-63 unused --
namingViolation (64), namingViolation (64),
objectClassViolation (65), objectClassViolation (65),
notAllowedOnNonLeaf (66), notAllowedOnNonLeaf (66),
notAllowedOnRDN (67), notAllowedOnRDN (67),
entryAlreadyExists (68), entryAlreadyExists (68),
Sermersheim Internet-Draft - Expires July 2002 Page 41
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
objectClassModsProhibited (69), objectClassModsProhibited (69),
-- 70 reserved for CLDAP -- -- 70 reserved for CLDAP --
affectsMultipleDSAs (71), affectsMultipleDSAs (71),
-- 72-79 unused -- -- 72-79 unused --
other (80) }, other (80) },
-- 81-90 reserved for APIs -- -- 81-90 reserved for APIs --
matchedDN LDAPDN, matchedDN LDAPDN,
errorMessage LDAPString, errorMessage LDAPString,
skipping to change at line 2293 skipping to change at line 2383
baseObject (0), baseObject (0),
singleLevel (1), singleLevel (1),
wholeSubtree (2) }, wholeSubtree (2) },
derefAliases ENUMERATED { derefAliases ENUMERATED {
neverDerefAliases (0), neverDerefAliases (0),
derefInSearching (1), derefInSearching (1),
derefFindingBaseObj (2), derefFindingBaseObj (2),
derefAlways (3) }, derefAlways (3) },
sizeLimit INTEGER (0 .. maxInt), sizeLimit INTEGER (0 .. maxInt),
Sermersheim Internet-Draft - Expires July 2002 Page 42
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
timeLimit INTEGER (0 .. maxInt), timeLimit INTEGER (0 .. maxInt),
typesOnly BOOLEAN, typesOnly BOOLEAN,
filter Filter, filter Filter,
attributes AttributeDescriptionList } attributes AttributeDescriptionList }
Filter ::= CHOICE { Filter ::= CHOICE {
and [0] SET SIZE (1..MAX) OF Filter, and [0] SET SIZE (1..MAX) OF Filter,
or [1] SET SIZE (1..MAX) OF Filter, or [1] SET SIZE (1..MAX) OF Filter,
skipping to change at line 2350 skipping to change at line 2441
object LDAPDN, object LDAPDN,
modification SEQUENCE OF SEQUENCE { modification SEQUENCE OF SEQUENCE {
operation ENUMERATED { operation ENUMERATED {
add (0), add (0),
delete (1), delete (1),
replace (2) }, replace (2) },
modification AttributeTypeAndValues } } modification AttributeTypeAndValues } }
AttributeTypeAndValues ::= SEQUENCE { AttributeTypeAndValues ::= SEQUENCE {
Sermersheim Internet-Draft - Expires July 2002 Page 43
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
type AttributeDescription, type AttributeDescription,
vals SET OF AttributeValue } vals SET OF AttributeValue }
ModifyResponse ::= [APPLICATION 7] LDAPResult ModifyResponse ::= [APPLICATION 7] LDAPResult
AddRequest ::= [APPLICATION 8] SEQUENCE { AddRequest ::= [APPLICATION 8] SEQUENCE {
entry LDAPDN, entry LDAPDN,
attributes AttributeList } attributes AttributeList }
skipping to change at line 2398 skipping to change at line 2490
requestName [0] LDAPOID, requestName [0] LDAPOID,
requestValue [1] OCTET STRING OPTIONAL } requestValue [1] OCTET STRING OPTIONAL }
ExtendedResponse ::= [APPLICATION 24] SEQUENCE { ExtendedResponse ::= [APPLICATION 24] SEQUENCE {
COMPONENTS OF LDAPResult, COMPONENTS OF LDAPResult,
responseName [10] LDAPOID OPTIONAL, responseName [10] LDAPOID OPTIONAL,
response [11] OCTET STRING OPTIONAL } response [11] OCTET STRING OPTIONAL }
END END
Sermersheim Internet-Draft - Expires July 2002 Page 44
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
Appendix B - Change History Appendix B - Change History
B.1 Changes made to RFC 2251: B.1 Changes made to RFC 2251:
B.1.1 Editorial B.1.1 Editorial
- Bibliography References: Changed all bibliography references to - Bibliography References: Changed all bibliography references to
use a long name form for readability. use a long name form for readability.
skipping to change at line 2454 skipping to change at line 2547
Previously, only the ;binary option was mentioned. Previously, only the ;binary option was mentioned.
B.2.3 Sections 4.2, 4.9, 4.10 B.2.3 Sections 4.2, 4.9, 4.10
- Added alias dereferencing specifications. In the case of modDN, - Added alias dereferencing specifications. In the case of modDN,
followed precedent set on other update operations (... alias is followed precedent set on other update operations (... alias is
not dereferenced...) In the case of bind and compare stated that not dereferenced...) In the case of bind and compare stated that
servers SHOULD NOT dereference aliases. Specifications were added servers SHOULD NOT dereference aliases. Specifications were added
because they were missing from the previous version and caused because they were missing from the previous version and caused
Sermersheim Internet-Draft - Expires July 2002 Page 45
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
interoperability problems. Concessions were made for bind and interoperability problems. Concessions were made for bind and
compare (neither should have ever allowed alias dereferencing) by compare (neither should have ever allowed alias dereferencing) by
using SHOULD NOT language, due to the behavior of some existing using SHOULD NOT language, due to the behavior of some existing
implementations. implementations.
B.2.4 Sections 4.5 and Appendix A B.2.4 Sections 4.5 and Appendix A
- Changed SubstringFilter.substrings.initial, any, and all from - Changed SubstringFilter.substrings.initial, any, and all from
skipping to change at line 2509 skipping to change at line 2603
B.3.6 Section 4.5.2 B.3.6 Section 4.5.2
- Removed all mention of ExtendedResponse due to lack of - Removed all mention of ExtendedResponse due to lack of
implementation. implementation.
B.4 Changes made to draft-ietf-ldapbis-protocol-02.txt: B.4 Changes made to draft-ietf-ldapbis-protocol-02.txt:
B.4.1 Section 4 B.4.1 Section 4
Sermersheim Internet-Draft - Expires July 2002 Page 46
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
- Removed "typically" from "and is typically transferred" in the - Removed "typically" from "and is typically transferred" in the
first paragraph. We know of no (and can conceive of no) case where first paragraph. We know of no (and can conceive of no) case where
this isn't true. this isn't true.
- Added "Section 5.1 specifies how the LDAP protocol is encoded." To - Added "Section 5.1 specifies how the LDAP protocol is encoded." To
the first paragraph. Added this cross reference for readability. the first paragraph. Added this cross reference for readability.
- Changed "version 3 " to "version 3 or later" in the second - Changed "version 3 " to "version 3 or later" in the second
paragraph. This was added to clarify the original intent. paragraph. This was added to clarify the original intent.
- Changed "protocol version" to "protocol versions" in the third - Changed "protocol version" to "protocol versions" in the third
skipping to change at line 2566 skipping to change at line 2661
- Changed "One unsolicited notification is defined" to "One - Changed "One unsolicited notification is defined" to "One
unsolicited notification (Notice of Disconnection) is defined" in unsolicited notification (Notice of Disconnection) is defined" in
the third paragraph. For clarity and readability. the third paragraph. For clarity and readability.
B.4.7 Section 4.5.1 B.4.7 Section 4.5.1
- Changed "checking for the existence of the objectClass attribute" - Changed "checking for the existence of the objectClass attribute"
to "checking for the presence of the objectClass attribute" in the to "checking for the presence of the objectClass attribute" in the
last paragraph. This was done as a measure of consistency (we use last paragraph. This was done as a measure of consistency (we use
Sermersheim Internet-Draft - Expires July 2002 Page 47
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
the terms present and presence rather than exists and existence in the terms present and presence rather than exists and existence in
search filters). search filters).
B.4.8 Section 4.5.3 B.4.8 Section 4.5.3
- Changed "outstanding search operations to different servers," to - Changed "outstanding search operations to different servers," to
"outstanding search operations" in the fifth paragraph as they may "outstanding search operations" in the fifth paragraph as they may
be to the same server. This is a point of clarification. be to the same server. This is a point of clarification.
skipping to change at line 2622 skipping to change at line 2718
description (a type and zero or more options) with one or more description (a type and zero or more options) with one or more
associated values. The attribute type governs whether the associated values. The attribute type governs whether the
attribute can have multiple values, the syntax and matching rules attribute can have multiple values, the syntax and matching rules
used to construct and compare values of that attribute, and other used to construct and compare values of that attribute, and other
functions. Options indicate modes of transfer and other functions. Options indicate modes of transfer and other
functions.". This points out that an attribute consists of both functions.". This points out that an attribute consists of both
the type and options. the type and options.
B.5.2 Section 4 B.5.2 Section 4
Sermersheim Internet-Draft - Expires July 2002 Page 48
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
- Changed "Section 5.1 specifies the encoding rules for the LDAP - Changed "Section 5.1 specifies the encoding rules for the LDAP
protocol" to "Section 5.1 specifies how the protocol is encoded protocol" to "Section 5.1 specifies how the protocol is encoded
and transferred." and transferred."
B.5.3 Section 4.1.2 B.5.3 Section 4.1.2
- Added ABNF for the textual representation of LDAPOID. Previously, - Added ABNF for the textual representation of LDAPOID. Previously,
there was no formal BNF for this construct. there was no formal BNF for this construct.
skipping to change at line 2678 skipping to change at line 2775
that is, that any of the referrals may be used to progress the that is, that any of the referrals may be used to progress the
operation, there is no inherent 'weighting' mechanism. operation, there is no inherent 'weighting' mechanism.
B.5.7 Section 4.5.1 and Appendix A B.5.7 Section 4.5.1 and Appendix A
- Added the comment "-- initial and final can occur at most once", - Added the comment "-- initial and final can occur at most once",
to clarify this restriction. to clarify this restriction.
B.5.8 Section 5.1 B.5.8 Section 5.1
Sermersheim Internet-Draft - Expires July 2002 Page 49
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
- Changed heading from "Mapping Onto BER-based Transport Services" - Changed heading from "Mapping Onto BER-based Transport Services"
to "Protocol Encoding". to "Protocol Encoding".
B.5.9 Section 5.2.1 B.5.9 Section 5.2.1
- Changed "The LDAPMessage PDUs" to "The encoded LDAPMessage PDUs" - Changed "The LDAPMessage PDUs" to "The encoded LDAPMessage PDUs"
to point out that the PDUs are encoded before being streamed to to point out that the PDUs are encoded before being streamed to
TCP. TCP.
B.6 Changes made to draft-ietf-ldapbis-protocol-03.txt: B.6 Changes made to draft-ietf-ldapbis-protocol-04.txt:
B.6.1 Section 4.5.1 and Appendix A B.6.1 Section 4.5.1 and Appendix A
- Changed the ASN.1 for the and and or choices of Filter to have a - Changed the ASN.1 for the and and or choices of Filter to have a
lower range of 1. This was an omission in the original ASN.1 lower range of 1. This was an omission in the original ASN.1
B.6.2 Various B.6.2 Various
- Fixed various typo's - Fixed various typo's
B.7 Changes made to draft-ietf-ldapbis-protocol-05.txt:
B.7.1 Section 3.2.1
- Added "(as defined in Section 12.4.1 of [X.501])" to the fifth
paragraph when talking about "operational attributes". This is
because the term "operational attributes" is never defined.
Alternately, we could drag a definition into the spec, for now,
I'm just pointing to the reference in X.501.
B.7.2 Section 4.1.5
- Changed "And is also case insensitive" to "The entire
AttributeDescription is case insensitive". This is to clarify
whether we're talking about the entire attribute description, or
just the options.
- Expounded on the definition of attribute description options. This
doc now specifies a difference between transfer and tagging
options and describes the semantics of each, and how and when
subtyping rules apply. Now allow options to be transmitted in any
order but disallow any ordering semantics to be implied. These
changes are the result of ongoing input from an engineering team
designed to deal with ambiguity issues surrounding attribute
options.
B.7.3 Sections 4.1.5.1 and 4.1.6
- Refer to non "binary" transfer encodings as "native encoding"
rather than "string" encoding to clarify and avoid confusion.
Appendix C - Outstanding Work Items Appendix C - Outstanding Work Items
Sermersheim Internet-Draft - Expires July 2002 Page 50
Lightweight Directory Access Protocol Version 3
C.1 Integrate result codes draft. C.1 Integrate result codes draft.
- The result codes draft should be reconciled with this draft. - The result codes draft should be reconciled with this draft.
Operation-specific instructions will reside with operations while Operation-specific instructions will reside with operations while
the error-specific sections will be added as an appendix. the error-specific sections will be added as an appendix.
C.2 Section 3.1 C.2 Section 3.1
- Add "This also increases the complexity of clients in this - Add "This also increases the complexity of clients in this
version." to fourth paragraph. version." to fourth paragraph.
skipping to change at line 2733 skipping to change at line 2865
- Change "the client may discard the PDU, or may abruptly close the - Change "the client may discard the PDU, or may abruptly close the
connection." to "the client MAY discard the PDU, or MAY abruptly connection." to "the client MAY discard the PDU, or MAY abruptly
close the connection." in the fourth paragraph. close the connection." in the fourth paragraph.
C.5 Section 4.1.1.1 C.5 Section 4.1.1.1
- Add "If an unsolicited notification as described in section 4.4 is - Add "If an unsolicited notification as described in section 4.4 is
sent from a server, the messageID value MUST be zero." to first sent from a server, the messageID value MUST be zero." to first
paragraph. paragraph.
Lightweight Directory Access Protocol Version 3
- Change "MUST have a value different" to "MUST have a non-zero - Change "MUST have a value different" to "MUST have a non-zero
value different" in the second paragraph. value different" in the second paragraph.
- Remove "or of the abandoned operation until it has received a - Remove "or of the abandoned operation until it has received a
response from the server for another request invoked subsequent to response from the server for another request invoked subsequent to
the abandonRequest," from the fourth paragraph as this imposes the abandonRequest," from the fourth paragraph as this imposes
synchronous behavior on the server. synchronous behavior on the server.
C.7 Section 4.1.4 C.7 Section 4.1.4
- Add "Note that due to the restriction above, and due to this - Add "Note that due to the restriction above, and due to this
skipping to change at line 2758 skipping to change at line 2887
paragraph. paragraph.
- Resolve issue on list with the subject "Attribute Type character - Resolve issue on list with the subject "Attribute Type character
set". set".
C.8 Section 4.1.5 C.8 Section 4.1.5
- Change "A server may treat" to "A server MUST treat" in the second - Change "A server may treat" to "A server MUST treat" in the second
to last paragraph. to last paragraph.
- Change "A server MUST treat an AttributeDescription with any - Change "A server MUST treat an AttributeDescription with any
options it does not implement as an unrecognized attribute type." options it does not implement as an unrecognized attribute type."
Sermersheim Internet-Draft - Expires July 2002 Page 51
Lightweight Directory Access Protocol Version 3
to "A server MUST treat an AttributeDescription with any options to "A server MUST treat an AttributeDescription with any options
it does not implement or support as an unrecognized attribute it does not implement or support as an unrecognized attribute
type." in the second to last paragraph. type." in the second to last paragraph.
- Clarify the statement "An AttributeDescription with one or more - Clarify the statement "An AttributeDescription with one or more
options is treated as a subtype of the attribute type without any options is treated as a subtype of the attribute type without any
options". There is an unresolved thread titles "RFC 2596 options". There is an unresolved thread titles "RFC 2596
questions" on the ietf-ldapext list regarding this. questions" on the ietf-ldapext list regarding this.
C.9 Section 4.1.5.1 C.9 Section 4.1.5.1
skipping to change at line 2789 skipping to change at line 2922
C.11 Section 4.1.7 C.11 Section 4.1.7
- Change "For all the string-valued user attributes described in - Change "For all the string-valued user attributes described in
[5], the assertion value syntax is the same as the value syntax." [5], the assertion value syntax is the same as the value syntax."
to "The assertion value syntax for all attributes using human- to "The assertion value syntax for all attributes using human-
readable syntaxes as described in [RFC2252] is the same as the readable syntaxes as described in [RFC2252] is the same as the
value syntax unless otherwise noted (an example being value syntax unless otherwise noted (an example being
objectIdentifierFirstComponentMatch)." in the third paragraph. objectIdentifierFirstComponentMatch)." in the third paragraph.
- Find out what the last sentence in third paragraph means (Clients - Find out what the last sentence in third paragraph means (Clients
may use attributes...) may use attributes...)
Lightweight Directory Access Protocol Version 3
- Add a fourth paragraph: "Servers SHOULD NOT generate codes 81-90 - Add a fourth paragraph: "Servers SHOULD NOT generate codes 81-90
as these are reserved for use by historical APIs [RFC 1823]. as these are reserved for use by historical APIs [RFC 1823]. Later
Later API specifications SHOULD avoid using the resultCode API specifications SHOULD avoid using the resultCode enumeration
enumeration to represent anything other than a protocol result to represent anything other than a protocol result indication."
indication."
C.13 Section 4.1.11 C.13 Section 4.1.11
- Add "after locating the target entry" to the first paragraph. - Add "after locating the target entry" to the first paragraph.
C.14 Section 4.1.12 C.14 Section 4.1.12
- Specify whether or not servers are to advertise the OIDs of known - Specify whether or not servers are to advertise the OIDs of known
response controls. response controls.
C.15 Section 4.2 C.15 Section 4.2
- Change "LDAPDN" to "identity" in the definition of the name field. - Change "LDAPDN" to "identity" in the definition of the name field.
- Rework definition of the name field to enumerate empty password and - Rework definition of the name field to enumerate empty password and
name combinations. <Needs more work following discussion on list> name combinations. <Needs more work following discussion on list>
C.17 Section 4.2.2 C.17 Section 4.2.2
- Add "as the authentication identity" to second paragraph. - Add "as the authentication identity" to second paragraph.
Sermersheim Internet-Draft - Expires July 2002 Page 52
Lightweight Directory Access Protocol Version 3
C.18 Section 4.2.3 C.18 Section 4.2.3
- Change "If the bind was successful, the resultCode will be - Change "If the bind was successful, the resultCode will be
success, otherwise it will be one of" to "If the bind was success, otherwise it will be one of" to "If the bind was
successful, the resultCode will be success, otherwise it MAY be successful, the resultCode will be success, otherwise it MAY be
one of" in the third paragraph. <May need further refinement when one of" in the third paragraph. <May need further refinement when
reconciled with resultCode draft>. reconciled with resultCode draft>.
- Change "operationsError" to "other" as a result code. - Change "operationsError" to "other" as a result code.
- Change "If the client bound with the password choice" to "If the - Change "If the client bound with the password choice" to "If the
client bound with the simple choice" in the last paragraph. client bound with the simple choice" in the last paragraph.
skipping to change at line 2845 skipping to change at line 2977
assume" in the second paragraph. assume" in the second paragraph.
- Change "and may close the connection" to "and MUST close the - Change "and may close the connection" to "and MUST close the
connection" in the second paragraph. connection" in the second paragraph.
C.20 Section 4.4 C.20 Section 4.4
- Add "Servers SHOULD NOT assume LDAPv3 clients understand or - Add "Servers SHOULD NOT assume LDAPv3 clients understand or
recognize unsolicited notifications or unsolicited controls other recognize unsolicited notifications or unsolicited controls other
than Notice of Disconnection defined below. Servers SHOULD avoid than Notice of Disconnection defined below. Servers SHOULD avoid
sending unsolicited notifications unless they know (by related sending unsolicited notifications unless they know (by related
Lightweight Directory Access Protocol Version 3
request or other means) that the client can make use of the request or other means) that the client can make use of the
notification." as a fourth paragraph. notification." as a fourth paragraph.
C.21 Section 4.5.1 C.21 Section 4.5.1
- Make sure the use of "subordinates" in the derefInSearching - Make sure the use of "subordinates" in the derefInSearching
definition is correct. See "derefInSearching" on list. definition is correct. See "derefInSearching" on list.
C.22 Section 4.5.2 C.22 Section 4.5.2
skipping to change at line 2873 skipping to change at line 3002
- Add "Similarly, a server MUST NOT return a SearchResultReference - Add "Similarly, a server MUST NOT return a SearchResultReference
when the scope of the search is baseObject. If a client receives when the scope of the search is baseObject. If a client receives
such a SearchResultReference it MUST interpret is as a protocol such a SearchResultReference it MUST interpret is as a protocol
error and MUST NOT follow it." to the first paragraph. error and MUST NOT follow it." to the first paragraph.
- Add "If the scope part of the LDAP URL is present, the client MUST - Add "If the scope part of the LDAP URL is present, the client MUST
use the new scope in its next request to progress the search. If use the new scope in its next request to progress the search. If
the scope part is absent the client MUST use subtree scope to the scope part is absent the client MUST use subtree scope to
complete subtree searches and base scope to complete one level complete subtree searches and base scope to complete one level
searches." to the third paragraph. searches." to the third paragraph.
Sermersheim Internet-Draft - Expires July 2002 Page 53
Lightweight Directory Access Protocol Version 3
C.24 Section 4.5.3.1 C.24 Section 4.5.3.1
- Change examples to use dc naming. - Change examples to use dc naming.
C.25 Section 4.6 C.25 Section 4.6
- Resolve the meaning of "and is ignored if the attribute does not - Resolve the meaning of "and is ignored if the attribute does not
exist". See "modify: "non-existent attribute"" on the list. exist". See "modify: "non-existent attribute"" on the list.
C.26 Section 4.7 C.26 Section 4.7
skipping to change at line 2901 skipping to change at line 3033
schema. Also what happens if there's no equality matching rule. schema. Also what happens if there's no equality matching rule.
C.28 Section 4.11 C.28 Section 4.11
- Change "(since these may have been in transit when the abandon was - Change "(since these may have been in transit when the abandon was
requested)." to "(since these may either have been in transit when requested)." to "(since these may either have been in transit when
the abandon was requested, or are not able to be abandoned)." in the abandon was requested, or are not able to be abandoned)." in
the fifth paragraph. the fifth paragraph.
- Add "Abandon and Unbind operations are not able to be abandoned. - Add "Abandon and Unbind operations are not able to be abandoned.
Other operations, in particular update operations, or operations Other operations, in particular update operations, or operations
Lightweight Directory Access Protocol Version 3
that have been chained, may not be abandonable (or immediately that have been chained, may not be abandonable (or immediately
abandonable)." as the sixth paragraph. abandonable)." as the sixth paragraph.
C.29 Section 4.12 C.29 Section 4.12
- Change "digitally signed operations and results" to "for instance - Change "digitally signed operations and results" to "for instance
StartTLS [RFC2830]" StartTLS [RFC2830]"
C.30 Section 5.1 C.30 Section 5.1
skipping to change at line 2931 skipping to change at line 3060
C.32 Section 6.1 C.32 Section 6.1
- Add "that are used by those attributes" to the first paragraph. - Add "that are used by those attributes" to the first paragraph.
- Add "Servers which support update operations MUST, and other - Add "Servers which support update operations MUST, and other
servers SHOULD, support strong authentication mechanisms described servers SHOULD, support strong authentication mechanisms described
in [RFC2829]." as a second paragraph. in [RFC2829]." as a second paragraph.
- Add "Servers which provide access to sensitive information MUST, - Add "Servers which provide access to sensitive information MUST,
and other servers SHOULD support privacy protections such as those and other servers SHOULD support privacy protections such as those
described in [RFC2829] and [RFC2830]." as a third paragraph. described in [RFC2829] and [RFC2830]." as a third paragraph.
Sermersheim Internet-Draft - Expires July 2002 Page 54
Lightweight Directory Access Protocol Version 3
C.33 Section 7 C.33 Section 7
- Add "Servers which support update operations MUST, and other - Add "Servers which support update operations MUST, and other
servers SHOULD, support strong authentication mechanisms described servers SHOULD, support strong authentication mechanisms described
in [RFC2829]." as a fourth paragraph. in [RFC2829]." as a fourth paragraph.
- Add "In order to automatically follow referrals, clients may need - Add "In order to automatically follow referrals, clients may need
to hold authentication secrets. This poses significant privacy and to hold authentication secrets. This poses significant privacy and
security concerns and SHOULD be avoided." as a sixth paragraph. security concerns and SHOULD be avoided." as a sixth paragraph.
- Add "This document provides a mechanism which clients may use to - Add "This document provides a mechanism which clients may use to
discover operational attributes. Those relying on security by discover operational attributes. Those relying on security by
obscurity should implement appropriate access controls to obscurity should implement appropriate access controls to
restricts access to operational attributes per local policy." as restricts access to operational attributes per local policy." as
an eighth paragraph. an eighth paragraph.
- Add "This document provides a mechanism which clients may use to - Add "This document provides a mechanism which clients may use to
discover operational attributes. Those relying on security by discover operational attributes. Those relying on security by
obscurity should implement appropriate access controls to obscurity should implement appropriate access controls to
restricts access to operational attributes per local policy." as restricts access to operational attributes per local policy." as
an eighth paragraph. an eighth paragraph.
Sermersheim Internet-Draft - Expires July 2002 Page 55
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/