draft-ietf-ldapbis-protocol-25.txt   draft-ietf-ldapbis-protocol-26.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-25.txt July 2004 Document: draft-ietf-ldapbis-protocol-26.txt Aug 2004
Obsoletes: RFCs 2251, 2830, 3771 Obsoletes: RFCs 2251, 2830, 3771
LDAP: The Protocol LDAP: The Protocol
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is subject to all provisions
all provisions of Section 10 of RFC2026. of section 3 of RFC 3667. By submitting this Internet-Draft, each
author represents that any applicable patent or other IPR claims of
which he or she is aware have been or will be disclosed, and any of
which he or she become aware will be disclosed, in accordance with
RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that
groups may also distribute working documents as Internet-Drafts. other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Distribution of this memo is unlimited. Technical discussion of this Technical discussion of this document will take place on the IETF
document will take place on the IETF LDAP Revision Working Group LDAP Revision Working Group (LDAPbis) mailing list <ietf-
(LDAPbis) mailing list <ietf-ldapbis@openldap.org>. Please send ldapbis@openldap.org>. Please send editorial comments directly to the
editorial comments directly to the editor <jimse@novell.com>. editor <jimse@novell.com>.
Copyright Notice
Copyright (C) The Internet Society 2004.
Abstract Abstract
This document describes the protocol elements, along with their This document describes the protocol elements, along with their
semantics and encodings, of the Lightweight Directory Access Protocol semantics and encodings, of the Lightweight Directory Access Protocol
(LDAP). LDAP provides access to distributed directory services that (LDAP). LDAP provides access to distributed directory services that
act in accordance with X.500 data and service models. These protocol act in accordance with X.500 data and service models. These protocol
elements are based on those described in the X.500 Directory Access elements are based on those described in the X.500 Directory Access
Protocol (DAP). Protocol (DAP).
Lightweight Directory Access Protocol Version 3
Table of Contents Table of Contents
1. Introduction....................................................2 1. Introduction....................................................3
1.1. Relationship to Obsolete Specifications.......................3 1.1. Relationship to Obsolete Specifications.......................3
2. Conventions.....................................................3 2. Conventions.....................................................3
3. Protocol Model..................................................4 3. Protocol Model..................................................4
3.1 Operation and LDAP Exchange Relationship.......................4 3.1 Operation and LDAP Exchange Relationship.......................4
4. Elements of Protocol............................................4 4. Elements of Protocol............................................5
4.1. Common Elements...............................................5 4.1. Common Elements...............................................5
4.1.1. Message Envelope............................................5 4.1.1. Message Envelope............................................5
4.1.2. String Types................................................7
Lightweight Directory Access Protocol Version 3
4.1.2. String Types................................................6
4.1.3. Distinguished Name and Relative Distinguished Name..........7 4.1.3. Distinguished Name and Relative Distinguished Name..........7
4.1.4. Attribute Descriptions......................................7 4.1.4. Attribute Descriptions......................................7
4.1.5. Attribute Value.............................................7 4.1.5. Attribute Value.............................................8
4.1.6. Attribute Value Assertion...................................8 4.1.6. Attribute Value Assertion...................................8
4.1.7. Attribute and PartialAttribute..............................8 4.1.7. Attribute and PartialAttribute..............................9
4.1.8. Matching Rule Identifier....................................9 4.1.8. Matching Rule Identifier....................................9
4.1.9. Result Message..............................................9 4.1.9. Result Message..............................................9
4.1.10. Referral..................................................10 4.1.10. Referral..................................................11
4.1.11. Controls..................................................12 4.1.11. Controls..................................................12
4.2. Bind Operation...............................................14 4.2. Bind Operation...............................................14
4.3. Unbind Operation.............................................16 4.3. Unbind Operation.............................................17
4.4. Unsolicited Notification.....................................17 4.4. Unsolicited Notification.....................................17
4.5. Search Operation.............................................18 4.5. Search Operation.............................................18
4.6. Modify Operation.............................................26 4.6. Modify Operation.............................................27
4.7. Add Operation................................................28 4.7. Add Operation................................................28
4.8. Delete Operation.............................................29 4.8. Delete Operation.............................................29
4.9. Modify DN Operation..........................................29 4.9. Modify DN Operation..........................................30
4.10. Compare Operation...........................................31 4.10. Compare Operation...........................................31
4.11. Abandon Operation...........................................31 4.11. Abandon Operation...........................................32
4.12. Extended Operation..........................................32 4.12. Extended Operation..........................................32
4.13. IntermediateResponse Message................................33 4.13. IntermediateResponse Message................................34
4.13.1. Usage with LDAP ExtendedRequest and ExtendedResponse......34 4.13.1. Usage with LDAP ExtendedRequest and ExtendedResponse......35
4.13.2. Usage with LDAP Request Controls..........................34 4.13.2. Usage with LDAP Request Controls..........................35
4.14. StartTLS Operation..........................................35 4.14. StartTLS Operation..........................................35
5. Protocol Encoding, Connection, and Transfer....................37 5. Protocol Encoding, Connection, and Transfer....................37
5.2. Protocol Encoding............................................38 5.2. Protocol Encoding............................................38
5.3. Transmission Control Protocol (TCP)..........................38 5.3. Transmission Control Protocol (TCP)..........................38
6. Security Considerations........................................38 6. Security Considerations........................................39
7. Acknowledgements...............................................40 7. Acknowledgements...............................................40
8. Normative References...........................................40 8. Normative References...........................................40
9. Informative References.........................................41 9. Informative References.........................................42
10. IANA Considerations...........................................42 10. IANA Considerations...........................................42
11. Editor's Address..............................................42 11. Editor's Address..............................................43
Appendix A - LDAP Result Codes....................................43 Appendix A - LDAP Result Codes....................................44
A.1 Non-Error Result Codes........................................43 A.1 Non-Error Result Codes........................................44
A.2 Result Codes..................................................43 A.2 Result Codes..................................................44
Appendix B - Complete ASN.1 Definition............................48 Appendix B - Complete ASN.1 Definition............................49
Appendix C - Changes..............................................54 Appendix C - Changes..............................................55
C.1 Changes made to RFC 2251:.....................................54 C.1 Changes made to RFC 2251:.....................................55
C.2 Changes made to RFC 2830:.....................................59 C.2 Changes made to RFC 2830:.....................................60
C.3 Changes made to RFC 3771:.....................................60 C.3 Changes made to RFC 3771:.....................................61
Lightweight Directory Access Protocol Version 3
1. Introduction 1. Introduction
The Directory is "a collection of open systems cooperating to provide The Directory is "a collection of open systems cooperating to provide
directory services" [X.500]. A directory user, which may be a human directory services" [X.500]. A directory user, which may be a human
or other entity, accesses the Directory through a client (or or other entity, accesses the Directory through a client (or
Directory User Agent (DUA)). The client, on behalf of the directory Directory User Agent (DUA)). The client, on behalf of the directory
user, interacts with one or more servers (or Directory System Agents user, interacts with one or more servers (or Directory System Agents
(DSA)). Clients interact with servers using a directory access (DSA)). Clients interact with servers using a directory access
protocol. protocol.
Lightweight Directory Access Protocol Version 3
This document details the protocol elements of the Lightweight This document details the protocol elements of the Lightweight
Directory Access Protocol (LDAP), along with their semantics. Directory Access Protocol (LDAP), along with their semantics.
Following the description of protocol elements, it describes the way Following the description of protocol elements, it describes the way
in which the protocol elements are encoded and transferred. in which the protocol elements are encoded and transferred.
1.1. Relationship to Obsolete Specifications 1.1. Relationship to Obsolete Specifications
This document is an integral part of the LDAP Technical Specification This document is an integral part of the LDAP Technical Specification
[Roadmap] which obsoletes the previously defined LDAP technical [Roadmap] which obsoletes the previously defined LDAP technical
specification, RFC 3377, in its entirety. specification, RFC 3377, in its entirety.
skipping to change at line 149 skipping to change at line 158
"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 [Keyword]. to be interpreted as described in [Keyword].
The term "connection" refers to the underlying transport service used The term "connection" refers to the underlying transport service used
to carry the protocol exchange. to carry the protocol exchange.
The term "LDAP exchange" refers to application layer where LDAP PDUs The term "LDAP exchange" refers to application layer where LDAP PDUs
are exchanged between protocol peers. are exchanged between protocol peers.
The term "TLS layer" refers to a layer inserted between the The term "TLS layer" refers to a layer inserted between the
connection and the LDAP exchange that utilizes [TLS] to protect the connection and the LDAP exchange that utilizes Transport Layer
exchange of LDAP PDUs. Security ([TLS]) to protect the exchange of LDAP PDUs.
Lightweight Directory Access Protocol Version 3
The term "SASL layer" refers to a layer inserted between the The term "SASL layer" refers to a layer inserted between the
connection and the LDAP exchange that utilizes [SASL] to protect the connection and the LDAP exchange that utilizes Simple Authentication
exchange of LDAP PDUs. and Security Layer ([SASL]) to protect the exchange of LDAP PDUs.
See the table in Section 5 for an illustration of these four terms. See the table in Section 5 for an illustration of these four terms.
The term "TLS-protected LDAP exchange" refers to an LDAP exchange The term "TLS-protected LDAP exchange" refers to an LDAP exchange
protected by a TLS-layer. protected by a TLS-layer.
Lightweight Directory Access Protocol Version 3
The term "association" refers to the association of the LDAP exchange The term "association" refers to the association of the LDAP exchange
and its current authentication and authorization state. and its current authentication and authorization state.
Character names in this document use the notation for code points and
names from the Unicode Standard [Unicode]. For example, the letter
"a" may be represented as either <U+0061> or <LATIN SMALL LETTER A>.
Note: a glossary of terms used in Unicode can be found in [Glossary].
Information on the Unicode character encoding model can be found in
[CharModel].
3. Protocol Model 3. Protocol Model
The general model adopted by this protocol is one of clients The general model adopted by this protocol is one of clients
performing protocol operations against servers. In this model, a performing protocol operations against servers. In this model, a
client transmits a protocol request describing the operation to be client transmits a protocol request describing the operation to be
performed to a server. The server is then responsible for performing performed to a server. The server is then responsible for performing
the necessary operation(s) in the Directory. Upon completion of an the necessary operation(s) in the Directory. Upon completion of an
operation, the server typically returns a response containing operation, the server typically returns a response containing
appropriate data to the requesting client. appropriate data to the requesting client.
Protocol operations are generally independent of one another. Each
operation is processed as an atomic action, leaving the directory in
a consistent state.
Although servers are required to return responses whenever such Although servers are required to return responses whenever such
responses are defined in the protocol, there is no requirement for responses are defined in the protocol, there is no requirement for
synchronous behavior on the part of either clients or servers. synchronous behavior on the part of either clients or servers.
Requests and responses for multiple operations generally may be Requests and responses for multiple operations generally may be
exchanged between a client and server in any order, provided the exchanged between a client and server in any order. If required,
client eventually receives a response for every request that requires synchronous behavior may be controlled by client applications.
one.
The core protocol operations defined in this document can be mapped The core protocol operations defined in this document can be mapped
to a subset of the X.500 (1993) Directory Abstract Service [X.511]. to a subset of the X.500 (1993) Directory Abstract Service [X.511].
However there is not a one-to-one mapping between LDAP operations and However there is not a one-to-one mapping between LDAP operations and
X.500 Directory Access Protocol (DAP) operations. Server X.500 Directory Access Protocol (DAP) operations. Server
implementations acting as a gateway to X.500 directories may need to implementations acting as a gateway to X.500 directories may need to
make multiple DAP requests to service a single LDAP request. make multiple DAP requests to service a single LDAP request.
3.1 Operation and LDAP Exchange Relationship 3.1 Operation and LDAP Exchange Relationship
Lightweight Directory Access Protocol Version 3
Protocol operations are tied to an LDAP exchange. If the connection Protocol operations are tied to an LDAP exchange. When the connection
is closed, any uncompleted operations tied to the LDAP exchange are, is closed, any uncompleted operations tied to the LDAP exchange are,
when possible, abandoned, and when not possible, completed without when possible, abandoned, and when not possible, completed without
transmission of the response. Also, if the connection is closed, the transmission of the response. Also, when the connection is closed,
client MUST NOT assume that any uncompleted update operations tied to the client MUST NOT assume that any uncompleted update operations
the LDAP exchange have succeeded or failed. tied to the LDAP exchange have succeeded or failed.
4. Elements of Protocol 4. Elements of Protocol
The protocol is described using Abstract Syntax Notation One The protocol is described using Abstract Syntax Notation One
([ASN.1]), and is transferred using a subset of ASN.1 Basic Encoding ([ASN.1]), and is transferred using a subset of ASN.1 Basic Encoding
Rules ([BER]). Section 5 specifies how the protocol elements are Rules ([BER]). Section 5 specifies how the protocol elements are
encoded and transferred. encoded and transferred.
In order to support future extensions to this protocol, extensibility In order to support future extensions to this protocol, extensibility
is implied where it is allowed per ASN.1 (i.e. sequence, set, choice, is implied where it is allowed per ASN.1 (i.e. sequence, set, choice,
and enumerated types are extensible). In addition, ellipses (...) and enumerated types are extensible). In addition, ellipses (...)
have been supplied in ASN.1 types that are explicitly extensible as have been supplied in ASN.1 types that are explicitly extensible as
discussed in [LDAPIANA]. Because of the implied extensibility, discussed in [LDAPIANA]. Because of the implied extensibility,
clients and servers MUST (unless otherwise specified) ignore trailing clients and servers MUST (unless otherwise specified) ignore trailing
SEQUENCE components whose tags they do not recognize. SEQUENCE components whose tags they do not recognize.
Lightweight Directory Access Protocol Version 3
Changes to the protocol other than through the extension mechanisms Changes to the protocol other than through the extension mechanisms
described here require a different version number. A client indicates described here require a different version number. A client indicates
the version it is using as part of the bind request, described in the version it is using as part of the bind request, described in
Section 4.2. If a client has not sent a bind, the server MUST assume Section 4.2. If a client has not sent a bind, the server MUST assume
the client is using version 3 or later. the client is using version 3 or later.
Clients may determine the protocol versions a server supports by Clients may determine the protocol versions a server supports by
reading the 'supportedLDAPVersion' attribute from the root DSE (DSA- reading the 'supportedLDAPVersion' attribute from the root DSE (DSA-
Specific Entry) [Models]. Specific Entry) [Models].
skipping to change at line 246 skipping to change at line 265
encapsulated in a common envelope, the LDAPMessage, which is defined encapsulated in a common envelope, the LDAPMessage, which is defined
as follows: as follows:
LDAPMessage ::= SEQUENCE { LDAPMessage ::= SEQUENCE {
messageID MessageID, messageID MessageID,
protocolOp CHOICE { protocolOp CHOICE {
bindRequest BindRequest, bindRequest BindRequest,
bindResponse BindResponse, bindResponse BindResponse,
unbindRequest UnbindRequest, unbindRequest UnbindRequest,
searchRequest SearchRequest, searchRequest SearchRequest,
Lightweight Directory Access Protocol Version 3
searchResEntry SearchResultEntry, searchResEntry SearchResultEntry,
searchResDone SearchResultDone, searchResDone SearchResultDone,
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,
skipping to change at line 268 skipping to change at line 289
compareResponse CompareResponse, compareResponse CompareResponse,
abandonRequest AbandonRequest, abandonRequest AbandonRequest,
extendedReq ExtendedRequest, extendedReq ExtendedRequest,
extendedResp ExtendedResponse, extendedResp ExtendedResponse,
..., ...,
intermediateResponse IntermediateResponse }, intermediateResponse IntermediateResponse },
controls [0] Controls OPTIONAL } controls [0] Controls OPTIONAL }
MessageID ::= INTEGER (0 .. maxInt) MessageID ::= INTEGER (0 .. maxInt)
Lightweight Directory Access Protocol Version 3
maxInt INTEGER ::= 2147483647 -- (2^^31 - 1) -- maxInt INTEGER ::= 2147483647 -- (2^^31 - 1) --
The ASN.1 type Controls is defined in Section 4.1.11. The ASN.1 type Controls is defined in Section 4.1.11.
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 302 skipping to change at line 321
4.1.1.1. Message ID 4.1.1.1. Message ID
All LDAPMessage envelopes encapsulating responses contain the All LDAPMessage envelopes encapsulating responses contain the
messageID value of the corresponding request LDAPMessage. messageID value of the corresponding request LDAPMessage.
The message ID of a request MUST have a non-zero value different from The message ID of a request MUST have a non-zero value different from
the values of any other uncompleted requests in the LDAP association the values of any other uncompleted requests in the LDAP association
of which this message is a part. The zero value is reserved for the of which this message is a part. The zero value is reserved for the
unsolicited notification message. unsolicited notification message.
Lightweight Directory Access Protocol Version 3
Typical clients increment a counter for each request. Typical clients increment a counter for each request.
A client MUST NOT send a request with the same message ID as an A client MUST NOT send a request with the same message ID as an
earlier request on the same LDAP association unless it can be earlier request on the same LDAP association unless it can be
determined that the server is no longer servicing the earlier request determined that the server is no longer servicing the earlier request
(e.g. after the final response is received, or a subsequent bind (e.g. after the final response is received, or a subsequent bind
completes). Otherwise the behavior is undefined. For this purpose, completes). Otherwise the behavior is undefined. For this purpose,
note that abandon and abandoned operations do not send responses. note that abandon and abandoned operations do not send responses.
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 ASN.1 OCTET STRING types, the strings of LDAPString type encode as ASN.1 OCTET STRING types, the
[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. Note that Unicode characters U+0000 following the [UTF-8] algorithm. Note that Unicode characters U+0000
through U+007F are the same as ASCII 0 through 127, respectively, and through U+007F are the same as ASCII 0 through 127, respectively, and
have the same single octet UTF-8 encoding. Other Unicode characters have the same single octet UTF-8 encoding. Other Unicode characters
have a multiple octet UTF-8 encoding. have a multiple octet UTF-8 encoding.
LDAPString ::= OCTET STRING -- UTF-8 encoded, LDAPString ::= OCTET STRING -- UTF-8 encoded,
Lightweight Directory Access Protocol Version 3
-- [ISO10646] characters -- [ISO10646] characters
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. Although an LDAPOID is representation of an OBJECT IDENTIFIER. Although an LDAPOID is
encoded as an OCTET STRING, values are limited to the definition of encoded as an OCTET STRING, values are limited to the definition of
<numericoid> given in Section 1.4 of [Models]. <numericoid> given in Section 1.4 of [Models].
LDAPOID ::= OCTET STRING -- Constrained to <numericoid> [Models] LDAPOID ::= OCTET STRING -- Constrained to <numericoid> [Models]
skipping to change at line 355 skipping to change at line 373
-- Constrained to <distinguishedName> [LDAPDN] -- Constrained to <distinguishedName> [LDAPDN]
A RelativeLDAPDN is defined to be the representation of a Relative A RelativeLDAPDN is defined to be the representation of a Relative
Distinguished Name (RDN) after encoding according to the Distinguished Name (RDN) after encoding according to the
specification in [LDAPDN]. specification in [LDAPDN].
RelativeLDAPDN ::= LDAPString RelativeLDAPDN ::= LDAPString
-- Constrained to <name-component> [LDAPDN] -- Constrained to <name-component> [LDAPDN]
4.1.4. Attribute Descriptions 4.1.4. Attribute Descriptions
Lightweight Directory Access Protocol Version 3
The definition and encoding rules for attribute descriptions are The definition and encoding rules for attribute descriptions are
defined in Section 2.5 of [Models]. Briefly, an attribute description defined in Section 2.5 of [Models]. Briefly, an attribute description
is an attribute type and zero or more options. is an attribute type and zero or more options.
AttributeDescription ::= LDAPString AttributeDescription ::= LDAPString
-- Constrained to <attributedescription> -- Constrained to <attributedescription>
-- [Models] -- [Models]
4.1.5. Attribute Value 4.1.5. 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 attribute value. The attribute value is encoded according to encoded attribute value. The attribute value is encoded according to
the LDAP-specific encoding definition of its corresponding syntax. the LDAP-specific encoding definition of its corresponding syntax.
The LDAP-specific encoding definitions for different syntaxes and The LDAP-specific encoding definitions for different syntaxes and
attribute types may be found in other documents and in particular attribute types may be found in other documents and in particular
[Syntaxes]. [Syntaxes].
AttributeValue ::= OCTET STRING AttributeValue ::= OCTET STRING
Lightweight Directory Access Protocol Version 3
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 attribute values thus protocol values may include multi-megabyte attribute values
(e.g. photographs). (e.g. photographs).
Attribute values may be defined which have arbitrary and non- Attribute values may be defined which have arbitrary and non-
printable syntax. Implementations MUST NOT display nor attempt to printable syntax. Implementations MUST NOT display nor attempt to
decode an attribute value if its syntax is not known. The decode an attribute value if its syntax is not known. The
implementation may attempt to discover the subschema of the source implementation may attempt to discover the subschema of the source
entry, and retrieve the descriptions of 'attributeTypes' from it entry, and retrieve the descriptions of 'attributeTypes' from it
[Models]. [Models].
skipping to change at line 409 skipping to change at line 426
AttributeValueAssertion ::= SEQUENCE { AttributeValueAssertion ::= SEQUENCE {
attributeDesc AttributeDescription, attributeDesc AttributeDescription,
assertionValue AssertionValue } assertionValue AssertionValue }
AssertionValue ::= OCTET STRING AssertionValue ::= OCTET STRING
The syntax of the AssertionValue depends on the context of the LDAP The syntax of the AssertionValue depends on the context of the LDAP
operation being performed. For example, the syntax of the EQUALITY operation being performed. For example, the syntax of the EQUALITY
matching rule for an attribute is used when performing a Compare matching rule for an attribute is used when performing a Compare
Lightweight Directory Access Protocol Version 3
operation. Often this is the same syntax used for values of the operation. Often this is the same syntax used for values of the
attribute type, but in some cases the assertion syntax differs from attribute type, but in some cases the assertion syntax differs from
the value syntax. See objectIdentiferFirstComponentMatch in the value syntax. See objectIdentiferFirstComponentMatch in
[Syntaxes] for an example. [Syntaxes] for an example.
4.1.7. Attribute and PartialAttribute 4.1.7. Attribute and PartialAttribute
Attributes and partial attributes consist of an attribute description Attributes and partial attributes consist of an attribute description
and attribute values. A PartialAttribute allows zero values, while and attribute values. A PartialAttribute allows zero values, while
Attribute requires at least one value. Attribute requires at least one value.
PartialAttribute ::= SEQUENCE { PartialAttribute ::= SEQUENCE {
type AttributeDescription, type AttributeDescription,
vals SET OF value AttributeValue } vals SET OF value AttributeValue }
Attribute ::= PartialAttribute(WITH COMPONENTS { Attribute ::= PartialAttribute(WITH COMPONENTS {
..., ...,
vals (SIZE(1..MAX))}) vals (SIZE(1..MAX))})
Lightweight Directory Access Protocol Version 3
No two attribute values may be equivalent as described by Section 2.3 No two attribute values may be equivalent as described by Section 2.3
of [Models]. The set of attribute values is unordered. of [Models]. The set of attribute values is unordered.
Implementations MUST NOT rely upon the ordering being repeatable. Implementations MUST NOT rely upon the ordering being repeatable.
4.1.8. Matching Rule Identifier 4.1.8. Matching Rule Identifier
Matching rules are defined in Section 4.1.3 of [Models]. A matching Matching rules are defined in Section 4.1.3 of [Models]. A matching
rule is identified in the protocol by the printable representation of rule is identified in the protocol by the printable representation of
either its <numericoid>, or one of its short name descriptors either its <numericoid>, or one of its short name descriptors
[Models], e.g. 'caseIgnoreMatch' or '2.5.13.2'. [Models], e.g. 'caseIgnoreMatch' or '2.5.13.2'.
skipping to change at line 462 skipping to change at line 479
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),
Lightweight Directory Access Protocol Version 3
-- 9 reserved -- -- 9 reserved --
referral (10), referral (10),
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),
-- 22-31 unused -- -- 22-31 unused --
noSuchObject (32), noSuchObject (32),
aliasProblem (33), aliasProblem (33),
invalidDNSyntax (34), invalidDNSyntax (34),
-- 35 reserved for undefined isLeaf -- -- 35 reserved for undefined isLeaf --
aliasDereferencingProblem (36), aliasDereferencingProblem (36),
-- 37-47 unused -- -- 37-47 unused --
inappropriateAuthentication (48), inappropriateAuthentication (48),
Lightweight Directory Access Protocol Version 3
invalidCredentials (49), invalidCredentials (49),
insufficientAccessRights (50), insufficientAccessRights (50),
busy (51), busy (51),
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),
skipping to change at line 518 skipping to change at line 534
[LDAPIANA]. The meanings of the listed result codes are given in [LDAPIANA]. The meanings of the listed result codes are given in
Appendix A. If a server detects multiple errors for an operation, Appendix A. If a server detects multiple errors for an operation,
only one result code is returned. The server should return the result only one result code is returned. The server should return the result
code that best indicates the nature of the error encountered. code that best indicates the nature of the error encountered.
The diagnosticMessage field of this construct may, at the server's The diagnosticMessage field of this construct may, at the server's
option, be used to return a string containing a textual, human- option, be used to return a string containing a textual, human-
readable (terminal control and page formatting characters should be readable (terminal control and page formatting characters should be
avoided) diagnostic message. As this diagnostic message is not avoided) diagnostic message. As this diagnostic message is not
standardized, implementations MUST NOT rely on the values returned. standardized, implementations MUST NOT rely on the values returned.
Lightweight Directory Access Protocol Version 3
If the server chooses not to return a textual diagnostic, the If the server chooses not to return a textual diagnostic, the
diagnosticMessage field MUST be empty. diagnosticMessage field MUST be empty.
For certain result codes (typically, but not restricted to For certain result codes (typically, but not restricted to
noSuchObject, aliasProblem, invalidDNSyntax and noSuchObject, aliasProblem, invalidDNSyntax and
aliasDereferencingProblem), the matchedDN field is set to the name of aliasDereferencingProblem), the matchedDN field is set to the name of
the lowest entry (object or alias) in the Directory that was matched. the lowest entry (object or alias) in the Directory that was matched.
If no aliases were dereferenced while attempting to locate the entry, If no aliases were dereferenced while attempting to locate the entry,
this will be a truncated form of the name provided, or if aliases this will be a truncated form of the name provided, or if aliases
were dereferenced, of the resulting name, as defined in Section 12.5 were dereferenced, of the resulting name, as defined in Section 12.5
skipping to change at line 539 skipping to change at line 558
4.1.10. Referral 4.1.10. Referral
The referral result code indicates that the contacted server cannot The referral result code indicates that the contacted server cannot
or will not perform the operation and that one or more other servers or will not perform the operation and that one or more other servers
may be able to. Reasons for this include: may be able to. Reasons for this include:
- The target entry of the request is not held locally, but the - The target entry of the request is not held locally, but the
server has knowledge of its possible existence elsewhere. server has knowledge of its possible existence elsewhere.
Lightweight Directory Access Protocol Version 3
- The operation is restricted on this server -- perhaps due to a - The operation is restricted on this server -- perhaps due to a
read-only copy of an entry to be modified. read-only copy of an entry to be modified.
The referral field is present in an LDAPResult if the resultCode The referral field is present in an LDAPResult if the resultCode
field value is referral, and absent with all other result codes. It field value is referral, and absent with all other result codes. It
contains one or more references to one or more servers or services contains one or more references to one or more servers or services
that may be accessed via LDAP or other protocols. Referrals can be that may be accessed via LDAP or other protocols. Referrals can be
returned in response to any operation request (except unbind and returned in response to any operation request (except unbind and
abandon which do not have responses). At least one URI MUST be abandon which do not have responses). At least one URI MUST be
present in the Referral. present in the Referral.
skipping to change at line 573 skipping to change at line 590
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 supported services. If multiple referral by contacting one of the supported services. If multiple
URIs are present, the client assumes that any supported URI may be URIs are present, the client assumes that any supported URI may be
used to progress the operation. used to progress the operation.
Protocol peers that follow referrals MUST ensure that they do not Protocol peers that follow referrals MUST ensure that they do not
loop between servers. They MUST NOT repeatedly contact the same loop between servers. They MUST NOT repeatedly contact the same
server for the same request with the same target entry name, scope server for the same request with the same target entry name, scope
and filter. Some implementations use a counter that is incremented and filter. Some implementations use a counter that is incremented
each time referral handling occurs for an operation, and these kinds each time referral handling occurs for an operation, and these kinds
Lightweight Directory Access Protocol Version 3
of implementations MUST be able to handle at least ten nested of implementations MUST be able to handle at least ten nested
referrals between the root and a leaf entry. referrals between the root and a leaf entry.
A URI for a server implementing LDAP and accessible via [TCP]/[IP] A URI for a server implementing LDAP and accessible via [TCP]/[IP]
(v4 or v6) is written as an LDAP URL according to [LDAPURL]. (v4 or v6) is written as an LDAP URL according to [LDAPURL].
When an LDAP URL is used, the following instructions are followed: When an LDAP URL is used, the following instructions are followed:
- If an alias was dereferenced, the <dn> part of the URL MUST be - If an alias was dereferenced, the <dn> part of the URL MUST be
present, with the new target object name. UTF-8 encoded characters present, with the new target object name. UTF-8 encoded characters
skipping to change at line 594 skipping to change at line 613
may not be legal for URLs (e.g. spaces) and MUST be escaped using may not be legal for URLs (e.g. spaces) and MUST be escaped using
the % method in [URI]. the % method in [URI].
- It is RECOMMENDED that the <dn> part be present to avoid - It is RECOMMENDED that the <dn> part be present to avoid
ambiguity. ambiguity.
- If the <dn> part is present, the client MUST use this name in its - If the <dn> part is present, the client MUST use this name in its
next request to progress the operation, and if it is not present next request to progress the operation, and if it is not present
the client will use the same name as in the original request. the client will use the same name as in the original request.
Lightweight Directory Access Protocol Version 3
- Some servers (e.g. participating in distributed indexing) may - Some servers (e.g. participating in distributed indexing) may
provide a different filter in a URL of a referral for a search provide a different filter in a URL of a referral for a search
operation. operation.
- If the <filter> part of the LDAP URL is present, the client MUST - If the <filter> part of the LDAP URL is present, the client MUST
use this filter in its next request to progress this search, and use this filter in its next request to progress this search, and
if it is not present the client MUST use the same filter as it if it is not present the client MUST use the same filter as it
used for that search. used for that search.
- For search, it is RECOMMENDED that the <scope> part be present to - For search, it is RECOMMENDED that the <scope> part be present to
skipping to change at line 628 skipping to change at line 645
4.1.11. Controls 4.1.11. Controls
Controls provide a mechanism whereby the semantics and arguments of Controls provide a mechanism whereby the semantics and arguments of
existing LDAP operations may be extended. One or more controls may be existing LDAP operations may be extended. One or more controls may be
attached to a single LDAP message. A control only affects the attached to a single LDAP message. A control only affects the
semantics of the message it is attached to. semantics of the message it is attached to.
Controls sent by clients are termed 'request controls' and those sent Controls sent by clients are termed 'request controls' and those sent
by servers are termed 'response controls'. by servers are termed 'response controls'.
Lightweight Directory Access Protocol Version 3
Controls ::= SEQUENCE OF control Control Controls ::= SEQUENCE OF control Control
Control ::= SEQUENCE { Control ::= SEQUENCE {
controlType LDAPOID, controlType LDAPOID,
criticality BOOLEAN DEFAULT FALSE, criticality BOOLEAN DEFAULT FALSE,
controlValue OCTET STRING OPTIONAL } controlValue OCTET STRING OPTIONAL }
The controlType field is the dotted-decimal representation of an The controlType field is the dotted-decimal representation of an
OBJECT IDENTIFIER which uniquely identifies the control. This OBJECT IDENTIFIER which uniquely identifies the control. This
provides unambiguous naming of controls. Often, response control(s) provides unambiguous naming of controls. Often, response control(s)
skipping to change at line 649 skipping to change at line 668
request control. request control.
The criticality field only has meaning in controls attached to The criticality field only has meaning in controls attached to
request messages (except unbindRequest). For controls attached to request messages (except unbindRequest). For controls attached to
response messages and the unbindRequest, the criticality field SHOULD response messages and the unbindRequest, the criticality field SHOULD
be FALSE, and MUST be ignored by the receiving protocol peer. A value be FALSE, and MUST be ignored by the receiving protocol peer. A value
of TRUE indicates that it is unacceptable to perform the operation of TRUE indicates that it is unacceptable to perform the operation
without applying the semantics of the control and FALSE otherwise. without applying the semantics of the control and FALSE otherwise.
Specifically, the criticality field is applied as follows: Specifically, the criticality field is applied as follows:
Lightweight Directory Access Protocol Version 3
- Regardless of the value of the criticality field, if the server - Regardless of the value of the criticality field, if the server
recognizes the control type and it is appropriate for the recognizes the control type and it is appropriate for the
operation, the server is to make use of the control when operation, the server is to make use of the control when
performing the operation. performing the operation.
- 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, appropriate for the operation, and the criticality field is TRUE,
the server MUST NOT perform the operation, and for operations that the server MUST NOT perform the operation, and for operations that
have a response message, MUST return unavailableCriticalExtension have a response message, MUST return unavailableCriticalExtension
in the resultCode. in the resultCode.
skipping to change at line 675 skipping to change at line 692
The controlValue may contain information associated with the The controlValue may contain information associated with the
controlType. Its format is defined by the specification of the controlType. Its format is defined by the specification of the
control. Implementations MUST be prepared to handle arbitrary control. Implementations MUST be prepared to handle arbitrary
contents of the controlValue octet string, including zero bytes. It contents of the controlValue octet string, including zero bytes. It
is absent only if there is no value information which is associated is absent only if there is no value information which is associated
with a control of its type. When a controlValue is defined in terms with a control of its type. When a controlValue is defined in terms
of ASN.1, and BER encoded according to Section 5.2, it also follows of ASN.1, and BER encoded according to Section 5.2, it also follows
the extensibility rules in Section 4. the extensibility rules in Section 4.
Servers list the controlType of all request controls they recognize Servers list the controlType of request controls they recognize in
in the supportedControl attribute in the root DSE (Section 5.1 of the 'supportedControl' attribute in the root DSE (Section 5.1 of
[Models]). [Models]).
Controls SHOULD NOT be combined unless the semantics of the Controls SHOULD NOT be combined unless the semantics of the
combination has been specified. The semantics of control combination has been specified. The semantics of control
combinations, if specified, are generally found in the control combinations, if specified, are generally found in the control
specification most recently published. When a combination of controls specification most recently published. When a combination of controls
is encountered whose semantics are invalid, not specified (or not is encountered whose semantics are invalid, not specified (or not
Lightweight Directory Access Protocol Version 3
known), the message is considered to be not well-formed, thus the known), the message is considered to be not well-formed, thus the
operation fails with protocolError. Additionally, unless order- operation fails with protocolError. Additionally, unless order-
dependent semantics are given in a specification, the order of a dependent semantics are given in a specification, the order of a
combination of controls in the SEQUENCE is ignored. Where the order combination of controls in the SEQUENCE is ignored. Where the order
is to be ignored but cannot be ignored by the server, the message is is to be ignored but cannot be ignored by the server, the message is
considered not well-formed and the operation fails with considered not well-formed and the operation fails with
protocolError. protocolError.
This document does not specify any controls. Controls may be This document does not specify any controls. Controls may be
specified in other documents. Documents detailing control extensions specified in other documents. Documents detailing control extensions
skipping to change at line 706 skipping to change at line 725
- the OBJECT IDENTIFIER assigned to the control, - the OBJECT IDENTIFIER assigned to the control,
- direction as to what value the sender should provide for the - direction as to what value the sender should provide for the
criticality field (note: the semantics of the criticality field criticality field (note: the semantics of the criticality field
are defined above should not be altered by the control's are defined above should not be altered by the control's
specification), specification),
- whether information is to be present in the controlValue field, - whether information is to be present in the controlValue field,
and if so, the format of the controlValue contents, and if so, the format of the controlValue contents,
Lightweight Directory Access Protocol Version 3
- the semantics of the control, and - the semantics of the control, and
- optionally, semantics regarding the combination of the control - optionally, semantics regarding the combination of the control
with other controls. with other controls.
4.2. Bind Operation 4.2. Bind Operation
The function of the Bind Operation is to allow authentication The function of the Bind Operation is to allow authentication
information to be exchanged between the client and server. The Bind information to be exchanged between the client and server. The Bind
operation should be thought of as the "authenticate" operation. operation should be thought of as the "authenticate" operation.
skipping to change at line 740 skipping to change at line 757
-- 1 and 2 reserved -- 1 and 2 reserved
sasl [3] SaslCredentials, sasl [3] SaslCredentials,
... } ... }
SaslCredentials ::= SEQUENCE { SaslCredentials ::= SEQUENCE {
mechanism LDAPString, mechanism LDAPString,
credentials OCTET STRING OPTIONAL } credentials OCTET STRING OPTIONAL }
Fields of the Bind Request are: Fields of the Bind Request are:
Lightweight Directory Access Protocol Version 3
- 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 LDAP association. This document describes to be used in this LDAP association. This document describes
version 3 of the protocol. There is no version negotiation. The version 3 of the protocol. There is no version negotiation. The
client sets this field to the version it desires. If the server client sets this field to the version it desires. If the server
does not support the specified version, it MUST respond with does not support the specified version, it MUST respond with
protocolError in the resultCode field of the BindResponse. protocolError in the resultCode field of the BindResponse.
- 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 ([AuthMeth] Section string) for the purposes of anonymous binds ([AuthMeth] Section
skipping to change at line 761 skipping to change at line 780
authentication ([AuthMeth] Section 3.3.2). Where the server authentication ([AuthMeth] Section 3.3.2). Where the server
attempts to locate the named object, it SHALL NOT perform alias attempts to locate the named object, it SHALL NOT perform alias
dereferencing. dereferencing.
- authentication: information used in authentication. This type is - authentication: information used in authentication. This type is
extensible as defined in Section 3.7 of [LDAPIANA]. Servers that extensible as defined in Section 3.7 of [LDAPIANA]. Servers that
do not support a choice supplied by a client return do not support a choice supplied by a client return
authMethodNotSupported in the resultCode field of the authMethodNotSupported in the resultCode field of the
BindResponse. BindResponse.
Lightweight Directory Access Protocol Version 3
Textual passwords (consisting of a character sequence with a known Textual passwords (consisting of a character sequence with a known
character set and encoding) transferred to the server using the character set and encoding) transferred to the server using the
simple AuthenticationChoice SHALL be transferred as [UTF-8] simple AuthenticationChoice SHALL be transferred as [UTF-8]
encoded [Unicode]. Prior to transfer, clients SHOULD prepare text encoded [Unicode]. Prior to transfer, clients SHOULD prepare text
passwords by applying the [SASLprep] profile of the [Stringprep] passwords by applying the [SASLprep] profile of the [Stringprep]
algorithm. Passwords consisting of other data (such as random algorithm. Passwords consisting of other data (such as random
octets) MUST NOT be altered. The determination of whether a octets) MUST NOT be altered. The determination of whether a
password is textual is a local client matter. password is textual is a local client matter.
Authorization is the decision of which access an operation has to the Authorization is the decision of which access an operation has to the
skipping to change at line 794 skipping to change at line 811
multi-step bind process. Each step requires the server to return a multi-step bind process. Each step requires the server to return a
BindResponse to indicate the status of authentication. BindResponse to indicate the status of authentication.
After sending a BindRequest, clients MUST NOT send further LDAP PDUs After sending a BindRequest, clients MUST NOT send further LDAP PDUs
until receiving the BindResponse. Similarly, servers SHOULD NOT until receiving the BindResponse. Similarly, servers SHOULD NOT
process or respond to requests received while processing a process or respond to requests received while processing a
BindRequest. BindRequest.
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 to that request, it may then send a Bind Request. If operationsError to that request, it may then send a Bind Request. If
Lightweight Directory Access Protocol Version 3
this also fails or the client chooses not to bind on the existing this also fails or the client chooses not to bind on the existing
LDAP exchange, it may close the connection, reopen it and begin again LDAP exchange, it may close the connection, reopen it and begin again
by first sending a PDU with a Bind Request. This will aid in by first sending a PDU with a Bind Request. This will aid in
interoperating with servers implementing other versions of LDAP. interoperating with servers implementing other versions of LDAP.
Clients may send multiple Bind Requests on an LDAP exchange to change Clients may send multiple Bind Requests on an LDAP exchange to change
the authentication and/or security associations or to complete a the authentication and/or security associations or to complete a
multi-stage bind process. Authentication from earlier binds is multi-stage bind process. Authentication from earlier binds is
subsequently ignored. subsequently ignored.
skipping to change at line 815 skipping to change at line 834
client to invoke the BindRequest multiple times ([AuthMeth] Section client to invoke the BindRequest multiple times ([AuthMeth] Section
8.2). Clients MUST NOT invoke operations between two Bind Requests 8.2). Clients MUST NOT invoke operations between two Bind Requests
made as part of a multi-stage bind. made as part of a multi-stage bind.
A client may abort a SASL bind negotiation by sending a BindRequest A client may abort a SASL bind negotiation by sending a BindRequest
with a different value in the mechanism field of SaslCredentials, or with a different value in the mechanism field of SaslCredentials, or
an AuthenticationChoice other than sasl. an AuthenticationChoice other than sasl.
If the client sends a BindRequest with the sasl mechanism field as an If the client sends a BindRequest with the sasl mechanism field as an
empty string, the server MUST return a BindResponse with empty string, the server MUST return a BindResponse with
Lightweight Directory Access Protocol Version 3
authMethodNotSupported as the resultCode. This will allow clients to authMethodNotSupported as the resultCode. This will allow clients to
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.
4.2.2. Bind Response 4.2.2. 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,
skipping to change at line 850 skipping to change at line 866
protocolError, it is to assume that the server does not support this protocolError, it is to assume that the server does not support this
version of LDAP. While the client may be able proceed with another version of LDAP. While the client may be able proceed with another
version of this protocol (this may or may not require closing and re- version of this protocol (this may or may not require closing and re-
establishing the connection), how to proceed with another version of establishing the connection), how to proceed with another version of
this protocol is beyond the scope of this document. Clients which are this protocol is beyond the scope of this document. Clients which are
unable or unwilling to proceed SHOULD close the connection. unable or unwilling to proceed SHOULD close the connection.
The serverSaslCreds field is used as part of a SASL-defined bind The serverSaslCreds field is used as part of a SASL-defined bind
mechanism to allow the client to authenticate the server to which it mechanism to allow the client to authenticate the server to which it
is communicating, or to perform "challenge-response" authentication. is communicating, or to perform "challenge-response" authentication.
Lightweight Directory Access Protocol Version 3
If the client bound with the simple choice, or the SASL mechanism If the client bound with the simple choice, or the SASL mechanism
does not require the server to return information to the client, then does not require the server to return information to the client, then
this field SHALL NOT be included in the BindResponse. this field SHALL NOT be included in the BindResponse.
4.3. Unbind Operation 4.3. Unbind Operation
The function of the Unbind Operation is to terminate an LDAP The function of the Unbind Operation is to terminate an LDAP
association and close the connection. The Unbind operation is not the association and close the connection. The Unbind operation is not the
antithesis of the Bind operation as the name implies. The naming of antithesis of the Bind operation as the name implies. The naming of
these operations is historical. The Unbind operation should be these operations is historical. The Unbind operation should be
thought of as the "quit" operation. thought of as the "quit" operation.
The Unbind Operation is defined as follows: The Unbind Operation is defined as follows:
UnbindRequest ::= [APPLICATION 2] NULL UnbindRequest ::= [APPLICATION 2] NULL
The Unbind Operation has no response defined. Upon transmission of The Unbind Operation has no response defined. Upon transmission of
the UnbindRequest, each protocol peer is to consider the LDAP the UnbindRequest, each protocol peer is to consider the LDAP
association terminated, MUST cease transmission of messages to the association terminated, MUST cease transmission of messages to the
Lightweight Directory Access Protocol Version 3
other peer, and MUST close the connection. Uncompleted operations are other peer, and MUST close the connection. Uncompleted operations are
handled as specified in Section 5.1. handled as specified in Section 5.1.
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
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 LDAP exchange or connection between the client and server or in the LDAP exchange or connection between the client and
the server. The notification is of an advisory nature, and the server the server. The notification is of an advisory nature, and the server
skipping to change at line 904 skipping to change at line 920
specified in the responseName, specified in the responseName,
- the format of the contents (if any) of the responseValue, - the format of the contents (if any) of the responseValue,
- the circumstances which will cause the notification to be - the circumstances which will cause the notification to be
returned, and returned, and
- the semantics of the operation. - the semantics of the operation.
4.4.1. Notice of Disconnection 4.4.1. Notice of Disconnection
Lightweight Directory Access Protocol Version 3
This notification may be used by the server to advise the client that This notification may be used by the server to advise the client that
the server is about to close the connection due to an error the server is about to close the connection due to an error
condition. This notification is intended to assist clients in condition. This notification is intended to assist clients in
distinguishing between an error condition and a transient network distinguishing between an error condition and a transient network
failure. Note that this notification is not a response to an unbind failure. Note that this notification is not a response to an unbind
requested by the client. Uncompletetd operations are handled as requested by the client. Uncompleted operations are handled as
specified in Section 5.1. specified in Section 5.1.
The responseName is 1.3.6.1.4.1.1466.20036, the response field is The responseName is 1.3.6.1.4.1.1466.20036, the responseValue field
absent, and the resultCode is used to indicate the reason for the is absent, and the resultCode is used to indicate the reason for the
disconnection. disconnection.
The following result codes have these meanings when used in this The following result codes have these meanings when used in this
notification: 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.
Lightweight Directory Access Protocol Version 3
- strongAuthRequired: The server has detected that an established - strongAuthRequired: The server has detected that an established
security association between the client and server has security association between the client and server has
unexpectedly failed or been compromised, or that the server now unexpectedly failed or been compromised, or that the server now
requires the client to authenticate using a strong(er) mechanism. requires the client to authenticate using a strong(er) mechanism.
- unavailable: This server will stop accepting new connections and - unavailable: This server will stop accepting new connections and
operations on all existing LDAP exchanges, and be unavailable for operations on all existing LDAP exchanges, and be unavailable for
an extended period of time. The client may make use of an an extended period of time. The client may make use of an
alternative server. alternative server.
skipping to change at line 958 skipping to change at line 973
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) },
derefAliases ENUMERATED { derefAliases ENUMERATED {
Lightweight Directory Access Protocol Version 3
neverDerefAliases (0), neverDerefAliases (0),
derefInSearching (1), derefInSearching (1),
derefFindingBaseObj (2), derefFindingBaseObj (2),
derefAlways (3) }, derefAlways (3) },
sizeLimit INTEGER (0 .. maxInt), sizeLimit INTEGER (0 .. maxInt),
timeLimit INTEGER (0 .. maxInt), timeLimit INTEGER (0 .. maxInt),
typesOnly BOOLEAN, typesOnly BOOLEAN,
filter Filter, filter Filter,
attributes AttributeSelection } attributes AttributeSelection }
AttributeSelection ::= SEQUENCE OF selector LDAPString AttributeSelection ::= SEQUENCE OF selector LDAPString
-- The LDAPString is constrained to -- The LDAPString is constrained to
-- <attributeSelector> below -- <attributeSelector> below
Filter ::= CHOICE { Filter ::= CHOICE {
and [0] SET SIZE (1..MAX) OF filter Filter, and [0] SET SIZE (1..MAX) OF filter Filter,
or [1] SET SIZE (1..MAX) OF filter Filter, or [1] SET SIZE (1..MAX) OF filter Filter,
not [2] Filter, not [2] Filter,
equalityMatch [3] AttributeValueAssertion, equalityMatch [3] AttributeValueAssertion,
Lightweight Directory Access Protocol Version 3
substrings [4] SubstringFilter, substrings [4] SubstringFilter,
greaterOrEqual [5] AttributeValueAssertion, greaterOrEqual [5] AttributeValueAssertion,
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,
-- initial and final can occur at most once -- initial and final can occur at most once
skipping to change at line 1016 skipping to change at line 1030
- scope: Specifies the scope of the search to be performed. The - scope: Specifies the scope of the search to be performed. The
semantics (as described in [X.511]) of the possible values of this semantics (as described in [X.511]) of the possible values of this
field are: field are:
baseObject: The scope is constrained to the entry named by baseObject: The scope is constrained to the entry named by
baseObject. baseObject.
singleLevel: The scope is constrained to the immediate singleLevel: The scope is constrained to the immediate
subordinates of the entry named by baseObject. subordinates of the entry named by baseObject.
Lightweight Directory Access Protocol Version 3
wholeSubtree: the scope is constrained to the entry named by wholeSubtree: the scope is constrained to the entry named by
the baseObject, and all its subordinates. the baseObject, and all its subordinates.
- derefAliases: An indicator as to how alias entries (as defined in - derefAliases: An indicator as to how alias entries (as defined in
[Models]) are to be handled in searching. The semantics of the [Models]) 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 or neverDerefAliases: Do not dereference aliases in searching or
in locating the base object of the search. in locating the base object of the search.
derefInSearching: While searching, dereference any alias entry derefInSearching: While searching, dereference any alias entry
subordinate to the base object which is also in the search subordinate to the base object which is also in the search
scope. The filter is applied to the dereferenced object(s). If scope. The filter is applied to the dereferenced object(s). If
the search scope is wholeSubtree, the search continues in the the search scope is wholeSubtree, the search continues in the
subtree of any dereferenced object. Aliases in that subtree are subtree of any dereferenced object. Aliases in that subtree are
also dereferenced. Servers SHOULD eliminate duplicate entries also dereferenced. Servers SHOULD eliminate duplicate entries
that arise due to alias dereferencing while searching. that arise due to alias dereferencing while searching.
Lightweight Directory Access Protocol Version 3
derefFindingBaseObj: Dereference aliases in locating the base derefFindingBaseObj: Dereference aliases in locating the base
object of the search, but not when searching subordinates of object of the search, but not when searching subordinates of
the base object. the base object.
derefAlways: Dereference aliases both in searching and in derefAlways: Dereference aliases both in searching and in
locating the base object of the search. locating the base object of the search.
Servers MUST detect looping while dereferencing aliases in order Servers MUST detect looping while dereferencing aliases in order
to prevent denial of service attacks of this nature. to prevent denial of service attacks of this nature.
- sizeLimit: A size limit that restricts the maximum number of - sizeLimit: A size limit that restricts the maximum number of
skipping to change at line 1070 skipping to change at line 1084
descriptions (no values) to be returned. Setting this field to descriptions (no values) to be returned. Setting this field to
FALSE causes both attribute descriptions and values to be FALSE causes both attribute descriptions and values to be
returned. returned.
- 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
Lightweight Directory Access Protocol Version 3
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
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
Lightweight Directory Access Protocol Version 3
is TRUE, and Undefined if it is Undefined. is TRUE, and Undefined if it is Undefined.
The present match evaluates to TRUE where there is an attribute or The present match evaluates to TRUE where there is an attribute or
subtype of the specified attribute description present in an subtype of the specified attribute description present in an
entry, and FALSE otherwise (including a presence test with an entry, and FALSE otherwise (including a presence test with an
unrecognized attribute description.) unrecognized attribute description.)
The matching rule for equalityMatch filter items is defined by the The matching rule for equalityMatch filter items is defined by the
EQUALITY matching rule for the attribute type. EQUALITY matching rule for the attribute type.
skipping to change at line 1126 skipping to change at line 1139
the ORDERING and EQUALITY matching rules for the attribute type. the ORDERING and EQUALITY matching rules for the attribute type.
The matching rule for the lessOrEqual filter item is defined by The matching rule for the lessOrEqual filter item is defined by
the ORDERING matching rule for the attribute type. the ORDERING matching rule for the attribute type.
An approxMatch filter item evaluates to TRUE when there is a value An approxMatch filter item evaluates to TRUE when there is a value
of the attribute or subtype for which some locally-defined of the attribute or subtype for which some locally-defined
approximate matching algorithm (e.g. spelling variations, phonetic approximate matching algorithm (e.g. spelling variations, phonetic
match, etc.) returns TRUE. If an item matches for equality, it match, etc.) returns TRUE. If an item matches for equality, it
also satisfies an approximate match. If approximate matching is also satisfies an approximate match. If approximate matching is
not supported, this filter item should be treated as an not supported for the attribute, this filter item should be
equalityMatch. Lightweight Directory Access Protocol Version 3
treated as an equalityMatch.
An extensibleMatch filter item is evaluated as follows: An extensibleMatch filter item is evaluated as follows:
If the matchingRule field is absent, the type field MUST be If the matchingRule field is absent, the type field MUST be
present, and an equality match is performed for that type. present, and an equality match is performed for that type.
If the type field is absent and the matchingRule is present, the If the type field is absent and the matchingRule is present, the
matchValue is compared against all attributes in an entry which matchValue is compared against all attributes in an entry which
support that matchingRule. The matchingRule determines the support that matchingRule. The matchingRule determines the
syntax for the assertion value. The filter item evaluates to syntax for the assertion value. The filter item evaluates to
TRUE if it matches with at least one attribute in the entry, TRUE if it matches with at least one attribute in the entry,
FALSE if it does not match any attribute in the entry, and FALSE if it does not match any attribute in the entry, and
Undefined if the matchingRule is not recognized or the Undefined if the matchingRule is not recognized or the
assertionValue is invalid. assertionValue is invalid.
If the type field is present and the matchingRule is present, If the type field is present and the matchingRule is present,
the matchValue is compared against entry attributes of the the matchValue is compared against entry attributes of the
specified type. In this case, the matchingRule MUST be one specified type. In this case, the matchingRule MUST be one
Lightweight Directory Access Protocol Version 3
suitable for use with the specified type (see [Syntaxes]), suitable for use with the specified type (see [Syntaxes]),
otherwise the filter item is Undefined. otherwise the filter item is Undefined.
If the dnAttributes field is set to TRUE, the match is If the dnAttributes field is set to TRUE, the match is
additionally applied against all the AttributeValueAssertions in additionally applied against all the AttributeValueAssertions in
an entry's distinguished name, and evaluates to TRUE if there is an entry's distinguished name, and evaluates to TRUE if there is
at least one attribute in the distinguished name for which the at least one attribute in the distinguished name for which the
filter item evaluates to TRUE. The dnAttributes field is present filter item evaluates to TRUE. The dnAttributes field is present
to alleviate the need for multiple versions of generic matching to alleviate the need for multiple versions of generic matching
rules (such as word matching), where one applies to entries and rules (such as word matching), where one applies to entries and
another applies to entries and dn attributes as well. another applies to entries and dn attributes as well.
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 MatchingRuleId in the
extensibleMatch is not recognized by the server, the assertion extensibleMatch is not recognized by the server, the assertion
value is invalid, or the type of filtering requested is not value is invalid, 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, assertion values are matching rule ids are not recognized, assertion values are
invalid, or the assertion syntax is not supported. More details of invalid, or the assertion syntax is not supported. More details of
filter processing are given in Section 7.8 of [X.511]. filter processing are given in Section 7.8 of [X.511].
- attributes: A selection list of the attributes to be returned from - attributes: A selection list of the attributes to be returned from
each entry which matches the search filter. LDAPString values of each entry which matches the search filter. LDAPString values of
this field are constrained to the following Augmented Backus-Naur this field are constrained to the following Augmented Backus-Naur
Form ([ABNF]): Form ([ABNF]):
Lightweight Directory Access Protocol Version 3
attributeSelector = attributedescription / selectorpecial attributeSelector = attributedescription / selectorpecial
selectorspecial = noattrs / alluserattrs selectorspecial = noattrs / alluserattrs
noattrs = %x31.2E.31 ; "1.1" noattrs = %x31.2E.31 ; "1.1"
alluserattrs = %x2A ; asterisk ("*") alluserattrs = %x2A ; asterisk ("*")
The <attributedescription> production is defined in Section 2.5 of The <attributedescription> production is defined in Section 2.5 of
[Models]. [Models].
There are three special cases which may exist in the attribute There are three special cases which may appear in the attributes
selection: selection list:
- an empty list with no attributes, - an empty list with no attributes,
- a list containing "*" (with zero or more attribute - a list containing "*" (with zero or more attribute
descriptions), and descriptions), and
Lightweight Directory Access Protocol Version 3
- a list containing only "1.1". - a list containing only "1.1".
An empty list requests the return of all user attributes. An empty list requests the return of all user attributes.
A list containing "*" requests all user attributes in addition to A list containing "*" requests the return of all user attributes
other listed (operational) attributes. in addition to other listed (operational) attributes.
A list containing only the OID "1.1" indicates that no values are A list containing only the OID "1.1" indicates that no attributes
to be returned. If "1.1" is provided with other values, the "1.1" are to be returned. If "1.1" is provided with other
value is ignored. This OID was chosen because it does not (and can attributeSelector values, the "1.1" attributeSelector is ignored.
not) correspond to any attribute in use. This OID was chosen because it does not (and can not) correspond
to any attribute in use.
Client implementors should note that even if all user attributes Client implementors should note that even if all user attributes
are requested, some attributes and/or attribute values of the are requested, some attributes and/or attribute values of the
entry may not be included in search results due to access controls entry may not be included in search results due to access controls
or other restrictions. Furthermore, servers will not return or other restrictions. Furthermore, servers will not return
operational attributes, such as objectClasses or attributeTypes, operational attributes, such as objectClasses or attributeTypes,
unless they are listed by name. Operational attributes are unless they are listed by name. Operational attributes are
described in [Models]. described in [Models].
Attributes are returned at most once in an entry. If an attribute Attributes are returned at most once in an entry. If an attribute
skipping to change at line 1239 skipping to change at line 1252
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 operation are returned as zero or more The results of the search operation are returned as zero or more
searchResultEntry messages, zero or more SearchResultReference searchResultEntry messages, zero or more SearchResultReference
messages, followed by a single searchResultDone message. messages, followed by a single searchResultDone message.
SearchResultEntry ::= [APPLICATION 4] SEQUENCE { SearchResultEntry ::= [APPLICATION 4] SEQUENCE {
objectName LDAPDN, objectName LDAPDN,
attributes PartialAttributeList } attributes PartialAttributeList }
PartialAttributeList ::= SEQUENCE OF PartialAttributeList ::= SEQUENCE OF
partialAttribute PartialAttribute partialAttribute PartialAttribute
-- Note that the PartialAttributeList may hold zero elements. -- Note that the PartialAttributeList may hold zero elements.
-- This may happen when none of the attributes of an entry -- This may happen when none of the attributes of an entry
-- were requested, or could be returned. -- were requested, or could be returned.
-- Note also that the partialAttribute vals set may hold zero -- Note also that the partialAttribute vals set may hold zero
-- elements. This may happen when typesOnly is requested, access -- elements. This may happen when typesOnly is requested, access
-- controls prevent the return of values, or other reasons. -- controls prevent the return of values, or other reasons.
Lightweight Directory Access Protocol Version 3
SearchResultReference ::= [APPLICATION 19] SEQUENCE SearchResultReference ::= [APPLICATION 19] SEQUENCE
SIZE (1..MAX) OF uri URI SIZE (1..MAX) OF uri URI
SearchResultDone ::= [APPLICATION 5] LDAPResult SearchResultDone ::= [APPLICATION 5] LDAPResult
Each SearchResultEntry represents an entry found during the search. Each SearchResultEntry represents an entry found during the search.
Each SearchResultReference represents an area not yet explored during Each SearchResultReference represents an area not yet explored during
the search. The SearchResultEntry and SearchResultReference PDUs may the search. The SearchResultEntry and SearchResultReference PDUs may
come in any order. Following all the SearchResultReference and come in any order. Following all the SearchResultReference and
SearchResultEntry responses, the server returns a SearchResultDone SearchResultEntry responses, the server returns a SearchResultDone
skipping to change at line 1292 skipping to change at line 1305
If the server's schema defines short names [Models] for an attribute If the server's schema defines short names [Models] for an attribute
type then the server SHOULD use one of those names in attribute type then the server SHOULD use one of those names in attribute
descriptions for that attribute type (in preference to using the descriptions for that attribute type (in preference to using the
<numericoid> [Models] format of the attribute type's object <numericoid> [Models] format of the attribute type's object
identifier). The server SHOULD NOT use the short name if that name is identifier). The server SHOULD NOT use the short name if that name is
known by the server to be ambiguous, or otherwise likely to cause known by the server to be ambiguous, or otherwise likely to cause
interoperability problems. interoperability problems.
4.5.3. Continuation References in the Search Result 4.5.3. Continuation References in the Search Result
Lightweight Directory Access Protocol Version 3
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 one or more non-local entries, baseObject but was unable to search one or more non-local entries,
the server may return one or more SearchResultReference entries, each the server may return one or more SearchResultReference entries, each
containing a reference to another set of servers for continuing the containing a reference to another set of servers for continuing the
operation. A server MUST NOT return any SearchResultReference if it operation. A server MUST NOT return any SearchResultReference if it
has not located the baseObject and thus has not searched any entries; has not located the baseObject and thus has not searched any entries;
in this case it would return a SearchResultDone containing either a in this case it would return a SearchResultDone containing either a
referral or noSuchObject result code (depending on the server's referral or noSuchObject result code (depending on the server's
knowledge of the entry named in the baseObject). knowledge of the entry named in the baseObject).
skipping to change at line 1314 skipping to change at line 1328
context [Section 5 of Models], it may use the search filter to context [Section 5 of Models], it may use the search filter to
determine whether or not to return a SearchResultReference response. determine whether or not to return a SearchResultReference response.
Otherwise SearchResultReference responses are always returned when in Otherwise SearchResultReference responses are always returned when in
scope. scope.
The SearchResultReference is of the same data type as the Referral. The SearchResultReference is of the same data type as the Referral.
A URI for a server implementing LDAP and accessible via [TCP]/[IP] A URI for a server implementing LDAP and accessible via [TCP]/[IP]
(v4 or v6) is written as an LDAP URL according to [LDAPURL]. (v4 or v6) is written as an LDAP URL according to [LDAPURL].
Lightweight Directory Access Protocol Version 3
In order to complete the search, the client issues a new search In order to complete the search, the client issues a new search
operation for each SearchResultReference that is returned. Note that operation for each SearchResultReference that is returned. Note that
the abandon operation described in Section 4.11 applies only to a the abandon operation described in Section 4.11 applies only to a
particular operation sent on an association between a client and particular operation sent on an association between a client and
server. The client must abandon subsequent search operations it server. The client must abandon subsequent search operations it
wishes to individually. wishes to individually.
Clients that follow search continuation references MUST ensure that Clients that follow search continuation references MUST ensure that
they do not loop between servers. They MUST NOT repeatedly contact they do not loop between servers. They MUST NOT repeatedly contact
the same server for the same request with the same target entry name, the same server for the same request with the same target entry name,
skipping to change at line 1350 skipping to change at line 1362
provide a different filter in a URL of a SearchResultReference. provide a different filter in a URL of a SearchResultReference.
- If the <filter> part of the URL is present, the client MUST use - If the <filter> part of the URL is present, the client MUST use
this filter in its next request to progress this search, and if it this filter in its next request to progress this search, and if it
is not present the client MUST use the same filter as it used for is not present the client MUST use the same filter as it used for
that search. that search.
- If the originating search scope was singleLevel, the <scope> part - If the originating search scope was singleLevel, the <scope> part
of the URL will be "base". of the URL will be "base".
Lightweight Directory Access Protocol Version 3
- it is RECOMMENDED that the <scope> part be present to avoid - it is RECOMMENDED that the <scope> part be present to avoid
ambiguity. ambiguity.
- Other aspects of the new search request may be the same as or - Other aspects of the new search request may be the same as or
different from the search request which generated the different from the search request which generated the
SearchResultReference. SearchResultReference.
- The name of an unexplored subtree in a SearchResultReference need - The name of an unexplored subtree in a SearchResultReference need
not be subordinate to the base object. not be subordinate to the base object.
Other kinds of URIs may be returned. The syntax and semantics of such Other kinds of URIs may be returned. The syntax and semantics of such
URIs is left to future specifications. Clients may ignore URIs that URIs is left to future specifications. Clients may ignore URIs that
they do not support. they do not support.
4.5.3.1. Examples 4.5.3.1. Examples
For example, suppose the contacted server (hosta) holds the entry For example, suppose the contacted server (hosta) holds the entry
<DC=Example,DC=NET> and the entry <CN=Manager,DC=Example,DC=NET>. It <DC=Example,DC=NET> and the entry <CN=Manager,DC=Example,DC=NET>. It
Lightweight Directory Access Protocol Version 3
knows that either LDAP-capable servers (hostb) or (hostc) hold knows that either LDAP-capable servers (hostb) or (hostc) hold
<OU=People,DC=Example,DC=NET> (one is the master and the other server <OU=People,DC=Example,DC=NET> (one is the master and the other server
a shadow), and that LDAP-capable server (hostd) holds the subtree a shadow), and that LDAP-capable server (hostd) holds the subtree
<OU=Roles,DC=Example,DC=NET>. If a wholeSubtree search of <OU=Roles,DC=Example,DC=NET>. If a wholeSubtree search of
<DC=Example,DC=NET> is requested to the contacted server, it may <DC=Example,DC=NET> is requested to the contacted server, it may
return the following: return the following:
SearchResultEntry for DC=Example,DC=NET SearchResultEntry for DC=Example,DC=NET
SearchResultEntry for CN=Manager,DC=Example,DC=NET SearchResultEntry for CN=Manager,DC=Example,DC=NET
SearchResultReference { SearchResultReference {
skipping to change at line 1405 skipping to change at line 1416
ldap://hoste/OU=Managers,OU=People,DC=Example,DC=NET??sub } ldap://hoste/OU=Managers,OU=People,DC=Example,DC=NET??sub }
SearchResultReference { SearchResultReference {
ldap://hostf/OU=Consultants,OU=People,DC=Example,DC=NET??sub } ldap://hostf/OU=Consultants,OU=People,DC=Example,DC=NET??sub }
SearchResultDone (success) SearchResultDone (success)
Similarly, if a singleLevel search of <DC=Example,DC=NET> is Similarly, if a singleLevel search of <DC=Example,DC=NET> is
requested to the contacted server, it may return the following: requested to the contacted server, it may return the following:
SearchResultEntry for CN=Manager,DC=Example,DC=NET SearchResultEntry for CN=Manager,DC=Example,DC=NET
SearchResultReference { SearchResultReference {
Lightweight Directory Access Protocol Version 3
ldap://hostb/OU=People,DC=Example,DC=NET??base ldap://hostb/OU=People,DC=Example,DC=NET??base
ldap://hostc/OU=People,DC=Example,DC=NET??base } ldap://hostc/OU=People,DC=Example,DC=NET??base }
SearchResultReference { SearchResultReference {
ldap://hostd/OU=Roles,DC=Example,DC=NET??base } ldap://hostd/OU=Roles,DC=Example,DC=NET??base }
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,
but has knowledge of its possible location, then it may return a but has knowledge of its possible location, then it may return a
referral to the client. In this case, if the client requests a referral to the client. In this case, if the client requests a
subtree search of <DC=Example,DC=ORG> to hosta, the server returns a subtree search of <DC=Example,DC=ORG> to hosta, the server returns a
SearchResultDone containing a referral. SearchResultDone containing a referral.
SearchResultDone (referral) { SearchResultDone (referral) {
ldap://hostg/DC=Example,DC=ORG??sub } ldap://hostg/DC=Example,DC=ORG??sub }
4.6. Modify Operation 4.6. Modify Operation
Lightweight Directory Access Protocol Version 3
The Modify Operation allows a client to request that a modification The Modify Operation allows a client to request that a modification
of an entry be performed on its behalf by a server. The Modify of an entry be performed on its behalf by a server. The Modify
Request is defined as follows: Request is defined as follows:
ModifyRequest ::= [APPLICATION 6] SEQUENCE { ModifyRequest ::= [APPLICATION 6] SEQUENCE {
object LDAPDN, object LDAPDN,
changes SEQUENCE OF change SEQUENCE { changes SEQUENCE OF change SEQUENCE {
operation ENUMERATED { operation ENUMERATED {
add (0), add (0),
delete (1), delete (1),
skipping to change at line 1460 skipping to change at line 1471
performed MUST conform to the requirements of the directory model performed MUST conform to the requirements of the directory model
and controlling schema [Models]. and controlling schema [Models].
- operation: Used to specify the type of modification being - operation: Used to specify the type of modification being
performed. Each operation type acts on the following performed. Each operation type acts on the following
modification. The values of this field have the following modification. The values of this field have the following
semantics respectively: semantics respectively:
add: add values listed to the modification attribute, add: add values listed to the modification attribute,
creating the attribute if necessary; creating the attribute if necessary;
Lightweight Directory Access Protocol Version 3
delete: delete values listed from the modification attribute, delete: delete values listed from the modification attribute,
removing the entire attribute if no values are listed, or if removing the entire attribute if no values are listed, or if
all current values of the attribute are listed for deletion; all current values of the attribute are listed for deletion;
replace: replace all existing values of the modification replace: replace all existing values of the modification
attribute with the new values listed, creating the attribute attribute with the new values listed, creating the attribute
if it did not already exist. A replace with no value will if it did not already exist. A replace with no value will
delete the entire attribute if it exists, and is ignored if delete the entire attribute if it exists, and is ignored if
the attribute does not exist. the attribute does not exist.
- modification: A PartialAttribute (which may have an empty SET - modification: A PartialAttribute (which may have an empty SET
of vals) used to hold the attribute type or attribute type and of vals) used to hold the attribute type or attribute type and
values being modified. values being modified.
Upon receipt of a Modify Request, the server attempts to perform the Upon receipt of a Modify Request, the server attempts to perform the
necessary modifications to the DIT and returns the result in a Modify necessary modifications to the DIT and returns the result in a Modify
Response, defined as follows: Response, defined as follows:
Lightweight Directory Access Protocol Version 3
ModifyResponse ::= [APPLICATION 7] LDAPResult ModifyResponse ::= [APPLICATION 7] LDAPResult
The server will return to the client a single Modify Response The server will return to the client a single Modify Response
indicating either the successful completion of the DIT modification, indicating either the successful completion of the DIT modification,
or the reason that the modification failed. Due to the requirement or the reason that the modification failed. Due to the requirement
for atomicity in applying the list of modifications in the Modify for atomicity in applying the list of modifications in the Modify
Request, the client may expect that no modifications of the DIT have Request, the client may expect that no modifications of the DIT have
been performed if the Modify Response received indicates any sort of been performed if the Modify Response received indicates any sort of
error, and that all requested modifications have been performed if error, and that all requested modifications have been performed if
the Modify Response indicates successful completion of the Modify the Modify Response indicates successful completion of the Modify
skipping to change at line 1515 skipping to change at line 1525
entry MUST be identical. entry MUST be identical.
4.7. Add Operation 4.7. Add Operation
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 }
Lightweight Directory Access Protocol Version 3
AttributeList ::= SEQUENCE OF attribute Attribute AttributeList ::= SEQUENCE OF attribute Attribute
Fields of the Add Request are: Fields of the Add Request are:
- entry: the name of the entry to be added. The server SHALL NOT - entry: the name of the entry to be added. The server SHALL NOT
dereference any aliases in locating the entry to be added. dereference any aliases in locating the entry to be added.
- attributes: the list of attributes that, along with those from the - attributes: the list of attributes that, along with those from the
RDN, make up the content of the entry being added. Clients MAY or RDN, make up the content of the entry being added. Clients MAY or
MAY NOT include the RDN attribute in this list. Clients MUST MAY NOT include the RDN attribute in this list. Clients MUST
include the 'objectClass' attribute, and values of any mandatory include the 'objectClass' attribute, and values of any mandatory
attributes of the listed object classes. Clients MUST NOT supply attributes of the listed object classes. Clients MUST NOT supply
NO-USER-MODIFICATION attributes such as the createTimestamp or NO-USER-MODIFICATION attributes such as the createTimestamp or
creatorsName attributes, since the server maintains these creatorsName attributes, since the server maintains these
automatically. automatically.
Lightweight Directory Access Protocol Version 3
The entry named in the entry field of the AddRequest MUST NOT exist The entry named in the entry field of the AddRequest MUST NOT exist
for the AddRequest to succeed. The immediate superior (parent) of an for the AddRequest to succeed. The immediate superior (parent) of an
object or alias entry to be added MUST exist. For example, if the object or alias entry to be added MUST exist. For example, if the
client attempted to add <CN=JS,DC=Example,DC=NET>, the client attempted to add <CN=JS,DC=Example,DC=NET>, the
<DC=Example,DC=NET> entry did not exist, and the <DC=NET> entry did <DC=Example,DC=NET> entry did not exist, and the <DC=NET> entry did
exist, then the server would return the noSuchObject result code with exist, then the server would return the noSuchObject result code with
the matchedDN field containing <DC=NET>. the matchedDN field containing <DC=NET>.
Server implementations SHOULD NOT restrict where entries can be Server implementations SHOULD NOT restrict where entries can be
located in the Directory unless DIT structure rules are in place. located in the Directory unless DIT structure rules are in place.
skipping to change at line 1570 skipping to change at line 1579
DelRequest ::= [APPLICATION 10] LDAPDN DelRequest ::= [APPLICATION 10] LDAPDN
The Delete Request consists of the name of the entry to be deleted. The Delete Request consists of the name of the entry to be deleted.
The server SHALL NOT dereference aliases while resolving the name of The server SHALL NOT dereference aliases while resolving the name of
the target entry to be removed. the target entry to be removed.
Only leaf entries (those with no subordinate entries) can be deleted Only leaf entries (those with no subordinate entries) can be deleted
with this operation. with this operation.
Lightweight Directory Access Protocol Version 3
Upon receipt of a Delete Request, a server will attempt to perform Upon receipt of a Delete Request, a server will attempt to perform
the entry removal requested and return the result in the Delete the entry removal requested and return the result in the Delete
Response defined as follows: Response defined as follows:
DelResponse ::= [APPLICATION 11] LDAPResult DelResponse ::= [APPLICATION 11] LDAPResult
4.9. Modify DN Operation 4.9. Modify DN Operation
The Modify DN Operation allows a client to change the Relative The Modify DN Operation allows a client to change the Relative
Distinguished Name (RDN) of an entry in the Directory, and/or to move Distinguished Name (RDN) of an entry in the Directory, and/or to move
a subtree of entries to a new location in the Directory. The Modify a subtree of entries to a new location in the Directory. The Modify
DN Request is defined as follows: DN Request is defined as follows:
ModifyDNRequest ::= [APPLICATION 12] SEQUENCE { ModifyDNRequest ::= [APPLICATION 12] SEQUENCE {
entry LDAPDN, entry LDAPDN,
newrdn RelativeLDAPDN, newrdn RelativeLDAPDN,
Lightweight Directory Access Protocol Version 3
deleteoldrdn BOOLEAN, deleteoldrdn BOOLEAN,
newSuperior [0] LDAPDN OPTIONAL } newSuperior [0] LDAPDN OPTIONAL }
Fields of the Modify DN Request are: Fields of the Modify DN Request are:
- entry: the name of the entry to be changed. This entry may or may - entry: the name of the entry to be changed. This entry may or may
not have subordinate entries. not have subordinate entries.
- newrdn: the new RDN of the entry. If the operation moves the entry - newrdn: the new RDN of the entry. If the operation moves the entry
to a new superior without changing its RDN, the value of the old to a new superior without changing its RDN, the value of the old
skipping to change at line 1625 skipping to change at line 1633
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 and return the result in the Modify DN Response, the name change and return the result in the Modify DN Response,
defined as follows: defined as follows:
ModifyDNResponse ::= [APPLICATION 13] LDAPResult ModifyDNResponse ::= [APPLICATION 13] LDAPResult
For example, if the entry named in the entry field was <cn=John For example, if the entry named in the entry field was <cn=John
Smith,c=US>, the newrdn field was <cn=John Cougar Smith>, and the Smith,c=US>, the newrdn field was <cn=John Cougar Smith>, and the
newSuperior field was absent, then this operation would attempt to newSuperior field was absent, then this operation would attempt to
rename the entry to be <cn=John Cougar Smith,c=US>. If there was rename the entry to be <cn=John Cougar Smith,c=US>. If there was
Lightweight Directory Access Protocol Version 3
already an entry with that name, the operation would fail with the already an entry with that name, the operation would fail with the
entryAlreadyExists result code. entryAlreadyExists result code.
The object named in newSuperior MUST exist. For example, if the The object named in newSuperior MUST exist. For example, if the
client attempted to add <CN=JS,DC=Example,DC=NET>, the client attempted to add <CN=JS,DC=Example,DC=NET>, the
<DC=Example,DC=NET> entry did not exist, and the <DC=NET> entry did <DC=Example,DC=NET> entry did not exist, and the <DC=NET> entry did
exist, then the server would return the noSuchObject result code with exist, then the server would return the noSuchObject result code with
the matchedDN field containing <DC=NET>. the matchedDN field containing <DC=NET>.
If the deleteoldrdn field is TRUE, the attribute values forming the If the deleteoldrdn field is TRUE, the attribute values forming the
old RDN but not the new RDN are deleted from the entry. If the old RDN but not the new RDN are deleted from the entry. If the
deleteoldrdn field is FALSE, the attribute values forming the old RDN deleteoldrdn field is FALSE, the attribute values forming the old RDN
will be retained as non-distinguished attribute values of the entry. will be retained as non-distinguished attribute values of the entry.
The server MUST fail the operation and return an error in the result The server MUST fail the operation and return an error in the result
code if the setting of the deleteoldrdn field would cause a schema code if the setting of the deleteoldrdn field would cause a schema
inconsistency in the entry. inconsistency in the entry.
Lightweight Directory Access Protocol Version 3
Note that X.500 restricts the ModifyDN operation to only affect Note that X.500 restricts the ModifyDN operation to only affect
entries that are contained within a single server. If the LDAP server entries that are contained within a single server. If the LDAP server
is mapped onto DAP, then this restriction will apply, and the is mapped onto DAP, then this restriction will apply, and the
affectsMultipleDSAs result code will be returned if this error affectsMultipleDSAs result code will be returned if this error
occurred. In general, clients MUST NOT expect to be able to perform occurred. In general, clients MUST NOT expect to be able to perform
arbitrary movements of entries and subtrees between servers or arbitrary movements of entries and subtrees between servers or
between naming contexts. between naming contexts.
4.10. Compare Operation 4.10. Compare Operation
skipping to change at line 1680 skipping to change at line 1688
the requested comparison and return the result in the Compare the requested comparison and return the result in the Compare
Response, defined as follows: Response, defined as follows:
CompareResponse ::= [APPLICATION 15] LDAPResult CompareResponse ::= [APPLICATION 15] LDAPResult
The resultCode field is set to compareTrue, compareFalse, or an The resultCode field is set to compareTrue, compareFalse, or an
appropriate error. compareTrue indicates that the assertion value in appropriate error. compareTrue indicates that the assertion value in
the ava field matches a value of the attribute or subtype according the ava field matches a value of the attribute or subtype according
to the attribute's EQUALITY matching rule. compareFalse indicates to the attribute's EQUALITY matching rule. compareFalse indicates
that the assertion value in the ava field and the values of the that the assertion value in the ava field and the values of the
Lightweight Directory Access Protocol Version 3
attribute or subtype did not match. Other result codes indicate attribute or subtype did not match. Other result codes indicate
either that the result of the comparison was Undefined (Section either that the result of the comparison was Undefined (Section
4.5.1), or that some error occurred. 4.5.1), or that some error occurred.
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 interrogated by other means. compared but not interrogated by other means.
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 uncompleted operation. The Abandon Request that the server abandon an uncompleted operation. The Abandon Request
is defined as follows: is defined as follows:
AbandonRequest ::= [APPLICATION 16] MessageID AbandonRequest ::= [APPLICATION 16] MessageID
Lightweight Directory Access Protocol Version 3
The MessageID is that of an operation which was requested earlier in The MessageID is that of an operation which was requested earlier in
this LDAP association. The abandon request itself has its own message this LDAP association. The abandon request itself has its own
id. This is distinct from the id of the earlier operation being MessageID. This is distinct from the MessageID of the earlier
abandoned. operation being abandoned.
There is no response defined in the Abandon operation. Upon receipt There is no response defined in the Abandon operation. Upon receipt
of an AbandonRequest, the server MAY abandon the operation identified of an AbandonRequest, the server MAY abandon the operation identified
by the MessageID. Since the client cannot tell the difference between by the MessageID. Since the client cannot tell the difference between
a successfully abandoned operation and an uncompleted operation, the a successfully abandoned operation and an uncompleted operation, the
application of the Abandon operation is limited to uses where the application of the Abandon operation is limited to uses where the
client does not require an indication of its outcome. client does not require an indication of its outcome.
Abandon, Bind, Unbind, and StartTLS operations cannot be abandoned. Abandon, Bind, Unbind, and StartTLS operations cannot be abandoned.
skipping to change at line 1732 skipping to change at line 1740
Clients should not send abandon requests for the same operation Clients should 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, or are not able to be abandoned). when the abandon was requested, or are not able to be abandoned).
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.
4.12. Extended Operation 4.12. Extended Operation
Lightweight Directory Access Protocol Version 3
The extended operation allows additional operations to be defined for The extended operation allows additional operations to be defined for
services not already available in the protocol. For example, to add services not already available in the protocol. For example, to add
operations to install transport layer security (see Section 4.14). operations to install transport layer security (see Section 4.14).
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. defined in RFCs or be private to particular implementations.
Each extended operation consists of an extended request and an Each extended operation consists of an extended request and an
extended response. extended response.
ExtendedRequest ::= [APPLICATION 23] SEQUENCE { ExtendedRequest ::= [APPLICATION 23] SEQUENCE {
requestName [0] LDAPOID, requestName [0] LDAPOID,
requestValue [1] OCTET STRING OPTIONAL } requestValue [1] OCTET STRING OPTIONAL }
The requestName is a dotted-decimal representation of the unique The requestName is a dotted-decimal representation of the unique
OBJECT IDENTIFIER corresponding to the request. The requestValue is OBJECT IDENTIFIER corresponding to the request. The requestValue is
Lightweight Directory Access Protocol Version 3
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 an The server will respond to this with an LDAPMessage containing an
ExtendedResponse. ExtendedResponse.
ExtendedResponse ::= [APPLICATION 24] SEQUENCE { ExtendedResponse ::= [APPLICATION 24] SEQUENCE {
COMPONENTS OF LDAPResult, COMPONENTS OF LDAPResult,
responseName [10] LDAPOID OPTIONAL, responseName [10] LDAPOID OPTIONAL,
responseValue [11] OCTET STRING OPTIONAL } responseValue [11] OCTET STRING OPTIONAL }
skipping to change at line 1781 skipping to change at line 1787
nor a responseValue and MUST return a resultCode of protocolError. nor a responseValue and MUST return a resultCode of protocolError.
The requestValue and responseValue fields contain any information The requestValue and responseValue fields contain any information
associated with the operation. The format of these fields is defined associated with the operation. The format of these fields is defined
by the specification of the extended operation. Implementations MUST by the specification of the extended operation. Implementations MUST
be prepared to handle arbitrary contents of these fields, including be prepared to handle arbitrary contents of these fields, including
zero bytes. Values that are defined in terms of ASN.1 and BER encoded zero bytes. Values that are defined in terms of ASN.1 and BER encoded
according to Section 5.2, also follow the extensibility rules in according to Section 5.2, also follow the extensibility rules in
Section 4. Section 4.
It is RECOMMENDED that servers list the requestName of extended Servers list the requestName of Extended Requests they recognize in
operations they support in the 'supportedExtension' attribute of the the ' supportedExtension ' attribute in the root DSE (Section 5.1 of
root DSE [Models]. [Models]).
Extended operations may be specified in other documents. The Extended operations may be specified in other documents. The
specification of an extended operation consists of: specification of an extended operation consists of:
- the OBJECT IDENTIFIER assigned to the requestName, - the OBJECT IDENTIFIER assigned to the requestName,
Lightweight Directory Access Protocol Version 3
- the OBJECT IDENTIFIER (if any) assigned to the responseName (note - the OBJECT IDENTIFIER (if any) assigned to the responseName (note
that the same OBJECT IDENTIFIER my be used for both the that the same OBJECT IDENTIFIER my be used for both the
requestName and responseName), requestName and responseName),
- the format of the contents of the requestValue and responseValue - the format of the contents of the requestValue and responseValue
(if any), and (if any), and
- the semantics of the operation. - the semantics of the operation.
4.13. IntermediateResponse Message 4.13. IntermediateResponse Message
While the Search operation provides a mechanism to return multiple While the Search operation provides a mechanism to return multiple
response messages for a single search request, other operations, by response messages for a single search request, other operations, by
nature, do not provide for multiple response messages. nature, do not provide for multiple response messages.
Lightweight Directory Access Protocol Version 3
The IntermediateResponse message provides a general mechanism for The IntermediateResponse message provides a general mechanism for
defining single-request/multiple-response operations in LDAP. This defining single-request/multiple-response operations in LDAP. This
message is intended to be used in conjunction with the extended message is intended to be used in conjunction with the extended
operation to define new single-request/multiple-response operations operation to define new single-request/multiple-response operations
or in conjunction with a control when extending existing LDAP or in conjunction with a control when extending existing LDAP
operations in a way that requires them to return intermediate operations in a way that requires them to return intermediate
response information. response information.
It is intended that the definitions and descriptions of extended It is intended that the definitions and descriptions of extended
operations and controls that make use of the IntermediateResponse operations and controls that make use of the IntermediateResponse
skipping to change at line 1843 skipping to change at line 1848
- the OBJECT IDENTIFIER (if any) assigned to the responseName, - the OBJECT IDENTIFIER (if any) assigned to the responseName,
- the format of the contents of the responseValue, and - the format of the contents of the responseValue, and
- the semantics associated with the IntermediateResponse message. - the semantics associated with the IntermediateResponse message.
Extensions that allow the return of multiple types of Extensions that allow the return of multiple types of
IntermediateResponse messages SHALL identify those types using unique IntermediateResponse messages SHALL identify those types using unique
responseName values (note that one of these may specify no value). responseName values (note that one of these may specify no value).
Lightweight Directory Access Protocol Version 3
Sections 4.13.1 and 4.13.2 describe additional requirements on the Sections 4.13.1 and 4.13.2 describe additional requirements on the
inclusion of responseName and responseValue in IntermediateResponse inclusion of responseName and responseValue in IntermediateResponse
messages. messages.
4.13.1. Usage with LDAP ExtendedRequest and ExtendedResponse 4.13.1. Usage with LDAP ExtendedRequest and ExtendedResponse
A single-request/multiple-response operation may be defined using a A single-request/multiple-response operation may be defined using a
single ExtendedRequest message to solicit zero or more single ExtendedRequest message to solicit zero or more
IntermediateResponse messages of one or more kinds followed by an IntermediateResponse messages of one or more kinds followed by an
ExtendedResponse message. ExtendedResponse message.
4.13.2. Usage with LDAP Request Controls 4.13.2. Usage with LDAP Request Controls
A control's semantics may include the return of zero or more A control's semantics may include the return of zero or more
IntermediateResponse messages prior to returning the final result IntermediateResponse messages prior to returning the final result
Lightweight Directory Access Protocol Version 3
code for the operation. One or more kinds of IntermediateResponse code for the operation. One or more kinds of IntermediateResponse
messages may be sent in response to a request control. messages may be sent in response to a request control.
All IntermediateResponse messages associated with request controls All IntermediateResponse messages associated with request controls
SHALL include a responseName. This requirement ensures that the SHALL include a responseName. This requirement ensures that the
client can correctly identify the source of IntermediateResponse client can correctly identify the source of IntermediateResponse
messages when: messages when:
- two or more controls using IntermediateResponse messages are - two or more controls using IntermediateResponse messages are
included in a request for any LDAP operation or included in a request for any LDAP operation or
skipping to change at line 1894 skipping to change at line 1898
A client requests TLS establishment by transmitting a StartTLS A client requests TLS establishment by transmitting a StartTLS
request PDU to the server. The StartTLS request is defined in terms request PDU to the server. The StartTLS request is defined in terms
of an ExtendedRequest. The requestName is "1.3.6.1.4.1.1466.20037", of an ExtendedRequest. The requestName is "1.3.6.1.4.1.1466.20037",
and the requestValue field is always absent. and the requestValue field is always absent.
The client MUST NOT send any PDUs on this LDAP exchange following The client MUST NOT send any PDUs on this LDAP exchange following
this request until it receives a StartTLS extended response and, in this request until it receives a StartTLS extended response and, in
the case of a successful response, completes TLS negotiations. the case of a successful response, completes TLS negotiations.
Lightweight Directory Access Protocol Version 3
4.14.2. StartTLS Response 4.14.2. StartTLS Response
When a StartTLS request is made, servers supporting the operation When a StartTLS request is made, servers supporting the operation
MUST return a StartTLS response PDU to the requestor. The MUST return a StartTLS response PDU to the requestor. The
responseName is also "1.3.6.1.4.1.1466.20037", and the responseValue responseName, if present, is also "1.3.6.1.4.1.1466.20037". The
field is absent. responseValue is absent.
The server provides a resultCode field to either success or one of The server provides a resultCode field to either success or one of
the other values outlined in Section 4.14.2.2. the other values outlined in Section 4.14.2.2.
4.14.2.1. "Success" Response 4.14.2.1. "Success" Response
If the StartTLS Response contains a resultCode of success, this If the StartTLS Response contains a resultCode of success, this
indicates that the server is willing and able to negotiate TLS. Refer indicates that the server is willing and able to negotiate TLS. Refer
to Section 4 of [AuthMeth] for details. to Section 4 of [AuthMeth] for details.
Lightweight Directory Access Protocol Version 3
4.14.2.2. Response other than "success" 4.14.2.2. Response other than "success"
If the ExtendedResponse contains a result code other than success, If the ExtendedResponse contains a result code other than success,
this indicates that the server is unwilling or unable to negotiate this indicates that the server is unwilling or unable to negotiate
TLS. The following result codes have these meanings for this TLS. The following result codes have these meanings for this
operation: operation:
- operationsError: operations sequencing incorrect; e.g. TLS is - operationsError: operations sequencing incorrect; e.g. TLS is
already established. already established.
skipping to change at line 1944 skipping to change at line 1948
close the connection. close the connection.
The server MUST return unavailable if it supports TLS but cannot The server MUST return unavailable if it supports TLS but cannot
install the TLS layer for some reason, e.g. the certificate server install the TLS layer for some reason, e.g. the certificate server
not responding, it cannot contact its TLS implementation, or if the not responding, it cannot contact its TLS implementation, or if the
server is in process of shutting down. The client may retry the server is in process of shutting down. The client may retry the
StartTLS operation, or it may proceed with any other LDAP operation, StartTLS operation, or it may proceed with any other LDAP operation,
or it may close the connection. or it may close the connection.
4.14.3. Removal of the TLS Layer 4.14.3. Removal of the TLS Layer
Lightweight Directory Access Protocol Version 3
Two forms of TLS layer removal -- graceful and abrupt -- are Two forms of TLS layer removal -- graceful and abrupt -- are
supported. These do not involve LDAP PDUs, but are preformed at the provided. These do not involve LDAP PDUs, but are preformed at the
underlying layers. underlying layers.
If the connection is closed, uncompleted operations are handled as If the connection is closed, uncompleted operations are handled as
specified in Section 5.1. specified in Section 5.1.
4.14.3.1. Graceful Removal 4.14.3.1. Graceful Removal
Either the client or server MAY remove the TLS layer and leave the Either the client or server MAY remove the TLS layer and leave the
LDAP exchange intact by sending and receiving a TLS closure alert. LDAP exchange intact by sending and receiving a TLS closure alert.
The initiating protocol peer sends the TLS closure alert. If it The initiating protocol peer sends the TLS closure alert. If it
wishes to leave the LDAP exchange intact, it then MUST cease to send wishes to leave the LDAP exchange intact, it then MUST cease to send
Lightweight Directory Access Protocol Version 3
further PDUs and MUST ignore any received LDAP PDUs until it receives further PDUs and MUST ignore any received LDAP PDUs until it receives
a TLS closure alert from the other peer. a TLS closure alert from the other peer.
Once the initiating protocol peer receives a TLS closure alert from Once the initiating protocol peer receives a TLS closure alert from
the other peer it MAY send and receive LDAP PDUs. the other peer it MAY send and receive LDAP PDUs.
When a protocol peer receives the initial TLS closure alert, it may When a protocol peer receives the initial TLS closure alert, it may
choose to allow the LDAP exchange to remain intact. In this case, it choose to allow the LDAP exchange to remain intact. In this case, it
MUST immediately transmit a TLS closure alert. Following this, it MAY MUST immediately transmit a TLS closure alert. Following this, it MAY
send and receive LDAP PDUs. send and receive LDAP PDUs.
skipping to change at line 1998 skipping to change at line 2000
5. Protocol Encoding, Connection, and Transfer 5. Protocol Encoding, Connection, and Transfer
This protocol is designed to run over connection-oriented, reliable This protocol is designed to run over connection-oriented, reliable
transports, where the data stream is divided into octets (8-bit transports, where the data stream is divided into octets (8-bit
units), with each octet and each bit being significant. units), with each octet and each bit being significant.
One underlying service, LDAP over TCP, is defined in Section One underlying service, LDAP over TCP, is defined in Section
5.3. This service is generally applicable to applications providing 5.3. This service is generally applicable to applications providing
or consuming X.500-based directory services on the Internet. This or consuming X.500-based directory services on the Internet. This
specification was generally written with the TCP mapping in mind. specification was generally written with the TCP mapping in mind.
Lightweight Directory Access Protocol Version 3
Specifications detailing other mappings may encounter various Specifications detailing other mappings may encounter various
obstacles. obstacles.
Implementations of LDAP over TCP MUST implement the mapping as Implementations of LDAP over TCP MUST implement the mapping as
described in Section 5.3. described in Section 5.3.
This table illustrates the relationship between the different layers This table illustrates the relationship between the different layers
involved in an exchange between two protocol peers: involved in an exchange between two protocol peers:
+---------------+ |
| LDAP exchange | |
+---------------+ > LDAP PDU |
+---------------+ < data |
| SASL layer | |
+---------------+ > SASL-protected data |
+---------------+ < data |
Lightweight Directory Access Protocol Version 3 +---------------+
| LDAP exchange |
| TLS layer | | +---------------+ > LDAP PDUs
+---------------+ > TLS-protected data | Application +---------------+ < data
+---------------+ < data +------------ | SASL layer |
| connection | | Transport +---------------+ > SASL-protected data
+---------------+ < data
| TLS layer |
Application +---------------+ > TLS-protected data
------------+---------------+ < data
Transport | connection |
+---------------+ +---------------+
5.2. Protocol Encoding 5.2. Protocol Encoding
The protocol elements of LDAP SHALL be encoded for exchange using the The protocol elements of LDAP SHALL be encoded for exchange using the
Basic Encoding Rules [BER] of [ASN.1] with the following Basic Encoding Rules [BER] of [ASN.1] with the following
restrictions: restrictions:
- Only the definite form of length encoding is used. - Only the definite form of length encoding is used.
skipping to change at line 2053 skipping to change at line 2056
OCTET STRING values, such as attribute values, unless otherwise OCTET STRING values, such as attribute values, unless otherwise
stated. stated.
5.3. Transmission Control Protocol (TCP) 5.3. Transmission Control Protocol (TCP)
The encoded LDAPMessage PDUs are mapped directly onto the [TCP] The encoded LDAPMessage PDUs are mapped directly onto the [TCP]
bytestream using the BER-based encoding described in Section 5.2. It bytestream using the BER-based encoding described in Section 5.2. It
is recommended that server implementations running over the TCP is recommended that server implementations running over the TCP
provide a protocol listener on the Internet Assigned Numbers provide a protocol listener on the Internet Assigned Numbers
Authority (IANA)-assigned LDAP port, 389 [PortReg]. Servers may Authority (IANA)-assigned LDAP port, 389 [PortReg]. Servers may
Lightweight Directory Access Protocol Version 3
instead provide a listener on a different port number. Clients MUST instead provide a listener on a different port number. Clients MUST
support contacting servers on any valid TCP port. support contacting servers on any valid TCP port.
6. Security Considerations 6. Security Considerations
This version of the protocol provides facilities for simple This version of the protocol provides facilities for simple
authentication using a cleartext password, as well as any [SASL] authentication using a cleartext password, as well as any [SASL]
mechanism. Installing SASL layers can provide integrity and privacy mechanism. Installing SASL layers can provide integrity and other
services. data security services.
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.
Lightweight Directory Access Protocol Version 3
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.
Servers are encouraged to prevent directory modifications by clients Servers are encouraged to prevent directory modifications by clients
that have authenticated anonymously [AuthMeth]. that have authenticated anonymously [AuthMeth].
Security considerations for authentication methods, SASL mechanisms, Security considerations for authentication methods, SASL mechanisms,
and TLS are described in [AuthMeth]. and TLS are described in [AuthMeth].
skipping to change at line 2108 skipping to change at line 2111
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.
Servers may return referrals or search result references which Servers may return referrals or search result references which
redirect clients to peer servers. It is possible for a rogue redirect clients to peer servers. It is possible for a rogue
application to inject such referrals into the data stream in an application to inject such referrals into the data stream in an
attempt to redirect a client to a rogue server. Clients are advised attempt to redirect a client to a rogue server. Clients are advised
to be aware of this, and possibly reject referrals when to be aware of this, and possibly reject referrals when
Lightweight Directory Access Protocol Version 3
confidentiality measures are not in place. Clients are advised to confidentiality measures are not in place. Clients are advised to
reject referrals from the StartTLS operation. reject referrals from the StartTLS operation.
The matchedDN and diagnosticMessage fields, as well as some The matchedDN and diagnosticMessage fields, as well as some
resultCode values (e.g., attributeOrValueExists and resultCode values (e.g., attributeOrValueExists and
entryAlreadyExists), could disclose the presence the specific data in entryAlreadyExists), could disclose the presence the specific data in
the directory which is subject to access and other administrative the directory which is subject to access and other administrative
controls. Server implementations should restrict access to protected controls. Server implementations should restrict access to protected
information equally under both normal and error conditions. information equally under both normal and error conditions.
Protocol peers MUST be prepared to handle invalid and arbitrary Protocol peers MUST be prepared to handle invalid and arbitrary
length protocol encodings. A number of LDAP security advisories are length protocol encodings. Invalid protocol encodings include: BER
available through [CERT]. encoding exceptions, format string and UTF-8 encoding exceptions,
overflow exceptions, integer value exceptions, and binary mode on/off
Lightweight Directory Access Protocol Version 3 flag exceptions. The LDAPv3 PROTOS [PROTOS-LDAP] test suite provides
excellent examples of these exceptions and test cases used to
discover flaws.
7. Acknowledgements 7. Acknowledgements
This document is based on RFC 2251 by Mark Wahl, Tim Howes, and Steve This document is based on RFC 2251 by Mark Wahl, Tim Howes, and Steve
Kille. It is also based on RFC 2830 by Jeff Hodges, RL "Bob" Morgan, Kille. RFC 2251 was a product of the IETF ASID Working Group.
and Mark Wahl. It is also based on RFC 3771 by Roger Harrison, and
Kurt Zeilenga. Notable amounts of technical reviews and content were It is also based on RFC 2830 by Jeff Hodges, RL "Bob" Morgan, and
provided by Kurt Zeilenga, Steven Legg, and Hallvard Furuseth. Their Mark Wahl. RFC 2830 was a product of the IETF LDAPEXT Working Group.
work along with the input of individuals of the IETF ASID, LDAPEXT,
LDUP, LDAPBIS, and other Working Groups is gratefully acknowledged. It is also based on RFC 3771 by Roger Harrison, and Kurt Zeilenga.
RFC 3771 was an individual submission to the IETF.
This document is a product of the LDAPBIS Working Group. Significant
contributors of technical review and content include Kurt Zeilenga,
Steven Legg, and Hallvard Furuseth.
8. Normative References 8. Normative References
[ABNF] Crocker, D. and P. Overell, "Augmented BNF for Syntax [ABNF] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997. Specifications: ABNF", RFC 2234, November 1997.
Lightweight Directory Access Protocol Version 3
[ASN.1] ITU-T Recommendation X.680 (07/2002) | ISO/IEC 8824-1:2002 [ASN.1] ITU-T Recommendation X.680 (07/2002) | ISO/IEC 8824-1:2002
"Information Technology - Abstract Syntax Notation One "Information Technology - Abstract Syntax Notation One
(ASN.1): Specification of basic notation" (ASN.1): Specification of basic notation"
[AuthMeth] Harrison, R., "LDAP: Authentication Methods and Connection [AuthMeth] Harrison, R., "LDAP: Authentication Methods and Connection
Level Security Mechanisms", draft-ietf-ldapbis-authmeth- Level Security Mechanisms", draft-ietf-ldapbis-authmeth-
xx.txt, (a work in progress). xx.txt, (a work in progress).
[BER] ITU-T Rec. X.690 (07/2002) | ISO/IEC 8825-1:2002, [BER] ITU-T Rec. X.690 (07/2002) | ISO/IEC 8825-1:2002,
"Information technology - ASN.1 encoding rules: "Information technology - ASN.1 encoding rules:
skipping to change at line 2176 skipping to change at line 2190
[LDAPIANA] Zeilenga, K., "IANA Considerations for LDAP", draft-ietf- [LDAPIANA] Zeilenga, K., "IANA Considerations for LDAP", draft-ietf-
ldapbis-bcp64-xx.txt, (a work in progress). ldapbis-bcp64-xx.txt, (a work in progress).
[LDAPURL] Smith, M., "LDAP: Uniform Resource Locator", draft-ietf- [LDAPURL] Smith, M., "LDAP: Uniform Resource Locator", draft-ietf-
ldapbis-url-xx.txt, (a work in progress). ldapbis-url-xx.txt, (a work in progress).
[Models] Zeilenga, K., "LDAP: Directory Information Models", draft- [Models] Zeilenga, K., "LDAP: Directory Information Models", draft-
ietf-ldapbis-models-xx.txt (a work in progress). ietf-ldapbis-models-xx.txt (a work in progress).
Lightweight Directory Access Protocol Version 3
[Roadmap] Zeilenga, K., "LDAP: Technical Specification Road Map", [Roadmap] Zeilenga, K., "LDAP: Technical Specification Road Map",
draft-ietf-ldapbis-roadmap-xx.txt (a work in progress). draft-ietf-ldapbis-roadmap-xx.txt (a work in progress).
[SASL] Melnikov, A., "Simple Authentication and Security Layer", [SASL] Melnikov, A., "Simple Authentication and Security Layer",
draft-ietf-sasl-rfc2222bis-xx.txt (a work in progress). draft-ietf-sasl-rfc2222bis-xx.txt (a work in progress).
[SASLPrep] Zeilenga, K., "Stringprep profile for user names and [SASLPrep] Zeilenga, K., "Stringprep profile for user names and
passwords", draft-ietf-sasl-saslprep-xx.txt, (a work in passwords", draft-ietf-sasl-saslprep-xx.txt, (a work in
progress). progress).
[StringPrep] Hoffman P. and M. Blanchet, "Preparation of [StringPrep] Hoffman P. and M. Blanchet, "Preparation of
Internationalized Strings ('stringprep')", draft-hoffman- Internationalized Strings ('stringprep')", draft-hoffman-
rfc3454bis-xx.txt, a work in progress. rfc3454bis-xx.txt, a work in progress.
Lightweight Directory Access Protocol Version 3
[Syntaxes] Legg, S., and K. Dally, "LDAP: Syntaxes and Matching [Syntaxes] Legg, S., and K. Dally, "LDAP: Syntaxes and Matching
Rules", draft-ietf-ldapbis-syntaxes-xx.txt, (a work in Rules", draft-ietf-ldapbis-syntaxes-xx.txt, (a work in
progress). progress).
[TCP] Postel, J., "Transmission Control Protocol", STD7 and RFC [TCP] Postel, J., "Transmission Control Protocol", STD7 and RFC
793, September 1981 793, September 1981
[TLS] Dierks, T. and C. Allen. "The TLS Protocol Version 1.1", [TLS] Dierks, T. and C. Allen. "The TLS Protocol Version 1.1",
draft-ietf-tls-rfc2246-bis-xx.txt, a work in progress. draft-ietf-tls-rfc2246-bis-xx.txt, a work in progress.
skipping to change at line 2227 skipping to change at line 2241
[X.500] ITU-T Rec. X.500, "The Directory: Overview of Concepts, [X.500] ITU-T Rec. X.500, "The Directory: Overview of Concepts,
Models and Service", 1993. Models and Service", 1993.
[X.501] ITU-T Rec. X.501, "The Directory: Models", 1993. [X.501] ITU-T Rec. X.501, "The Directory: Models", 1993.
[X.511] ITU-T Rec. X.511, "The Directory: Abstract Service [X.511] ITU-T Rec. X.511, "The Directory: Abstract Service
Definition", 1993. Definition", 1993.
9. Informative References 9. Informative References
[CERT] The CERT(R) Center, http://www.cert.org [Glossary] The Unicode Consortium, "Unicode Glossary",
<http://www.unicode.org/glossary/>.
[CharModel] Whistler, K. and M. Davis, "Unicode Technical Report
#17, Character Encoding Model", UTR17,
<http://www.unicode.org/unicode/reports/tr17/>, August
2000.
[PROTOS-LDAP] University of Oulu, "PROTOS Test-Suite: c06-ldapv3"
<http://www.ee.oulu.fi/research/ouspg/protos/testing/c06/l
dapv3/>
[PortReg] IANA, "Port Numbers", [PortReg] IANA, "Port Numbers",
http://www.iana.org/assignments/port-numbers http://www.iana.org/assignments/port-numbers
Lightweight Directory Access Protocol Version 3
10. IANA Considerations 10. IANA Considerations
Lightweight Directory Access Protocol Version 3
It is requested that the Internet Assigned Numbers Authority (IANA) It is requested that the Internet Assigned Numbers Authority (IANA)
update the LDAP result code registry to indicate that this document update the LDAP result code registry to indicate that this document
provides the definitive technical specification for result codes 0- provides the definitive technical specification for result codes 0-
36, 48-54, 64-70, 80-90. 36, 48-54, 64-70, 80-90.
It is requested that the IANA update the LDAP Protocol Mechanism It is requested that the IANA update the LDAP Protocol Mechanism
registry to indicate that this document and [AuthMeth] provides the registry to indicate that this document and [AuthMeth] provides the
definitive technical specification for the Start TLS definitive technical specification for the Start TLS
(1.3.6.1.4.1.1466.20037) extended operation. (1.3.6.1.4.1.1466.20037) extended operation.
skipping to change at line 2358 skipping to change at line 2380
mechanism. mechanism.
referral (10) referral (10)
Indicates that a referral needs to be chased to complete the Indicates that a referral needs to be chased to complete the
operation (see Section 4.1.10). operation (see Section 4.1.10).
adminLimitExceeded (11) adminLimitExceeded (11)
Indicates that an administrative limit has been exceeded. Indicates that an administrative limit has been exceeded.
unavailableCriticalExtension (12) unavailableCriticalExtension (12)
Indicates that the server is unable or unwilling to perform a Indicates a critical control is unrecognized (see Section
critical control (see Section 4.1.11). 4.1.11).
confidentialityRequired (13) confidentialityRequired (13)
Indicates that data confidentiality protections are required. Indicates that data confidentiality protections are required.
saslBindInProgress (14) saslBindInProgress (14)
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
Indicates the server requires the client to send a new bind Indicates the server requires the client to send a new bind
request, with the same SASL mechanism, to continue the request, with the same SASL mechanism, to continue the
authentication process (see Section 4.2). authentication process (see Section 4.2).
noSuchAttribute (16) noSuchAttribute (16)
Indicates that the named entry does not contain the specified Indicates that the named entry does not contain the specified
attribute or attribute value. attribute or attribute value.
skipping to change at line 2495 skipping to change at line 2516
other (80) other (80)
Indicates the server has encountered an internal error. Indicates the server has encountered an internal error.
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
Appendix B - Complete ASN.1 Definition Appendix B - Complete ASN.1 Definition
This appendix is normative. This appendix is normative.
Lightweight-Directory-Access-Protocol-V3 Lightweight-Directory-Access-Protocol-V3
-- Copyright (C) The Internet Society (2003). This version of -- Copyright (C) The Internet Society (2004). This version of
-- this ASN.1 module is part of RFC XXXX; see the RFC itself -- this ASN.1 module is part of RFC XXXX; see the RFC itself
-- for full legal notices. -- for full legal notices.
DEFINITIONS DEFINITIONS
IMPLICIT TAGS IMPLICIT TAGS
EXTENSIBILITY IMPLIED ::= EXTENSIBILITY IMPLIED ::=
BEGIN BEGIN
LDAPMessage ::= SEQUENCE { LDAPMessage ::= SEQUENCE {
messageID MessageID, messageID MessageID,
skipping to change at line 3103 skipping to change at line 3116
responses to any request message received before the TLS closure. responses to any request message received before the TLS closure.
C.3 Changes made to RFC 3771: C.3 Changes made to RFC 3771:
- In general, all technical language was transferred in whole. - In general, all technical language was transferred in whole.
Supporting and background language seen as redundant due to its Supporting and background language seen as redundant due to its
presence in this document was omitted. presence in this document was omitted.
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
IPR Disclosure Acknowledgement Intellectual Property Statement
By submitting this Internet-Draft, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668.
IPR Notice
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the IETF's procedures with respect to rights in IETF Documents can on the IETF's procedures with respect to rights in IETF Documents can
be found in BCP 78 and BCP 79. be found in BCP 78 and BCP 79.
skipping to change at line 3134 skipping to change at line 3140
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org." ipr@ietf.org."
Copyright Notice Copyright Statement
Copyright (C) The Internet Society 1994.
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights." retain all their rights.
Disclaimer Disclaimer of Validity
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 

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