draft-ietf-ldapbis-protocol-20.txt   draft-ietf-ldapbis-protocol-21.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-20.txt Jan 2004 Document: draft-ietf-ldapbis-protocol-21.txt Jan 2004
Obsoletes: RFC 2251, 2830 Obsoletes: RFC 2251, 2830, [LIMR]
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 in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that other
skipping to change at line 65 skipping to change at line 65
4.1.3. Distinguished Name and Relative Distinguished Name..........6 4.1.3. Distinguished Name and Relative Distinguished Name..........6
4.1.4. Attribute Descriptions......................................7 4.1.4. Attribute Descriptions......................................7
4.1.5. Attribute Value.............................................7 4.1.5. Attribute Value.............................................7
4.1.6. Attribute Value Assertion...................................7 4.1.6. Attribute Value Assertion...................................7
4.1.7. Attribute and PartialAttribute..............................8 4.1.7. Attribute and PartialAttribute..............................8
4.1.8. Matching Rule Identifier....................................8 4.1.8. Matching Rule Identifier....................................8
4.1.9. Result Message..............................................8 4.1.9. Result Message..............................................8
4.1.10. Referral..................................................10 4.1.10. Referral..................................................10
4.1.11. Controls..................................................11 4.1.11. Controls..................................................11
4.2. Bind Operation...............................................12 4.2. Bind Operation...............................................13
4.3. Unbind Operation.............................................15 4.3. Unbind Operation.............................................16
4.4. Unsolicited Notification.....................................15 4.4. Unsolicited Notification.....................................16
4.5. Search Operation.............................................17 4.5. Search Operation.............................................17
4.6. Modify Operation.............................................25 4.6. Modify Operation.............................................26
4.7. Add Operation................................................27 4.7. Add Operation................................................27
4.8. Delete Operation.............................................28 4.8. Delete Operation.............................................28
4.9. Modify DN Operation..........................................28 4.9. Modify DN Operation..........................................28
4.10. Compare Operation...........................................29 4.10. Compare Operation...........................................30
4.11. Abandon Operation...........................................30 4.11. Abandon Operation...........................................30
4.12. Extended Operation..........................................31 4.12. Extended Operation..........................................31
4.13. StartTLS Operation..........................................32 4.13. IntermediateResponse Message................................32
5. Protocol Element Encodings and Transfer........................34 4.13.1. Usage with LDAP ExtendedRequest and ExtendedResponse......33
5.1. Protocol Encoding............................................34 4.13.2. Usage with LDAP Request Controls..........................34
5.2. Transfer Protocols...........................................35 4.14. StartTLS Operation..........................................34
6. Security Considerations........................................35 5. Protocol Element Encodings and Transfer........................36
7. Acknowledgements...............................................36 5.1. Protocol Encoding............................................37
8. Normative References...........................................36 5.2. Transfer Protocols...........................................37
9. Informative References.........................................38 6. Security Considerations........................................37
10. IANA Considerations...........................................38 7. Acknowledgements...............................................39
11. Editor's Address..............................................38 8. Normative References...........................................39
Appendix A - LDAP Result Codes....................................39 9. Informative References.........................................40
A.1 Non-Error Result Codes........................................39 10. IANA Considerations...........................................41
A.2 Result Codes..................................................39 11. Editor's Address..............................................41
Appendix B - Complete ASN.1 Definition............................43 Appendix A - LDAP Result Codes....................................42
Appendix C - Changes..............................................49 A.1 Non-Error Result Codes........................................42
C.1 Changes made to made to RFC 2251:.............................49 A.2 Result Codes..................................................42
C.2 Changes made to made to RFC 2830:.............................54 Appendix B - Complete ASN.1 Definition............................46
Appendix C - Changes..............................................52
C.1 Changes made to made to RFC 2251:.............................52
C.2 Changes made to made to RFC 2830:.............................57
C.3 Changes made to made to [LIMR]:...............................58
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.
Sermersheim Internet-Draft - Expires Jul 2004 Page 2
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.
Sermersheim Internet-Draft - Expires Jul 2004 Page 2
Lightweight Directory Access Protocol Version 3
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.
This document obsoletes all of RFC 2251 except the following: This document obsoletes all of RFC 2251 except the following:
Sections 3.2, 3.4, 4.1.3 (last paragraph), 4.1.4, 4.1.5, 4.1.5.1, Sections 3.2, 3.4, 4.1.3 (last paragraph), 4.1.4, 4.1.5, 4.1.5.1,
4.1.9 (last paragraph), 5.1, 6.1, and 6.2 (last paragraph) are 4.1.9 (last paragraph), 5.1, 6.1, and 6.2 (last paragraph) are
obsoleted by [Models]. obsoleted by [Models].
Section 3.3 is obsoleted by [Roadmap]. Section 3.3 is obsoleted by [Roadmap].
Sections 4.2.1 (portions), and 4.2.2 are obsoleted by [AuthMeth]. Sections 4.2.1 (portions), and 4.2.2 are obsoleted by [AuthMeth].
Appendix C.1 summarizes substantive changes to the remaining Appendix C.1 summarizes substantive changes to the remaining
sections. sections.
This document also obsoletes RFC 2830, Sections 2 and 4 in entirety. This document obsoletes RFC 2830, Sections 2 and 4 in entirety. The
The remainder of RFC 2830 is obsoleted by [AuthMeth]. Appendix C.2 remainder of RFC 2830 is obsoleted by [AuthMeth]. Appendix C.2
summarizes substantive changes to the remaining sections. summarizes substantive changes to the remaining sections.
This document also obsoletes [LIMR] in entrirety.
<<Note to RFC Editor: [LIMR] is to be replaced with the RFC
number assigned to draft-rharrison-ldap-intermediate-resp-
xx.txt, an RFC-to-be.>>
2. Conventions 2. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", and "MAY" in this document are "SHOULD", "SHOULD NOT", "RECOMMENDED", and "MAY" in this document are
to be interpreted as described in [Keyword]. to be interpreted as described in [Keyword].
The terms "connection" and "LDAP connection" both refer to the The terms "connection" and "LDAP connection" both refer to the
underlying transport protocol connection between two protocol peers. underlying transport protocol connection between two protocol peers.
The term "TLS connection" refers to a [TLS]-protected LDAP The term "TLS connection" refers to a [TLS]-protected LDAP
skipping to change at line 154 skipping to change at line 163
The terms "association" and "LDAP association" both refer to the The terms "association" and "LDAP association" both refer to the
association of the LDAP connection and its current authentication and association of the LDAP connection and its current authentication and
authorization state. authorization state.
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
Sermersheim Internet-Draft - Expires Jul 2004 Page 3
Lightweight Directory Access Protocol Version 3
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.
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, provided the
Sermersheim Internet-Draft - Expires Jul 2004 Page 3
Lightweight Directory Access Protocol Version 3
client eventually receives a response for every request that requires client eventually receives a response for every request that requires
one. 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.
skipping to change at line 209 skipping to change at line 218
Specific Entry) [Models]. Specific Entry) [Models].
4.1. Common Elements 4.1. Common Elements
This section describes the LDAPMessage envelope Protocol Data Unit This section describes the LDAPMessage envelope Protocol Data Unit
(PDU) format, as well as data type definitions, which are used in the (PDU) format, as well as data type definitions, which are used in the
protocol operations. protocol operations.
4.1.1. Message Envelope 4.1.1. Message Envelope
Sermersheim Internet-Draft - Expires Jul 2004 Page 4
Lightweight Directory Access Protocol Version 3
For the purposes of protocol exchanges, all protocol operations are For the purposes of protocol exchanges, all protocol operations are
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,
Sermersheim Internet-Draft - Expires Jul 2004 Page 4
Lightweight Directory Access Protocol Version 3
unbindRequest UnbindRequest, unbindRequest UnbindRequest,
searchRequest SearchRequest, searchRequest SearchRequest,
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,
modDNResponse ModifyDNResponse, modDNResponse ModifyDNResponse,
compareRequest CompareRequest, compareRequest CompareRequest,
compareResponse CompareResponse, compareResponse CompareResponse,
abandonRequest AbandonRequest, abandonRequest AbandonRequest,
extendedReq ExtendedRequest, extendedReq ExtendedRequest,
extendedResp ExtendedResponse, extendedResp ExtendedResponse,
intermediateResponse IntermediateResponse
... }, ... },
controls [0] Controls OPTIONAL } controls [0] Controls OPTIONAL }
MessageID ::= INTEGER (0 .. maxInt) MessageID ::= INTEGER (0 .. maxInt)
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
skipping to change at line 267 skipping to change at line 276
incorrect, then the server SHOULD return the Notice of Disconnection incorrect, then the server SHOULD return the Notice of Disconnection
described in Section 4.4.1, with the resultCode set to protocolError, described in Section 4.4.1, with the resultCode set to protocolError,
and MUST immediately close the connection. and MUST immediately close the connection.
In other cases where the client or server cannot parse a PDU, it In other cases where the client or server cannot parse a PDU, it
SHOULD abruptly close the connection where further communication SHOULD abruptly close the connection where further communication
(including providing notice) would be pernicious. Otherwise, server (including providing notice) would be pernicious. Otherwise, server
implementations MUST return an appropriate response to the request, implementations MUST return an appropriate response to the request,
with the resultCode set to protocolError. with the resultCode set to protocolError.
Sermersheim Internet-Draft - Expires Jul 2004 Page 5
Lightweight Directory Access Protocol Version 3
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 requests outstanding in the LDAP association the values of any other requests outstanding in the LDAP association
Sermersheim Internet-Draft - Expires Jul 2004 Page 5
Lightweight Directory Access Protocol Version 3
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.
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,
skipping to change at line 321 skipping to change at line 329
For example, For example,
1.3.6.1.4.1.1466.1.2.3 1.3.6.1.4.1.1466.1.2.3
4.1.3. Distinguished Name and Relative Distinguished Name 4.1.3. Distinguished Name and Relative Distinguished Name
An LDAPDN is defined to be the representation of a Distinguished Name An LDAPDN is defined to be the representation of a Distinguished Name
(DN) after encoding according to the specification in [LDAPDN]. (DN) after encoding according to the specification in [LDAPDN].
LDAPDN ::= LDAPString LDAPDN ::= LDAPString
Sermersheim Internet-Draft - Expires Jul 2004 Page 6
Lightweight Directory Access Protocol Version 3
-- 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]
Sermersheim Internet-Draft - Expires Jul 2004 Page 6
Lightweight Directory Access Protocol Version 3
4.1.4. Attribute Descriptions 4.1.4. Attribute Descriptions
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]
skipping to change at line 374 skipping to change at line 383
Clients MUST only send attribute values in a request that are valid Clients MUST only send attribute values in a request that are valid
according to the syntax defined for the attributes. according to the syntax defined for the attributes.
4.1.6. Attribute Value Assertion 4.1.6. Attribute Value Assertion
The AttributeValueAssertion (AVA) type definition is similar to the The AttributeValueAssertion (AVA) type definition is similar to the
one in the X.500 Directory standards. It contains an attribute one in the X.500 Directory standards. It contains an attribute
description and a matching rule ([Models Section 4.1.3) assertion description and a matching rule ([Models Section 4.1.3) assertion
value suitable for that type. Elements of this type are typically value suitable for that type. Elements of this type are typically
Sermersheim Internet-Draft - Expires Jul 2004 Page 7
Lightweight Directory Access Protocol Version 3
used to assert that the value in assertionValue matches a value of an used to assert that the value in assertionValue matches a value of an
attribute. attribute.
AttributeValueAssertion ::= SEQUENCE { AttributeValueAssertion ::= SEQUENCE {
attributeDesc AttributeDescription, attributeDesc AttributeDescription,
assertionValue AssertionValue } assertionValue AssertionValue }
AssertionValue ::= OCTET STRING AssertionValue ::= OCTET STRING
Sermersheim Internet-Draft - Expires Jul 2004 Page 7
Lightweight Directory Access Protocol Version 3
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
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
skipping to change at line 429 skipping to change at line 439
MatchingRuleId ::= LDAPString MatchingRuleId ::= LDAPString
4.1.9. Result Message 4.1.9. Result Message
The LDAPResult is the construct used in this protocol to return The LDAPResult is the construct used in this protocol to return
success or failure indications from servers to clients. To various success or failure indications from servers to clients. To various
requests, servers will return responses of LDAPResult or responses requests, servers will return responses of LDAPResult or responses
containing the components of LDAPResult to indicate the final status containing the components of LDAPResult to indicate the final status
of a protocol operation request. of a protocol operation request.
Sermersheim Internet-Draft - Expires Jul 2004 Page 8
Lightweight Directory Access Protocol Version 3
LDAPResult ::= SEQUENCE { LDAPResult ::= SEQUENCE {
resultCode ENUMERATED { resultCode ENUMERATED {
success (0), success (0),
operationsError (1), operationsError (1),
protocolError (2), protocolError (2),
timeLimitExceeded (3), timeLimitExceeded (3),
sizeLimitExceeded (4), sizeLimitExceeded (4),
compareFalse (5), compareFalse (5),
compareTrue (6), compareTrue (6),
Sermersheim Internet-Draft - Expires Jul 2004 Page 8
Lightweight Directory Access Protocol Version 3
authMethodNotSupported (7), authMethodNotSupported (7),
strongAuthRequired (8), strongAuthRequired (8),
-- 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),
skipping to change at line 486 skipping to change at line 495
objectClassModsProhibited (69), objectClassModsProhibited (69),
-- 70 reserved for CLDAP -- -- 70 reserved for CLDAP --
affectsMultipleDSAs (71), affectsMultipleDSAs (71),
-- 72-79 unused -- -- 72-79 unused --
other (80), other (80),
... }, ... },
matchedDN LDAPDN, matchedDN LDAPDN,
diagnosticMessage LDAPString, diagnosticMessage LDAPString,
referral [3] Referral OPTIONAL } referral [3] Referral OPTIONAL }
Sermersheim Internet-Draft - Expires Jul 2004 Page 9
Lightweight Directory Access Protocol Version 3
The resultCode enumeration is extensible as defined in Section 3.6 of The resultCode enumeration is extensible as defined in Section 3.6 of
[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
Sermersheim Internet-Draft - Expires Jul 2004 Page 9
Lightweight Directory Access Protocol Version 3
standardized, implementations MUST NOT rely on the values returned. standardized, implementations MUST NOT rely on the values returned.
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
skipping to change at line 543 skipping to change at line 551
-- URIs -- URIs
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.
Clients that follow referrals MUST ensure that they do not loop Clients that follow referrals MUST ensure that they do not loop
between servers. They MUST NOT repeatedly contact the same server for between servers. They MUST NOT repeatedly contact the same server for
the same request with the same target entry name, scope and filter. the same request with the same target entry name, scope and filter.
Sermersheim Internet-Draft - Expires Jul 2004 Page 10
Lightweight Directory Access Protocol Version 3
Some clients use a counter that is incremented each time referral Some clients use a counter that is incremented each time referral
handling occurs for an operation, and these kinds of clients MUST be handling occurs for an operation, and these kinds of clients MUST be
able to handle at least ten nested referrals between the root and a able to handle at least ten nested referrals between the root and a
leaf entry. 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:
Sermersheim Internet-Draft - Expires Jul 2004 Page 10
Lightweight Directory Access Protocol Version 3
- 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
appearing in the string representation of a DN or search filter appearing in the string representation of a DN or search filter
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.
skipping to change at line 586 skipping to change at line 595
is used by the client to progress the operation. is used by the client to progress the operation.
- Other aspects of the new request may be the same as or different - Other aspects of the new request may be the same as or different
from the request which generated the referral. from the request which generated the referral.
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.1.11. Controls 4.1.11. Controls
A control is a way to specify extension information for an LDAP Controls provide a mechanism whereby the semantics and arguments of
message. A control only alters the semantics of the message it is existing LDAP operations may be extended. One or more controls may be
attached to. attached to a single LDAP message. A control only affects the
semantics of the message it is attached to.
Controls sent by clients are termed 'request controls' and those sent
by servers are termed 'response controls'.
When an extension calls for a particular response control to be sent
in response to a request control, the response and request controls
are termed to be "paired".
Controls ::= SEQUENCE OF control Control Controls ::= SEQUENCE OF control Control
Sermersheim Internet-Draft - Expires Jul 2004 Page 11
Lightweight Directory Access Protocol Version 3
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 UTF-8 encoded dotted-decimal The controlType field is the dotted-decimal representation of an
representation of an OBJECT IDENTIFIER which uniquely identifies the OBJECT IDENTIFIER which uniquely identifies the control, or the
control, or the request control and its paired response control. This request control and its paired response control. This provides
prevents conflicts between control names. unambiguous naming of controls.
The criticality field is either TRUE or FALSE and only applies to
request messages (except unbindRequest). For response messages and
unbindRequest, the criticality field SHOULD be FALSE, and is ignored
by the receiving protocol peer.
Sermersheim Internet-Draft - Expires Jul 2004 Page 11 The criticality field only has meaning in controls attached to
Lightweight Directory Access Protocol Version 3 request messages (except unbindRequest). For controls attached to
response messages and the unbindRequest, the criticality field SHOULD
be FALSE, and MUST be ignored by the receiving protocol peer. A value
of TRUE indicates that it is unacceptable to perform the operation
without applying the semantics of the control and FALSE otherwise.
Specifically, the criticality field is applied as follows:
If the server recognizes the control type and it is appropriate for - Regardless of the value of the criticality field, if the server
the operation, the server will make use of the control when recognizes the control type and it is appropriate for the
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, the appropriate for the operation, and the criticality field is TRUE,
server MUST NOT perform the operation, and for operations that have a the server MUST NOT perform the operation, and for operations that
response, MUST return unavailableCriticalExtension in the resultCode. have a response message, MUST return unavailableCriticalExtension
in the resultCode.
If the control is unrecognized or inappropriate but the criticality - If the server does not recognize the control type or it is not
field is FALSE, the server MUST ignore the control. appropriate for the operation, and the criticality field is FALSE,
the server MUST ignore the control.
The controlValue contains any information associated with the The controlValue may contain information associated with the
control. Its format is defined by the specification of the control. controlType. Its format is defined by the specification of the
Implementations MUST be prepared to handle arbitrary contents of the control. Implementations MUST be prepared to handle arbitrary
controlValue octet string, including zero bytes. It is absent only if contents of the controlValue octet string, including zero bytes. It
there is no value information which is associated with a control of is absent only if there is no value information which is associated
its type. controlValues that are defined in terms of ASN.1 and BER with a control of its type. When a controlValue is defined in terms
encoded according to Section 5.1, also follow the extensibility rules of ASN.1, and BER encoded according to Section 5.1, it also follows
in Section 4. the extensibility rules in Section 4.
Servers list the controlType of all request controls they recognize Servers list the controlType of all request controls they recognize
in the supportedControl attribute in the root DSE (Section 5.1 of in 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. In the absence of combination specification most recently published. In the absence of combination
semantics, the behavior of the operation is undefined. semantics, the behavior of the operation is undefined.
Additionally, unless order-dependent semantics are given in a Additionally, unless order-dependent semantics are given in a
specification, the order of a combination of controls in the SEQUENCE specification, the order of a combination of controls in the SEQUENCE
is ignored. is ignored.
Sermersheim Internet-Draft - Expires Jul 2004 Page 12
Lightweight Directory Access Protocol Version 3
This document does not specify any controls. Controls may be This document does not specify any controls. Controls may be
specified in other documents. The specification of a control consists specified in other documents. Documents detailing control extensions
of: are to provide for each control:
- the OBJECT IDENTIFIER assigned to the control, - the OBJECT IDENTIFIER assigned to the control,
- whether the criticality field should be always set to TRUE, always - direction as to what value the sender should provide for the
set to FALSE, or sender's choice, and server behavior when criticality field (note: the semantics of the criticality field
constraints of this nature are violated, are defined above should not be altered by the control's
specification),
- whether there is information associated with the control, and if - whether information is to be present in the controlValue field,
so, the format of the controlValue contents, and if so, the format of the controlValue contents,
- 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
Sermersheim Internet-Draft - Expires Jul 2004 Page 12
Lightweight Directory Access Protocol Version 3
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.
Authentication and security-related semantics of this operation are Authentication and security-related semantics of this operation are
given in [AuthMeth]. given in [AuthMeth].
The Bind Request is defined as follows: The Bind Request is defined as follows:
BindRequest ::= [APPLICATION 0] SEQUENCE { BindRequest ::= [APPLICATION 0] SEQUENCE {
version INTEGER (1 .. 127), version INTEGER (1 .. 127),
skipping to change at line 699 skipping to change at line 722
Fields of the Bind Request are: Fields of the Bind Request are:
- version: A version number indicating the version of the protocol - version: A version number indicating the version of the protocol
to be used in this 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.
Sermersheim Internet-Draft - Expires Jul 2004 Page 13
Lightweight Directory Access Protocol Version 3
- 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
5.1) or when using Simple Authentication and Security Layer [SASL] 5.1) or when using Simple Authentication and Security Layer [SASL]
authentication ([AuthMeth] Section 3.3.2). Server behavior is authentication ([AuthMeth] Section 3.3.2). Server behavior is
undefined when the name is a null value, simple authentication is undefined when the name is a null value, simple authentication is
used, and a non-null password is specified. Where the server used, and a non-null password is specified. 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.
skipping to change at line 720 skipping to change at line 746
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.
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]
Sermersheim Internet-Draft - Expires Jul 2004 Page 13
Lightweight Directory Access Protocol Version 3
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 use of this authentication information when Authorization is the use of this authentication information when
performing operations. Authorization MAY be affected by factors performing operations. Authorization MAY be affected by factors
outside of the LDAP Bind Request, such as those provided by lower outside of the LDAP Bind Request, such as those provided by lower
layer security services. layer security services.
4.2.1. Processing of the Bind Request 4.2.1. Processing of the Bind Request
skipping to change at line 754 skipping to change at line 776
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
connection, it may close the connection, reopen it and begin again by connection, it may close the connection, reopen it and begin again by
first sending a PDU with a Bind Request. This will aid in 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 a connection to change the Clients may send multiple Bind Requests on a connection to change the
authentication and/or security associations or to complete a multi- authentication and/or security associations or to complete a multi-
stage bind process. Authentication from earlier binds is subsequently stage bind process. Authentication from earlier binds is subsequently
ignored. ignored.
Sermersheim Internet-Draft - Expires Jul 2004 Page 14
Lightweight Directory Access Protocol Version 3
For some SASL authentication mechanisms, it may be necessary for the For some SASL authentication mechanisms, it may be necessary for the
client to invoke the BindRequest multiple times. This is indicated by client to invoke the BindRequest multiple times. This is indicated by
the server sending a BindResponse with the resultCode set to the server sending a BindResponse with the resultCode set to
saslBindInProgress. This indicates that the server requires the saslBindInProgress. This indicates that the server requires the
client to send a new bind request, with the same sasl mechanism, to client to send a new bind request, with the same sasl mechanism, to
continue the authentication process. Clients MUST NOT invoke continue the authentication process. Clients MUST NOT invoke
operations between two Bind Requests made as part of a multi-stage operations between two Bind Requests made as part of a multi-stage
bind. 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
skipping to change at line 778 skipping to change at line 803
empty string, the server MUST return a BindResponse with empty string, the server MUST return a BindResponse with
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.
A failed Bind Operation has the effect of placing the connection in A failed Bind Operation has the effect of placing the connection in
an anonymous state. an anonymous state.
4.2.2. Bind Response 4.2.2. Bind Response
Sermersheim Internet-Draft - Expires Jul 2004 Page 14
Lightweight Directory Access Protocol Version 3
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,
serverSaslCreds [7] OCTET STRING OPTIONAL } serverSaslCreds [7] OCTET STRING OPTIONAL }
BindResponse consists simply of an indication from the server of the BindResponse consists simply of an indication from the server of the
status of the client's request for authentication. status of the client's request for authentication.
A successful bind operation is indicated by a BindResponse with a A successful bind operation is indicated by a BindResponse with a
skipping to change at line 811 skipping to change at line 833
is beyond the scope of this document. Clients which are unable or is beyond the scope of this document. Clients which are unable or
unwilling to proceed SHOULD drop the underlying connection. unwilling to proceed SHOULD drop the underlying 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.
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.
Sermersheim Internet-Draft - Expires Jul 2004 Page 15
Lightweight Directory Access Protocol Version 3
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 connection. The Unbind operation is not the association and 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
other peer, and MUST close the connection. Outstanding operations are other peer, and MUST close the connection. Outstanding operations are
handled as specified in Section 5.2. handled as specified in Section 5.2.
4.4. Unsolicited Notification 4.4. Unsolicited Notification
Sermersheim Internet-Draft - Expires Jul 2004 Page 15
Lightweight Directory Access Protocol Version 3
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 connection between the client and the server. The server or in the connection between the client and the server. The
notification is of an advisory nature, and the server will not expect notification is of an advisory nature, and the server will not expect
any response to be returned from the client. any response to be returned from the client.
The unsolicited notification is structured as an LDAPMessage in which The unsolicited notification is structured as an LDAPMessage in which
the messageID is zero and protocolOp is of the extendedResp form (See the messageID is zero and protocolOp is of the extendedResp form (See
Section 4.12). The responseName field of the ExtendedResponse always Section 4.12). The responseName field of the ExtendedResponse always
skipping to change at line 865 skipping to change at line 887
- 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
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
Sermersheim Internet-Draft - Expires Jul 2004 Page 16
Lightweight Directory Access Protocol Version 3
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. Outstanding operations are handled as requested by the client. Outstanding operations are handled as
specified in Section 5.2. specified in Section 5.2.
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 response field is
absent, and the resultCode is used to indicate the reason for the 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
skipping to change at line 887 skipping to change at line 913
- protocolError: The server has received data from the client in - protocolError: The server has received data from the client in
which the LDAPMessage structure could not be parsed. which the LDAPMessage structure could not be parsed.
- strongAuthRequired: The server has detected that an established - strongAuthRequired: The server has detected that an established
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 connections, and be unavailable for an operations on all existing connections, and be unavailable for an
Sermersheim Internet-Draft - Expires Jul 2004 Page 16
Lightweight Directory Access Protocol Version 3
extended period of time. The client may make use of an alternative extended period of time. The client may make use of an alternative
server. server.
Upon transmission of the Notice of Disconnection, the server is to Upon transmission of the Notice of Disconnection, the server is to
consider the LDAP association terminated, MUST cease transmission of consider the LDAP association terminated, MUST cease transmission of
messages to the client, and MUST close the connection. messages to the client, and MUST close the connection.
4.5. Search Operation 4.5. Search Operation
The Search Operation is used to request a server to return, subject The Search Operation is used to request a server to return, subject
skipping to change at line 921 skipping to change at line 943
baseObject LDAPDN, baseObject LDAPDN,
scope ENUMERATED { scope ENUMERATED {
baseObject (0), baseObject (0),
singleLevel (1), singleLevel (1),
wholeSubtree (2) }, wholeSubtree (2) },
derefAliases ENUMERATED { derefAliases ENUMERATED {
neverDerefAliases (0), neverDerefAliases (0),
derefInSearching (1), derefInSearching (1),
derefFindingBaseObj (2), derefFindingBaseObj (2),
derefAlways (3) }, derefAlways (3) },
Sermersheim Internet-Draft - Expires Jul 2004 Page 17
Lightweight Directory Access Protocol Version 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 selection LDAPString AttributeSelection ::= SEQUENCE OF selection LDAPString
-- constrained to <attributeSelection> below -- constrained to <attributeSelection> below
Filter ::= CHOICE { Filter ::= CHOICE {
skipping to change at line 943 skipping to change at line 969
not [2] Filter, not [2] Filter,
equalityMatch [3] AttributeValueAssertion, equalityMatch [3] AttributeValueAssertion,
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 {
Sermersheim Internet-Draft - Expires Jul 2004 Page 17
Lightweight Directory Access Protocol Version 3
type AttributeDescription, type AttributeDescription,
-- initial and final can occur at most once -- initial and final can occur at most once
substrings SEQUENCE SIZE (1..MAX) OF substring CHOICE { substrings SEQUENCE SIZE (1..MAX) OF substring CHOICE {
initial [0] AssertionValue, initial [0] AssertionValue,
any [1] AssertionValue, any [1] AssertionValue,
final [2] AssertionValue } } final [2] AssertionValue } }
MatchingRuleAssertion ::= SEQUENCE { MatchingRuleAssertion ::= SEQUENCE {
matchingRule [1] MatchingRuleId OPTIONAL, matchingRule [1] MatchingRuleId OPTIONAL,
type [2] AttributeDescription OPTIONAL, type [2] AttributeDescription OPTIONAL,
skipping to change at line 978 skipping to change at line 1000
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.
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.
Sermersheim Internet-Draft - Expires Jul 2004 Page 18
Lightweight Directory Access Protocol Version 3
- 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
skipping to change at line 999 skipping to change at line 1024
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.
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.
Sermersheim Internet-Draft - Expires Jul 2004 Page 18
Lightweight Directory Access Protocol Version 3
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
entries to be returned as a result of the search. A value of zero entries to be returned as a result of the search. A value of zero
in this field indicates that no client-requested size limit in this field indicates that no client-requested size limit
restrictions are in effect for the search. Servers may also restrictions are in effect for the search. Servers may also
enforce a maximum number of entries to return. enforce a maximum number of entries to return.
- timeLimit: A time limit that restricts the maximum time (in - timeLimit: A time limit that restricts the maximum time (in
skipping to change at line 1036 skipping to change at line 1057
fulfilled in order for the search to match a given entry. fulfilled in order for the search to match a given entry.
The 'and', 'or' and 'not' choices can be used to form combinations The 'and', 'or' and 'not' choices can be used to form combinations
of filters. At least one filter element MUST be present in an of filters. At least one filter element MUST be present in an
'and' or 'or' choice. The others match against individual 'and' or 'or' choice. The others match against individual
attribute values of entries in the scope of the search. attribute values of entries in the scope of the search.
(Implementor's note: the 'not' filter is an example of a tagged (Implementor's note: the 'not' filter is an example of a tagged
choice in an implicitly-tagged module. In BER this is treated as choice in an implicitly-tagged module. In BER this is treated as
if the tag was explicit.) if the tag was explicit.)
Sermersheim Internet-Draft - Expires Jul 2004 Page 19
Lightweight Directory Access Protocol Version 3
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
skipping to change at line 1057 skipping to change at line 1081
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
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.)
Sermersheim Internet-Draft - Expires Jul 2004 Page 19
Lightweight Directory Access Protocol Version 3
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.
There SHALL be at most one 'initial', and at most one 'final' in There SHALL be at most one 'initial', and at most one 'final' in
the 'substrings' of a SubstringFilter. If 'initial' is present, it the 'substrings' of a SubstringFilter. If 'initial' is present, it
SHALL be the first element of 'substrings'. If 'final' is present, SHALL be the first element of 'substrings'. If 'final' is present,
it SHALL be the last element of 'substrings'. it SHALL be the last element of 'substrings'.
The matching rule for AssertionValues in a substrings filter item The matching rule for AssertionValues in a substrings filter item
is defined by the SUBSTR matching rule for the attribute type. is defined by the SUBSTR matching rule for the attribute type.
Note that the AssertionValue in a substrings filter item conforms Note that the AssertionValue in a substrings filter item conforms
skipping to change at line 1092 skipping to change at line 1113
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, this filter item should be treated as an
equalityMatch. equalityMatch.
An extensibleMatch filter item is evaluated as follows: An extensibleMatch filter item is evaluated as follows:
Sermersheim Internet-Draft - Expires Jul 2004 Page 20
Lightweight Directory Access Protocol Version 3
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
skipping to change at line 1114 skipping to change at line 1138
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
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
Sermersheim Internet-Draft - Expires Jul 2004 Page 20
Lightweight Directory Access Protocol Version 3
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 matching rule id in the
skipping to change at line 1146 skipping to change at line 1166
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 list of the attributes to be returned from each - attributes: A list of the attributes to be returned from each
entry which matches the search filter. LDAPString values of this entry which matches the search filter. LDAPString values of this
field are constrained to the following Augmented Backus-Naur Form field are constrained to the following Augmented Backus-Naur Form
([ABNF]): ([ABNF]):
attributeSelection = noattrs / attributeSelection = attributedescription / selectionspecial
*( attributedescription / specialattr )
noattrs = %x31 %x2E %x31 ; "1.1" selectionspecial = noattrs / alluserattrs
specialattr = ASTERISK Sermersheim Internet-Draft - Expires Jul 2004 Page 21
Lightweight Directory Access Protocol Version 3
ASTERISK = %x2A ; asterisk ("*") noattrs = %x31.2E.31 ; "1.1"
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 two special values which may be used: an empty list with There are three special cases which may exist in the attribute
no attributes, and the attribute description string "*". Both of selection:
these signify that all user attributes are to be returned. (The - an empty list with no attributes,
"*" allows the client to request all user attributes in addition - a list containing "*" (with zero or more attribute
to any specified operational attributes). Client implementors descriptions), and
should note that even if all user attributes are requested, some - a list containing only "1.1".
attributes and/or attribute values of the entry may not be
included in search results due to access controls or other
restrictions. Furthermore, servers will not return operational
attributes, such as objectClasses or attributeTypes, unless they
are listed by name. Operational attributes are described in
[Models].
Attributes MUST NOT be named more than once in the list, and are An empty list requests the return of all user attributes.
Sermersheim Internet-Draft - Expires Jul 2004 Page 21 A list containing "*" requests all user attributes in addition to
Lightweight Directory Access Protocol Version 3 other listed (operational) attributes.
returned at most once in an entry. If there are attribute A list containing only the OID "1.1" indicates that no values are
descriptions in the list which are not recognized, they are to be returned. If "1.1" is provided with other values, the "1.1"
ignored by the server. value is ignored. This OID was chosen because it does not (and can
not) correspond to any attribute in use.
If the client does not want any attributes returned, it can Client implementors should note that even if all user attributes
specify a list containing only the attribute with OID "1.1". This are requested, some attributes and/or attribute values of the
OID was chosen because it does not (and can not) correspond to any entry may not be included in search results due to access controls
attribute in use. or other restrictions. Furthermore, servers will not return
operational attributes, such as objectClasses or attributeTypes,
unless they are listed by name. Operational attributes are
described in [Models].
Attributes are returned at most once in an entry. If an attribute
description is named more than once in the list, the subsequent
names are ignored. If an attribute description in the list is not
recognized, it is ignored by the server.
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.
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 {
Sermersheim Internet-Draft - Expires Jul 2004 Page 22
Lightweight Directory Access Protocol Version 3
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
skipping to change at line 1228 skipping to change at line 1257
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
response, which contains an indication of success, or detailing any response, which contains an indication of success, or detailing any
errors that have occurred. errors that have occurred.
Each entry returned in a SearchResultEntry will contain all Each entry returned in a SearchResultEntry will contain all
appropriate attributes as specified in the attributes field of the appropriate attributes as specified in the attributes field of the
Sermersheim Internet-Draft - Expires Jul 2004 Page 22
Lightweight Directory Access Protocol Version 3
Search Request. Return of attributes is subject to access control and Search Request. Return of attributes is subject to access control and
other administrative policy. other administrative policy.
Some attributes may be constructed by the server and appear in a Some attributes may be constructed by the server and appear in a
SearchResultEntry attribute list, although they are not stored SearchResultEntry attribute list, although they are not stored
attributes of an entry. Clients SHOULD NOT assume that all attributes attributes of an entry. Clients SHOULD NOT assume that all attributes
can be modified, even if permitted by access control. can be modified, even if permitted by access control.
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
skipping to change at line 1259 skipping to change at line 1284
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 a referral in this case it would return a SearchResultDone containing a referral
result code. result code.
Sermersheim Internet-Draft - Expires Jul 2004 Page 23
Lightweight Directory Access Protocol Version 3
If a server holds a copy or partial copy of the subordinate naming If a server holds a copy or partial copy of the subordinate naming
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].
skipping to change at line 1285 skipping to change at line 1313
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,
scope and filter. Some clients use a counter that is incremented each scope and filter. Some clients use a counter that is incremented each
time search result reference handling occurs for an operation, and time search result reference handling occurs for an operation, and
these kinds of clients MUST be able to handle at least ten nested these kinds of clients MUST be able to handle at least ten nested
search result references between the root and a leaf entry. search result references between the root and a leaf entry.
Sermersheim Internet-Draft - Expires Jul 2004 Page 23
Lightweight Directory Access Protocol Version 3
When an LDAP URL is used, the following instructions are followed: When an LDAP URL is used, the following instructions are followed:
- The <dn> part of the URL MUST be present, with the new target - The <dn> part of the URL MUST be present, with the new target
object name. The client MUST use this name when following the object name. The client MUST use this name when following the
reference. UTF-8 encoded characters appearing in the string reference. UTF-8 encoded characters appearing in the string
representation of a DN or search filter may not be legal for URLs representation of a DN or search filter may not be legal for URLs
(e.g. spaces) and MUST be escaped using the % method in [URI]. (e.g. spaces) and MUST be escaped using the % method in [URI].
- 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 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
skipping to change at line 1315 skipping to change at line 1340
- 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.
Sermersheim Internet-Draft - Expires Jul 2004 Page 24
Lightweight Directory Access Protocol Version 3
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
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:
skipping to change at line 1341 skipping to change at line 1369
SearchResultReference { SearchResultReference {
ldap://hostd/OU=Roles,DC=Example,DC=NET??sub } ldap://hostd/OU=Roles,DC=Example,DC=NET??sub }
SearchResultDone (success) SearchResultDone (success)
Client implementors should note that when following a Client implementors should note that when following a
SearchResultReference, additional SearchResultReference may be SearchResultReference, additional SearchResultReference may be
generated. Continuing the example, if the client contacted the server generated. Continuing the example, if the client contacted the server
(hostb) and issued the search for the subtree (hostb) and issued the search for the subtree
<OU=People,DC=Example,DC=NET>, the server might respond as follows: <OU=People,DC=Example,DC=NET>, the server might respond as follows:
Sermersheim Internet-Draft - Expires Jul 2004 Page 24
Lightweight Directory Access Protocol Version 3
SearchResultEntry for OU=People,DC=Example,DC=NET SearchResultEntry for OU=People,DC=Example,DC=NET
SearchResultReference { SearchResultReference {
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:
skipping to change at line 1370 skipping to change at line 1395
SearchResultDone (success) SearchResultDone (success)
If the contacted server does not hold the base object for the search, If the contacted server does not hold the base object for the search,
then it will return a referral to the client. For example, if the then it will return a referral to the client. For example, if the
client requests a subtree search of <DC=Example,DC=ORG> to hosta, the client requests a subtree search of <DC=Example,DC=ORG> to hosta, the
server may return only a SearchResultDone containing a referral. server may return only a SearchResultDone containing a referral.
SearchResultDone (referral) { SearchResultDone (referral) {
ldap://hostg/DC=Example,DC=ORG??sub } ldap://hostg/DC=Example,DC=ORG??sub }
Sermersheim Internet-Draft - Expires Jul 2004 Page 25
Lightweight Directory Access Protocol Version 3
4.6. Modify Operation 4.6. Modify Operation
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 {
skipping to change at line 1397 skipping to change at line 1425
- object: The name of the object to be modified. The value of this - object: The name of the object to be modified. The value of this
field contains the DN of the entry to be modified. The server field contains the DN of the entry to be modified. The server
SHALL NOT perform any alias dereferencing in determining the SHALL NOT perform any alias dereferencing in determining the
object to be modified. object to be modified.
- changes: A list of modifications to be performed on the entry. The - changes: A list of modifications to be performed on the entry. The
entire list of modifications MUST be performed in the order they entire list of modifications MUST be performed in the order they
are listed as a single atomic operation. While individual are listed as a single atomic operation. While individual
modifications may violate certain aspects of the directory schema modifications may violate certain aspects of the directory schema
(such as the object class definition and DIT content rule), the (such as the object class definition and DIT content rule), the
Sermersheim Internet-Draft - Expires Jul 2004 Page 25
Lightweight Directory Access Protocol Version 3
resulting entry after the entire list of modifications is resulting entry after the entire list of modifications is
performed MUST conform to the requirements of the directory schema performed MUST conform to the requirements of the directory schema
[Models]. [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,
skipping to change at line 1427 skipping to change at line 1451
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.
Sermersheim Internet-Draft - Expires Jul 2004 Page 26
Lightweight Directory Access Protocol Version 3
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:
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
skipping to change at line 1454 skipping to change at line 1481
The Modify Operation cannot be used to remove from an entry any of The Modify Operation cannot be used to remove from an entry any of
its distinguished values, i.e. those values which form the entry's its distinguished values, i.e. those values which form the entry's
relative distinguished name. An attempt to do so will result in the relative distinguished name. An attempt to do so will result in the
server returning the notAllowedOnRDN result code. The Modify DN server returning the notAllowedOnRDN result code. The Modify DN
Operation described in Section 4.9 is used to rename an entry. Operation described in Section 4.9 is used to rename an entry.
Note that due to the simplifications made in LDAP, there is not a Note that due to the simplifications made in LDAP, there is not a
direct mapping of the changes in an LDAP ModifyRequest onto the direct mapping of the changes in an LDAP ModifyRequest onto the
changes of a DAP ModifyEntry operation, and different implementations changes of a DAP ModifyEntry operation, and different implementations
of LDAP-DAP gateways may use different means of representing the of LDAP-DAP gateways may use different means of representing the
Sermersheim Internet-Draft - Expires Jul 2004 Page 26
Lightweight Directory Access Protocol Version 3
change. If successful, the final effect of the operations on the change. If successful, the final effect of the operations on the
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 }
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 make up the content of the - attributes: the list of attributes that, along with those from the
entry being added. Clients MUST include distinguished values RDN, make up the content of the entry being added. Clients MUST
(those forming the entry's own RDN) in this list, the include the 'objectClass' attribute, and values of any mandatory
'objectClass' attribute, and values of any mandatory attributes of attributes of the listed object classes. Clients MUST NOT supply
the listed object classes. Clients MUST NOT supply NO-USER- NO-USER-MODIFICATION attributes such as the createTimestamp or
MODIFICATION attributes such as the createTimestamp or
creatorsName attributes, since the server maintains these creatorsName attributes, since the server maintains these
automatically. automatically.
Sermersheim Internet-Draft - Expires Jul 2004 Page 27
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>. If the parent entry exists the matchedDN field containing <DC=NET>. If the parent entry exists
but is not in a naming context [Section 5 of Models] held by the but is not in a naming context [Section 5 of Models] held by the
server, the server SHOULD return a referral to the server holding the server, the server SHOULD return a referral to the server holding the
parent entry. parent entry.
skipping to change at line 1511 skipping to change at line 1536
Upon receipt of an Add Request, a server will attempt to add the Upon receipt of an Add Request, a server will attempt to add the
requested entry. The result of the add attempt will be returned to requested entry. The result of the add attempt will be returned to
the client in the Add Response, defined as follows: the client in the Add Response, defined as follows:
AddResponse ::= [APPLICATION 9] LDAPResult AddResponse ::= [APPLICATION 9] LDAPResult
A response of success indicates that the new entry has been added to A response of success indicates that the new entry has been added to
the Directory. the Directory.
Sermersheim Internet-Draft - Expires Jul 2004 Page 27
Lightweight Directory Access Protocol Version 3
4.8. Delete Operation 4.8. Delete Operation
The Delete Operation allows a client to request the removal of an The Delete Operation allows a client to request the removal of an
entry from the Directory. The Delete Request is defined as follows: entry from the Directory. The Delete Request is defined as follows:
DelRequest ::= [APPLICATION 10] LDAPDN DelRequest ::= [APPLICATION 10] LDAPDN
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.
skipping to change at line 1541 skipping to change at line 1563
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:
Sermersheim Internet-Draft - Expires Jul 2004 Page 28
Lightweight Directory Access Protocol Version 3
ModifyDNRequest ::= [APPLICATION 12] SEQUENCE { ModifyDNRequest ::= [APPLICATION 12] SEQUENCE {
entry LDAPDN, entry LDAPDN,
newrdn RelativeLDAPDN, newrdn RelativeLDAPDN,
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. - newrdn: the new RDN of the entry. If an attribute value in the
newrdn does not already exist in the entry (either as part of the
old RDN or as a non-distinguished value), it is added. If it
cannot be added, an appropriate error is returned.
- deleteoldrdn: a boolean field that controls whether the old RDN - deleteoldrdn: a boolean field that controls whether the old RDN
attribute values are to be retained as attributes of the entry, or attribute values are to be retained as attributes of the entry, or
deleted from the entry. deleted from the entry.
- newSuperior: if present, this is the name of an existing object - newSuperior: if present, this is the name of an existing object
entry which becomes the immediate superior (parent) of the entry which becomes the immediate superior (parent) of the
existing entry. existing entry.
The server SHALL NOT dereference any aliases in locating the objects The server SHALL NOT dereference any aliases in locating the objects
named in entry or newSuperior. named in entry or newSuperior.
Sermersheim Internet-Draft - Expires Jul 2004 Page 28
Lightweight Directory Access Protocol Version 3
Upon receipt of a ModifyDNRequest, a server will attempt to perform Upon receipt of a ModifyDNRequest, a server will attempt to perform
the name change 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
skipping to change at line 1595 skipping to change at line 1620
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.
Sermersheim Internet-Draft - Expires Jul 2004 Page 29
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 1621 skipping to change at line 1649
ava AttributeValueAssertion } ava AttributeValueAssertion }
Fields of the Compare Request are: Fields of the Compare Request are:
- entry: the name of the entry to be compared. The server SHALL NOT - entry: the name of the entry to be compared. The server SHALL NOT
dereference any aliases in locating the entry to be compared. dereference any aliases in locating the entry to be compared.
- ava: holds the attribute description and assertion value with - ava: holds the attribute description and assertion value with
which an attribute in the entry is to be compared. which an attribute in the entry is to be compared.
Sermersheim Internet-Draft - Expires Jul 2004 Page 29
Lightweight Directory Access Protocol Version 3
Upon receipt of a Compare Request, a server will attempt to perform Upon receipt of a Compare Request, a server will attempt to perform
the requested comparison 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
If the operation succeeds (e.g. the attribute or subtype is present The resultCode field is set to compareTrue, compareFalse, or an
and access controls allow comparison), the resultCode field will be appropriate error. compareTrue indicates that the assertion value in
compareTrue if the assertion value in the ava field is equivalent to the ava field is equivalent to a value of the attribute or subtype
any value of the attribute or subtype (according to the attribute's (according to the attribute's EQUALITY matching rule). compareFalse
EQUALITY matching rule). Otherwise compareFalse is returned in the indicates that the comparison of the assertion value in the ava field
resultCode field. and the values of the attribute or subtype resulted in an Undefined
(Section 4.5.1) or non-equivalent match.
In the event that the attribute or subtype is not present in the In the event that the attribute or subtype is not present in the
entry, the resultCode field is set to noSuchAttribute. If the entry, the resultCode field is set to noSuchAttribute. If the
attribute is unknown, the resultCode is set to attribute is unknown, the resultCode is set to
undefinedAttributeType. Note that errors and the result of comparison undefinedAttributeType. If the attribute or subtype has no equality
are all returned in the same construct. matching rule, innapropriateMatching is returned in the resultCode.
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
Sermersheim Internet-Draft - Expires Jul 2004 Page 30
Lightweight Directory Access Protocol Version 3
The function of the Abandon Operation is to allow a client to request The function of the Abandon Operation is to allow a client to request
that the server abandon an outstanding operation. The Abandon Request that the server abandon an outstanding operation. The Abandon Request
is defined as follows: is defined as follows:
AbandonRequest ::= [APPLICATION 16] MessageID AbandonRequest ::= [APPLICATION 16] MessageID
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 message
id. This is distinct from the id of the earlier operation being id. This is distinct from the id of the earlier operation being
abandoned. abandoned.
skipping to change at line 1678 skipping to change at line 1707
The ability to abandon other (particularly update) operations is at The ability to abandon other (particularly update) operations is at
the discretion of the server. the discretion of the server.
In the event that a server receives an Abandon Request on a Search In the event that a server receives an Abandon Request on a Search
Operation in the midst of transmitting responses to the search, that Operation in the midst of transmitting responses to the search, that
server MUST cease transmitting entry responses to the abandoned server MUST cease transmitting entry responses to the abandoned
request immediately, and MUST NOT send the SearchResponseDone. Of request immediately, and MUST NOT send the SearchResponseDone. Of
course, the server MUST ensure that only properly encoded LDAPMessage course, the server MUST ensure that only properly encoded LDAPMessage
PDUs are transmitted. PDUs are transmitted.
Sermersheim Internet-Draft - Expires Jul 2004 Page 30
Lightweight Directory Access Protocol Version 3
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
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.13). 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 {
Sermersheim Internet-Draft - Expires Jul 2004 Page 31
Lightweight Directory Access Protocol Version 3
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
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.
skipping to change at line 1733 skipping to change at line 1763
the messageID. the messageID.
If the requestName is not recognized by the server, the server MUST If the requestName is not recognized by the server, the server MUST
NOT provide a responseName nor a responseValue and MUST return a NOT provide a responseName nor a responseValue and MUST return a
resultCode of protocolError. 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
Sermersheim Internet-Draft - Expires Jul 2004 Page 31
Lightweight Directory Access Protocol Version 3
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.1, also follow the extensibility rules in according to Section 5.1, also follow the extensibility rules in
Section 4. Section 4.
It is RECOMMENDED that servers list the requestName of extended It is RECOMMENDED that servers list the requestName of extended
operations they support in the 'supportedExtension' attribute of the operations they support in the 'supportedExtension' attribute of the
root DSE [Models]. root DSE [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 (and possibly - the OBJECT IDENTIFIER assigned to the requestName (and possibly
responseName), 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. StartTLS Operation 4.13. IntermediateResponse Message
While the Search operation provides a mechanism to return multiple
response messages for a single search request, other operations, by
nature, do not provide for multiple response messages.
Sermersheim Internet-Draft - Expires Jul 2004 Page 32
Lightweight Directory Access Protocol Version 3
The IntermediateResponse message provides a general mechanism for
defining single-request/multiple-response operations in LDAP. This
message is intended to be used in conjunction with the extended
operation to define new single-request/multiple-response operations
or in conjunction with a control when extending existing LDAP
operations in a way that requires them to return intermediate
response information.
It is intended that the definitions and descriptions of extended
operations and controls that make use of the IntermediateResponse
message will define the circumstances when an IntermediateResponse
message can be sent by a server and the associated meaning of an
IntermediateResponse message sent in a particular circumstance.
Similarly, it is intended that clients will explicitly solicit
IntermediateResponse messages by issuing operations that specifically
call for their return.
IntermediateResponse ::= [APPLICATION 25] SEQUENCE {
responseName [0] LDAPOID OPTIONAL,
responseValue [1] OCTET STRING OPTIONAL }
IntermediateResponse messages SHALL NOT be returned to the client
unless the client issues a request that specifically solicits their
return. This document defines two forms of solicitation: extended
operation and request control.
Although the responseName and responseValue are optional in some
circumstances, generally speaking IntermediateResponse messages have
a predefined responseName and a responseValue. The value of the
responseName (if present), the syntax of the responseValue (if
present) and the semantics associated with a particular
IntermediateResponse message MUST be specified in documents
describing the extended operation or request control that uses them.
Sections 4.13.1 and 4.13.2 describe additional requirements on the
inclusion of responseName and responseValue in IntermediateResponse
messages.
4.13.1. Usage with LDAP ExtendedRequest and ExtendedResponse
A single-request/multiple-response operation may be defined using a
single ExtendedRequest message to solicit zero or more
IntermediateResponse messages of one or more kinds followed by an
ExtendedResponse message.
An extended operation that defines the return of multiple kinds of
IntermediateResponse messages MUST provide and document a mechanism
for the client to distinguish the kind of IntermediateResponse
message being sent. This SHALL be accomplished by using different
responseName values for each type of IntermediateResponse message
associated with the extended operation or by including identifying
information in the responseValue of each type of IntermediateResponse
message associated with the extended operation.
Sermersheim Internet-Draft - Expires Jul 2004 Page 33
Lightweight Directory Access Protocol Version 3
4.13.2. Usage with LDAP Request Controls
Any LDAP operation may be extended by the addition of one or more
controls ([RFC2251] Section 4.1.12). A control's semantics may
include the return of zero or more IntermediateResponse messages
prior to returning the final result code for the operation. One or
more kinds of IntermediateResponse messages may be sent in response
to a request control.
All IntermediateResponse messages associated with request controls
SHALL include a responseName. This requirement ensures that the
client can correctly identify the source of IntermediateResponse
messages when:
- two or more controls using IntermediateResponse messages are
included in a request for any LDAP operation or
- one or more controls using IntermediateResponse messages are
included in a request with an LDAP extended operation that uses
IntermediateResponse messages.
A request control that defines the return of multiple kinds of
IntermediateResponse messages MUST provide and document a mechanism
for the client to distinguish the kind of IntermediateResponse
message being sent. This SHALL be accomplished by using different
responseName values for each type of IntermediateResponse message
associated with the request control or by including identifying
information in the responseValue of each type of IntermediateResponse
message associated with the request control.
4.14. StartTLS Operation
The Start Transport Layer Security (StartTLS) operation provides the The Start Transport Layer Security (StartTLS) operation provides the
ability to establish Transport Layer Security ([TLS]) on an LDAP ability to establish Transport Layer Security ([TLS]) on an LDAP
connection. The StartTLS operation is defined using the extended connection. The StartTLS operation is defined using the extended
operation mechanism described in Section 4.12. operation mechanism described in Section 4.12.
4.13.1. StartTLS Request 4.14.1. StartTLS Request
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 connection following this The client MUST NOT send any PDUs on this connection following this
request until it receives a StartTLS extended response and completes request until it receives a StartTLS extended response and completes
TLS negotiations. TLS negotiations.
4.13.2. StartTLS Response Sermersheim Internet-Draft - Expires Jul 2004 Page 34
Lightweight Directory Access Protocol Version 3
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 is also "1.3.6.1.4.1.1466.20037", and the responseValue
field is absent. field 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.13.2.2. the other values outlined in Section 4.14.2.2.
4.13.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.
Sermersheim Internet-Draft - Expires Jul 2004 Page 32 4.14.2.2. Response other than "success"
Lightweight Directory Access Protocol Version 3
4.13.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.
- protocolError: TLS is not supported or incorrect PDU structure. - protocolError: TLS is not supported or incorrect PDU structure.
skipping to change at line 1825 skipping to change at line 1946
support TLS. The client may proceed with any LDAP operation, or it support TLS. The client may proceed with any LDAP operation, or it
may close the connection. may 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
establish a TLS connection for some reason, e.g. the certificate establish a TLS connection for some reason, e.g. the certificate
server not responding, it cannot contact its TLS implementation, or server not responding, it cannot contact its TLS implementation, or
if the server is in process of shutting down. The client may retry if the server is in process of shutting down. The client may retry
the StartTLS operation, or it may proceed with any other LDAP the StartTLS operation, or it may proceed with any other LDAP
operation, or it may close the LDAP connection. operation, or it may close the LDAP connection.
4.13.3. Closing a TLS Connection 4.14.3. Closing a TLS Connection
Sermersheim Internet-Draft - Expires Jul 2004 Page 35
Lightweight Directory Access Protocol Version 3
Two forms of TLS connection closure -- graceful and abrupt -- are Two forms of TLS connection closure -- graceful and abrupt -- are
supported. These do not involve LDAP PDUs, but are preformed at the supported. These do not involve LDAP PDUs, but are preformed at the
underlying layers. underlying layers.
4.13.3.1. Graceful Closure 4.14.3.1. Graceful Closure
Either the client or server MAY terminate the TLS connection and Either the client or server MAY terminate the TLS connection and
leave the LDAP connection intact by sending and receiving a TLS leave the LDAP connection intact by sending and receiving a TLS
closure alert. 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 connection intact, it then MUST cease to wishes to leave the LDAP connection intact, it then MUST cease to
send further PDUs and MUST ignore any received PDUs until it receives send further PDUs and MUST ignore any received 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.
Sermersheim Internet-Draft - Expires Jul 2004 Page 33
Lightweight Directory Access Protocol Version 3
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 underlying LDAP connection to remain intact. In choose to allow the underlying LDAP connection to remain intact. In
this case, it MUST immediately transmit a TLS closure alert. this case, it MUST immediately transmit a TLS closure alert.
Following this, it MAY send and receive LDAP PDUs. Following this, it MAY send and receive LDAP PDUs.
Protocol peers MAY drop the underlying LDAP connection after sending Protocol peers MAY drop the underlying LDAP connection after sending
or receiving a TLS closure alert. or receiving a TLS closure alert.
After the TLS connection has been closed, the server MUST NOT send After the TLS connection has been closed, the server MUST NOT send
responses to any request message received before the TLS closure. responses to any request message received before the TLS closure.
Thus, clients wishing to receive responses to messages sent while the Thus, clients wishing to receive responses to messages sent while the
TLS connection is intact MUST wait for those message responses before TLS connection is intact MUST wait for those message responses before
sending the TLS closure alert. sending the TLS closure alert.
4.13.3.2. Abrupt Closure 4.14.3.2. Abrupt Closure
Either the client or server MAY abruptly close the TLS connection by Either the client or server MAY abruptly close the TLS connection by
dropping the underlying transfer protocol connection. In this dropping the underlying transfer protocol connection. In this
circumstance, a server MAY send the client a Notice of Disconnection circumstance, a server MAY send the client a Notice of Disconnection
before dropping the underlying LDAP connection. Outstanding before dropping the underlying LDAP connection. Outstanding
operations are handled as specified in Section 5.2. operations are handled as specified in Section 5.2.
5. Protocol Element Encodings and Transfer 5. Protocol Element Encodings and Transfer
One underlying service, LDAP over TCP, is defined here. This service One underlying service, LDAP over TCP, is defined here. This service
is generally applicable to applications providing or consuming X.500- is generally applicable to applications providing or consuming X.500-
based directory services on the Internet. based directory services on the Internet.
Implementations of LDAP over TCP MUST implement the mapping as Implementations of LDAP over TCP MUST implement the mapping as
described in Section 5.2.1 described in Section 5.2.1
Sermersheim Internet-Draft - Expires Jul 2004 Page 36
Lightweight Directory Access Protocol Version 3
5.1. Protocol Encoding 5.1. 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.
- OCTET STRING values are encoded in the primitive form only. - OCTET STRING values are encoded in the primitive form only.
- If the value of a BOOLEAN type is true, the encoding of the value - If the value of a BOOLEAN type is true, the encoding of the value
octet is set to hex "FF". octet is set to hex "FF".
- If a value of a type is its default value, it is absent. Only some - If a value of a type is its default value, it is absent. Only some
BOOLEAN and INTEGER types have default values in this protocol BOOLEAN and INTEGER types have default values in this protocol
definition. definition.
These restrictions are meant to ease the overhead of encoding and These restrictions are meant to ease the overhead of encoding and
decoding certain elements in BER. decoding certain elements in BER.
Sermersheim Internet-Draft - Expires Jul 2004 Page 34
Lightweight Directory Access Protocol Version 3
These restrictions do not apply to ASN.1 types encapsulated inside of These restrictions do not apply to ASN.1 types encapsulated inside of
OCTET STRING values, such as attribute values, unless otherwise OCTET STRING values, such as attribute values, unless otherwise
stated. stated.
5.2. Transfer Protocols 5.2. Transfer Protocols
This protocol is designed to run over connection-oriented, reliable This protocol is designed to run over connection-oriented, reliable
transports, with all 8 bits in an octet being significant in the data transports, with all 8 bits in an octet being significant in the data
stream. Protocol operations are tied to a connection, thus if the stream. Protocol operations are tied to a connection, thus if the
connection is closed or dropped, the operation is aborted. When this connection is closed or dropped, the operation is aborted. When this
skipping to change at line 1932 skipping to change at line 2053
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
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]
Sermersheim Internet-Draft - Expires Jul 2004 Page 37
Lightweight Directory Access Protocol Version 3
mechanism. SASL allows for integrity and privacy services to be mechanism. SASL allows for integrity and privacy services to be
negotiated. negotiated.
It is also permitted that the server can return its credentials to It is also permitted that the server can return its credentials to
the client, if it chooses to do so. the client, if it chooses to do so.
Use of cleartext password is strongly discouraged where the Use of cleartext password is strongly discouraged where the
underlying transport service cannot guarantee confidentiality and may underlying transport service cannot guarantee confidentiality and may
result in disclosure of the password to unauthorized parties. result in disclosure of the password to unauthorized parties.
skipping to change at line 1953 skipping to change at line 2078
that have authenticated anonymously [AuthMeth]. that have authenticated anonymously [AuthMeth].
Requirements of authentication methods, SASL mechanisms, and TLS are Requirements of authentication methods, SASL mechanisms, and TLS are
described in [AuthMeth]. described in [AuthMeth].
It should be noted that SASL authentication exchanges do not provide It should be noted that SASL authentication exchanges do not provide
data confidentiality nor integrity protection for the version or name data confidentiality nor integrity protection for the version or name
fields of the bind request nor the resultCode, diagnosticMessage, or fields of the bind request nor the resultCode, diagnosticMessage, or
referral fields of the bind response nor of any information contained referral fields of the bind response nor of any information contained
in controls attached to bind request or responses. Thus information in controls attached to bind request or responses. Thus information
Sermersheim Internet-Draft - Expires Jul 2004 Page 35
Lightweight Directory Access Protocol Version 3
contained in these fields SHOULD NOT be relied on unless otherwise contained in these fields SHOULD NOT be relied on unless otherwise
protected (such as by establishing protections at the transport protected (such as by establishing protections at the transport
layer). layer).
Server implementors should plan for the possibility of an identity Server implementors should plan for the possibility of an identity
associated with an LDAP connection being deleted, renamed, or associated with an LDAP connection being deleted, renamed, or
modified, and take appropriate actions to prevent insecure side modified, and take appropriate actions to prevent insecure side
effects. Likewise, server implementors should plan for the effects. Likewise, server implementors should plan for the
possibility of an associated identity's credentials becoming invalid, possibility of an associated identity's credentials becoming invalid,
or an identity's privileges being changed. The ways in which these or an identity's privileges being changed. The ways in which these
skipping to change at line 1989 skipping to change at line 2110
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
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.
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. A number of LDAP security advisories are
available through [CERT]. available through [CERT].
Sermersheim Internet-Draft - Expires Jul 2004 Page 38
Lightweight Directory Access Protocol Version 3
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. It is also based on RFC 2830 by Jeff Hodges, RL "Bob" Morgan,
and Mark Wahl. Their work along with the input of individuals of the and Mark Wahl. Their work along with the input of individuals of the
IETF ASID, LDAPEXT, LDUP, LDAPBIS, and other Working Groups is IETF ASID, LDAPEXT, LDUP, LDAPBIS, and other Working Groups is
gratefully acknowledged. gratefully acknowledged.
8. Normative References 8. Normative References
skipping to change at line 2010 skipping to change at line 2134
Specifications: ABNF", RFC 2234, November 1997. Specifications: ABNF", RFC 2234, November 1997.
[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).
Sermersheim Internet-Draft - Expires Jul 2004 Page 36
Lightweight Directory Access Protocol Version 3
[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:
Specification of Basic Encoding Rules (BER), Canonical Specification of Basic Encoding Rules (BER), Canonical
Encoding Rules (CER) and Distinguished Encoding Rules Encoding Rules (CER) and Distinguished Encoding Rules
(DER)", 2002. (DER)", 2002.
[IP] Postel, J., "Internet Protocol", STD5 and RFC 791, [IP] Postel, J., "Internet Protocol", STD5 and RFC 791,
September 1981 September 1981
[ISO10646] Universal Multiple-Octet Coded Character Set (UCS) - [ISO10646] Universal Multiple-Octet Coded Character Set (UCS) -
skipping to change at line 2039 skipping to change at line 2160
[LDAPDN] Zeilenga, K., "LDAP: String Representation of [LDAPDN] Zeilenga, K., "LDAP: String Representation of
Distinguished Names", draft-ietf-ldapbis-dn-xx.txt, (a Distinguished Names", draft-ietf-ldapbis-dn-xx.txt, (a
work in progress). work in progress).
[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).
[LIMR] Harrison, R., and K. Zeilenga, "The Lightweight Directory
Access Protocol (LDAP) Intermediate Response Message",
draft-rharrison-ldap-intermediate-resp-xx.txt (a work in
progress).
Sermersheim Internet-Draft - Expires Jul 2004 Page 39
Lightweight Directory Access Protocol Version 3
[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).
[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
skipping to change at line 2066 skipping to change at line 2195
[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.
Sermersheim Internet-Draft - Expires Jul 2004 Page 37
Lightweight Directory Access Protocol Version 3
[Unicode] The Unicode Consortium, "The Unicode Standard, Version [Unicode] The Unicode Consortium, "The Unicode Standard, Version
3.2.0" is defined by "The Unicode Standard, Version 3.0" 3.2.0" is defined by "The Unicode Standard, Version 3.0"
(Reading, MA, Addison-Wesley, 2000. ISBN 0-201-61633-5), (Reading, MA, Addison-Wesley, 2000. ISBN 0-201-61633-5),
as amended by the "Unicode Standard Annex #27: Unicode as amended by the "Unicode Standard Annex #27: Unicode
3.1" (http://www.unicode.org/reports/tr27/) and by the 3.1" (http://www.unicode.org/reports/tr27/) and by the
"Unicode Standard Annex #28: Unicode 3.2" "Unicode Standard Annex #28: Unicode 3.2"
(http://www.unicode.org/reports/tr28/). (http://www.unicode.org/reports/tr28/).
[URI] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [URI] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifiers (URI): Generic Syntax", RFC 2396, Resource Identifiers (URI): Generic Syntax", RFC 2396,
skipping to change at line 2096 skipping to change at line 2222
[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 [CERT] The CERT(R) Center, http://www.cert.org
Sermersheim Internet-Draft - Expires Jul 2004 Page 40
Lightweight Directory Access Protocol Version 3
[PortReg] IANA, "Port Numbers", [PortReg] IANA, "Port Numbers",
http://www.iana.org/assignments/port-numbers http://www.iana.org/assignments/port-numbers
10. IANA Considerations 10. IANA Considerations
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.
skipping to change at line 2123 skipping to change at line 2252
11. Editor's Address 11. Editor's Address
Jim Sermersheim Jim Sermersheim
Novell, Inc. Novell, Inc.
1800 South Novell Place 1800 South Novell Place
Provo, Utah 84606, USA Provo, Utah 84606, USA
jimse@novell.com jimse@novell.com
+1 801 861-3088 +1 801 861-3088
Sermersheim Internet-Draft - Expires Jul 2004 Page 38 Sermersheim Internet-Draft - Expires Jul 2004 Page 41
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
Appendix A - LDAP Result Codes Appendix A - LDAP Result Codes
This normative appendix details additional considerations regarding This normative appendix details additional considerations regarding
LDAP result codes and provides a brief, general description of each LDAP result codes and provides a brief, general description of each
LDAP result code enumerated in Section 4.1.9. LDAP result code enumerated in Section 4.1.9.
Additional result codes MAY be defined for use with extensions Additional result codes MAY be defined for use with extensions
[LDAPIANA]. Client implementations SHALL treat any result code which [LDAPIANA]. Client implementations SHALL treat any result code which
skipping to change at line 2178 skipping to change at line 2307
or if TLS was already established. or if TLS was already established.
protocolError (2) protocolError (2)
Indicates the server received data which has incorrect Indicates the server received data which has incorrect
structure. structure.
For bind operation only, this code is also used to indicate For bind operation only, this code is also used to indicate
that the server does not support the requested protocol that the server does not support the requested protocol
version. version.
Sermersheim Internet-Draft - Expires Jul 2004 Page 39 Sermersheim Internet-Draft - Expires Jul 2004 Page 42
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
timeLimitExceeded (3) timeLimitExceeded (3)
Indicates that the time limit specified by the client was Indicates that the time limit specified by the client was
exceeded before the operation could be completed. exceeded before the operation could be completed.
sizeLimitExceeded (4) sizeLimitExceeded (4)
Indicates that the size limit specified by the client was Indicates that the size limit specified by the client was
exceeded before the operation could be completed. exceeded before the operation could be completed.
skipping to change at line 2235 skipping to change at line 2364
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.
undefinedAttributeType (17) undefinedAttributeType (17)
Indicates that a request field contains an unrecognized Indicates that a request field contains an unrecognized
attribute description. attribute description.
Sermersheim Internet-Draft - Expires Jul 2004 Page 40 Sermersheim Internet-Draft - Expires Jul 2004 Page 43
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
inappropriateMatching (18) inappropriateMatching (18)
Indicates that an attempt was made, e.g. in an assertion, to Indicates that an attempt was made, e.g. in an assertion, to
use a matching rule not defined for the attribute type use a matching rule not defined for the attribute type
concerned. concerned.
constraintViolation (19) constraintViolation (19)
Indicates that the client supplied an attribute value which Indicates that the client supplied an attribute value which
does not conform to the constraints placed upon it by the does not conform to the constraints placed upon it by the
skipping to change at line 2293 skipping to change at line 2422
provide some form of credentials. provide some form of credentials.
invalidCredentials (49) invalidCredentials (49)
Indicates that the provided credentials (e.g. the user's name Indicates that the provided credentials (e.g. the user's name
and password) are invalid. and password) are invalid.
insufficientAccessRights (50) insufficientAccessRights (50)
Indicates that the client does not have sufficient access Indicates that the client does not have sufficient access
rights to perform the operation. rights to perform the operation.
Sermersheim Internet-Draft - Expires Jul 2004 Page 41 Sermersheim Internet-Draft - Expires Jul 2004 Page 44
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
busy (51) busy (51)
Indicates that the server is too busy to service the Indicates that the server is too busy to service the
operation. operation.
unavailable (52) unavailable (52)
Indicates that the server is shutting down or a subsystem Indicates that the server is shutting down or a subsystem
necessary to complete the operation is offline. necessary to complete the operation is offline.
unwillingToPerform (53) unwillingToPerform (53)
Indicates that the server is unwilling to perform the Indicates that the server is unwilling to perform the
operation. operation.
loopDetect (54) loopDetect (54)
Indicates that the server has detected an internal loop. Indicates that the server has detected an internal loop (e.g.
while dereferencing aliases or chaining an operation).
namingViolation (64) namingViolation (64)
Indicates that the entry's name violates naming restrictions. Indicates that the entry's name violates naming restrictions.
objectClassViolation (65) objectClassViolation (65)
Indicates that the entry violates object class restrictions. Indicates that the entry violates object class restrictions.
notAllowedOnNonLeaf (66) notAllowedOnNonLeaf (66)
Indicates that the operation is inappropriately acting upon a Indicates that the operation is inappropriately acting upon a
non-leaf entry. non-leaf entry.
skipping to change at line 2344 skipping to change at line 2474
For example, this code is returned when a client attempts to For example, this code is returned when a client attempts to
modify the structural object class of an entry. modify the structural object class of an entry.
affectsMultipleDSAs (71) affectsMultipleDSAs (71)
Indicates that the operation cannot be completed as it Indicates that the operation cannot be completed as it
affects multiple servers (DSAs). affects multiple servers (DSAs).
other (80) other (80)
Indicates the server has encountered an internal error. Indicates the server has encountered an internal error.
Sermersheim Internet-Draft - Expires Jul 2004 Page 42 Sermersheim Internet-Draft - Expires Jul 2004 Page 45
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 (2003). 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.
skipping to change at line 2384 skipping to change at line 2514
addResponse AddResponse, addResponse AddResponse,
delRequest DelRequest, delRequest DelRequest,
delResponse DelResponse, delResponse DelResponse,
modDNRequest ModifyDNRequest, modDNRequest ModifyDNRequest,
modDNResponse ModifyDNResponse, modDNResponse ModifyDNResponse,
compareRequest CompareRequest, compareRequest CompareRequest,
compareResponse CompareResponse, compareResponse CompareResponse,
abandonRequest AbandonRequest, abandonRequest AbandonRequest,
extendedReq ExtendedRequest, extendedReq ExtendedRequest,
extendedResp ExtendedResponse, extendedResp ExtendedResponse,
intermediateResponse IntermediateResponse
... }, ... },
controls [0] Controls OPTIONAL } controls [0] Controls OPTIONAL }
MessageID ::= INTEGER (0 .. maxInt) MessageID ::= INTEGER (0 .. maxInt)
maxInt INTEGER ::= 2147483647 -- (2^^31 - 1) -- maxInt INTEGER ::= 2147483647 -- (2^^31 - 1) --
LDAPString ::= OCTET STRING -- UTF-8 encoded, LDAPString ::= OCTET STRING -- UTF-8 encoded,
-- [ISO10646] characters -- [ISO10646] characters
LDAPOID ::= OCTET STRING -- Constrained to <numericoid> [Models] LDAPOID ::= OCTET STRING -- Constrained to <numericoid> [Models]
LDAPDN ::= LDAPString -- Constrained to <distinguishedName> LDAPDN ::= LDAPString -- Constrained to <distinguishedName>
-- [LDAPDN] -- [LDAPDN]
RelativeLDAPDN ::= LDAPString -- Constrained to <name-component> RelativeLDAPDN ::= LDAPString -- Constrained to <name-component>
-- [LDAPDN]
Sermersheim Internet-Draft - Expires Jul 2004 Page 43 Sermersheim Internet-Draft - Expires Jul 2004 Page 46
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
-- [LDAPDN]
AttributeDescription ::= LDAPString AttributeDescription ::= LDAPString
-- Constrained to <attributedescription> -- Constrained to <attributedescription>
-- [Models] -- [Models]
AttributeValue ::= OCTET STRING AttributeValue ::= OCTET STRING
AttributeValueAssertion ::= SEQUENCE { AttributeValueAssertion ::= SEQUENCE {
attributeDesc AttributeDescription, attributeDesc AttributeDescription,
assertionValue AssertionValue } assertionValue AssertionValue }
skipping to change at line 2457 skipping to change at line 2589
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),
Sermersheim Internet-Draft - Expires Jul 2004 Page 44 Sermersheim Internet-Draft - Expires Jul 2004 Page 47
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
inappropriateAuthentication (48),
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 2515 skipping to change at line 2647
... } ... }
SaslCredentials ::= SEQUENCE { SaslCredentials ::= SEQUENCE {
mechanism LDAPString, mechanism LDAPString,
credentials OCTET STRING OPTIONAL } credentials OCTET STRING OPTIONAL }
BindResponse ::= [APPLICATION 1] SEQUENCE { BindResponse ::= [APPLICATION 1] SEQUENCE {
COMPONENTS OF LDAPResult, COMPONENTS OF LDAPResult,
serverSaslCreds [7] OCTET STRING OPTIONAL } serverSaslCreds [7] OCTET STRING OPTIONAL }
UnbindRequest ::= [APPLICATION 2] NULL Sermersheim Internet-Draft - Expires Jul 2004 Page 48
Sermersheim Internet-Draft - Expires Jul 2004 Page 45
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
UnbindRequest ::= [APPLICATION 2] NULL
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 {
neverDerefAliases (0), neverDerefAliases (0),
derefInSearching (1), derefInSearching (1),
derefFindingBaseObj (2), derefFindingBaseObj (2),
skipping to change at line 2572 skipping to change at line 2704
MatchingRuleAssertion ::= SEQUENCE { MatchingRuleAssertion ::= SEQUENCE {
matchingRule [1] MatchingRuleId OPTIONAL, matchingRule [1] MatchingRuleId OPTIONAL,
type [2] AttributeDescription OPTIONAL, type [2] AttributeDescription OPTIONAL,
matchValue [3] AssertionValue, matchValue [3] AssertionValue,
dnAttributes [4] BOOLEAN DEFAULT FALSE } dnAttributes [4] BOOLEAN DEFAULT FALSE }
SearchResultEntry ::= [APPLICATION 4] SEQUENCE { SearchResultEntry ::= [APPLICATION 4] SEQUENCE {
objectName LDAPDN, objectName LDAPDN,
attributes PartialAttributeList } attributes PartialAttributeList }
PartialAttributeList ::= SEQUENCE OF Sermersheim Internet-Draft - Expires Jul 2004 Page 49
Sermersheim Internet-Draft - Expires Jul 2004 Page 46
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
PartialAttributeList ::= SEQUENCE OF
partialAttribute PartialAttribute partialAttribute PartialAttribute
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
ModifyRequest ::= [APPLICATION 6] SEQUENCE { ModifyRequest ::= [APPLICATION 6] SEQUENCE {
object LDAPDN, object LDAPDN,
changes SEQUENCE OF change SEQUENCE { changes SEQUENCE OF change SEQUENCE {
skipping to change at line 2630 skipping to change at line 2761
AbandonRequest ::= [APPLICATION 16] MessageID AbandonRequest ::= [APPLICATION 16] MessageID
ExtendedRequest ::= [APPLICATION 23] SEQUENCE { ExtendedRequest ::= [APPLICATION 23] SEQUENCE {
requestName [0] LDAPOID, requestName [0] LDAPOID,
requestValue [1] OCTET STRING OPTIONAL } requestValue [1] OCTET STRING OPTIONAL }
ExtendedResponse ::= [APPLICATION 24] SEQUENCE { ExtendedResponse ::= [APPLICATION 24] SEQUENCE {
COMPONENTS OF LDAPResult, COMPONENTS OF LDAPResult,
responseName [10] LDAPOID OPTIONAL, responseName [10] LDAPOID OPTIONAL,
responseValue [11] OCTET STRING OPTIONAL }
Sermersheim Internet-Draft - Expires Jul 2004 Page 47 Sermersheim Internet-Draft - Expires Jul 2004 Page 50
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
responseValue [11] OCTET STRING OPTIONAL }
END END
Sermersheim Internet-Draft - Expires Jul 2004 Page 48 Sermersheim Internet-Draft - Expires Jul 2004 Page 51
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
Appendix C - Changes Appendix C - Changes
This appendix is non-normative. This appendix is non-normative.
This appendix summarizes substantive changes made to RFC 2251 and RFC This appendix summarizes substantive changes made to RFC 2251 and RFC
2830. 2830.
C.1 Changes made to made to RFC 2251: C.1 Changes made to made to RFC 2251:
skipping to change at line 2687 skipping to change at line 2819
- There was a mandatory requirement for the server to return a - There was a mandatory requirement for the server to return a
Notice of Disconnection and drop the connection when a PDU is Notice of Disconnection and drop the connection when a PDU is
malformed in a certain way. This has been clarified such that the malformed in a certain way. This has been clarified such that the
server SHOULD return the Notice of Disconnection, and MUST drop server SHOULD return the Notice of Disconnection, and MUST drop
the connection. the connection.
C.1.5 Section 4.1.1.1 C.1.5 Section 4.1.1.1
- Clarified that the messageID of requests MUST be non-zero. - Clarified that the messageID of requests MUST be non-zero.
Sermersheim Internet-Draft - Expires Jul 2004 Page 49 Sermersheim Internet-Draft - Expires Jul 2004 Page 52
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
- Clarified when it is and isn't appropriate to return an already - Clarified when it is and isn't appropriate to return an already
used message id. RFC 2251 accidentally imposed synchronous server used message id. RFC 2251 accidentally imposed synchronous server
behavior in its wording of this. behavior in its wording of this.
C.1.6 Section 4.1.2 C.1.6 Section 4.1.2
- Stated that LDAPOID is constrained to <numericoid> from [Models]. - Stated that LDAPOID is constrained to <numericoid> from [Models].
skipping to change at line 2738 skipping to change at line 2870
C.1.12 Section 4.1.11 C.1.12 Section 4.1.11
- Defined referrals in terms of URIs rather than URLs. - Defined referrals in terms of URIs rather than URLs.
- Removed the requirement that all referral URIs MUST be equally - Removed the requirement that all referral URIs MUST be equally
capable of progressing the operation. The statement was ambiguous capable of progressing the operation. The statement was ambiguous
and provided no instructions on how to carry it out. and provided no instructions on how to carry it out.
- Added the requirement that clients MUST NOT loop between servers. - Added the requirement that clients MUST NOT loop between servers.
- Clarified the instructions for using LDAPURLs in referrals, and in - Clarified the instructions for using LDAPURLs in referrals, and in
doing so added a recommendation that the scope part be present. doing so added a recommendation that the scope part be present.
Sermersheim Internet-Draft - Expires Jul 2004 Page 50 Sermersheim Internet-Draft - Expires Jul 2004 Page 53
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
C.1.13 Section 4.1.12 C.1.13 Section 4.1.12
- Specified how control values defined in terms of ASN.1 are to be - Specified how control values defined in terms of ASN.1 are to be
encoded. encoded.
- Noted that the criticality field is only applied to request - Noted that the criticality field is only applied to request
messages (except unbindRequest). messages (except unbindRequest), and must be ignored when present
on response messages and unbindRequest.
- Added language regarding combinations of controls on a message. - Added language regarding combinations of controls on a message.
- Changed "The server MUST be prepared" to "Implementations MUST be - Changed "The server MUST be prepared" to "Implementations MUST be
prepared" in the eighth paragraph to reflect that both client and prepared" in the eighth paragraph to reflect that both client and
server implementations must be able to handle this (as both parse server implementations must be able to handle this (as both parse
controls). controls).
C.1.14 Section 4.2 C.1.14 Section 4.2
- Mandated that servers return protocolError when the version is not - Mandated that servers return protocolError when the version is not
supported. supported.
skipping to change at line 2787 skipping to change at line 2920
negotiations. If there were dependencies between multiple negotiations. If there were dependencies between multiple
negotiations of a particular mechanism, the mechanism technical negotiations of a particular mechanism, the mechanism technical
specification should detail how applications are to deal with specification should detail how applications are to deal with
them. LDAP should not require any special handling. And if an LDAP them. LDAP should not require any special handling. And if an LDAP
client had used such a mechanism, it would have the option of client had used such a mechanism, it would have the option of
using another mechanism. using another mechanism.
- Dropped MUST imperative in paragraph 3 to align with [Keywords]. - Dropped MUST imperative in paragraph 3 to align with [Keywords].
C.1.16 Section 4.2.3 C.1.16 Section 4.2.3
Sermersheim Internet-Draft - Expires Jul 2004 Page 54
Lightweight Directory Access Protocol Version 3
- Moved most error-related text to Appendix A, and added text - Moved most error-related text to Appendix A, and added text
regarding certain errors used in conjunction with the bind regarding certain errors used in conjunction with the bind
operation. operation.
Sermersheim Internet-Draft - Expires Jul 2004 Page 51
Lightweight Directory Access Protocol Version 3
- Prohibited the server from specifying serverSaslCreds when not - Prohibited the server from specifying serverSaslCreds when not
appropriate. appropriate.
C.1.17 Section 4.3 C.1.17 Section 4.3
- Required both peers to cease transmission and close the connection - Required both peers to cease transmission and close the connection
for the unbind operation. for the unbind operation.
C.1.18 Section 4.4 C.1.18 Section 4.4
- Added instructions for future specifications of Unsolicited - Added instructions for future specifications of Unsolicited
Notifications. Notifications.
C.1.19 Section 4.5.1 C.1.19 Section 4.5.1
- SearchRequest attributes is now defined as an AttributeSelection - SearchRequest attributes is now defined as an AttributeSelection
type rather than AttributeDescriptionList. type rather than AttributeDescriptionList, and an ABNF is
provided.
- SearchRequest attributes may contain duplicate attribute
descriptions. This was previously prohibited. Now servers are
instructed to ignore subsequent names when they are duplicated.
This was relaxed in order to allow different short names and also
OIDs to be requested for an attribute.
- The Filter choices 'and' and 'or', and the SubstringFilter - The Filter choices 'and' and 'or', and the SubstringFilter
substrings types are now defined with a lower bound of 1. substrings types are now defined with a lower bound of 1.
- The SubstringFilter substrings 'initial, 'any', and 'final' types - The SubstringFilter substrings 'initial, 'any', and 'final' types
are now AssertionValue rather than LDAPString. Also, added are now AssertionValue rather than LDAPString. Also, added
imperatives stating that 'initial' (if present) must be listed imperatives stating that 'initial' (if present) must be listed
first, and 'final' (if present) must be listed last. first, and 'final' (if present) must be listed last.
- Clarified the semantics of the derefAliases choices. - Clarified the semantics of the derefAliases choices.
- Added instructions for equalityMatch, substrings, greaterOrEqual, - Added instructions for equalityMatch, substrings, greaterOrEqual,
lessOrEqual, and approxMatch. lessOrEqual, and approxMatch.
skipping to change at line 2834 skipping to change at line 2972
knows they are ambiguous or may cause interoperability problems. knows they are ambiguous or may cause interoperability problems.
- Removed all mention of ExtendedResponse due to lack of - Removed all mention of ExtendedResponse due to lack of
implementation. implementation.
C.1.21 Section 4.5.3 C.1.21 Section 4.5.3
- Made changes similar to those made to Section 4.1.11. - Made changes similar to those made to Section 4.1.11.
C.1.22 Section 4.5.3.1 C.1.22 Section 4.5.3.1
Sermersheim Internet-Draft - Expires Jul 2004 Page 55
Lightweight Directory Access Protocol Version 3
- Fixed examples to adhere to changes made to Section 4.5.3. - Fixed examples to adhere to changes made to Section 4.5.3.
C.1.23 Section 4.6 C.1.23 Section 4.6
- Removed restriction that required an EQUALITY matching rule in - Removed restriction that required an EQUALITY matching rule in
order to perform value delete modifications. It is sufficiently order to perform value delete modifications. It is sufficiently
Sermersheim Internet-Draft - Expires Jul 2004 Page 52
Lightweight Directory Access Protocol Version 3
documented that in absence of an equality matching rule, octet documented that in absence of an equality matching rule, octet
equality is used. equality is used.
- Replaced AttributeTypeAndValues with Attribute as they are - Replaced AttributeTypeAndValues with Attribute as they are
equivalent. equivalent.
- Clarified what type of modification changes might temporarily - Clarified what type of modification changes might temporarily
violate schema. violate schema.
C.1.24 Section 4.9 C.1.24 Section 4.7
- Aligned Add operation with X.511 in that the attributes of the RDN
are used in conjunction with the listed attributes to create the
entry. Previously, Add required that the distinguished values be
present in the listed attributes.
C.1.25 Section 4.9
- Required servers to not dereference aliases for modify DN. This - Required servers to not dereference aliases for modify DN. This
was added for consistency with other operations and to help ensure was added for consistency with other operations and to help ensure
data consistency. data consistency.
- Allow modify DN to fail when moving between naming contexts. - Allow modify DN to fail when moving between naming contexts.
- Specified what happens when the attributes of the newrdn are no
present on the entry.
C.1.25 Section 4.10 C.1.26 Section 4.10
- Clarified the semantics of Compare when the attribute is not - Clarified the semantics of Compare when the attribute is not
present and when it is unknown. present and when it is unknown.
- Clarified that an Undefined compare results in a compareFalse
resultCode.
- Required servers to not dereference aliases for compare. This was - Required servers to not dereference aliases for compare. This was
added for consistency with other operations and to help ensure added for consistency with other operations and to help ensure
data consistency. data consistency.
C.1.26 Section 4.11 C.1.27 Section 4.11
- Explained that since abandon returns no response, clients should - Explained that since abandon returns no response, clients should
not use it if they need to know the outcome. not use it if they need to know the outcome.
- Specified that Abandon and Unbind cannot be abandoned. - Specified that Abandon and Unbind cannot be abandoned.
C.1.27 Section 4.12 C.1.28 Section 4.12
- Specified how values of extended operations defined in terms of - Specified how values of extended operations defined in terms of
ASN.1 are to be encoded. ASN.1 are to be encoded.
Sermersheim Internet-Draft - Expires Jul 2004 Page 56
Lightweight Directory Access Protocol Version 3
- Added instructions on what extended operation specifications - Added instructions on what extended operation specifications
consist of. consist of.
- Added a recommendation that servers advertise supported extended - Added a recommendation that servers advertise supported extended
operations. operations.
C.1.28 Section 5.2 C.1.29 Section 5.2
- Moved referral-specific instructions into referral-related - Moved referral-specific instructions into referral-related
sections. sections.
C.1.29 Section 7 C.1.30 Section 7
- Reworded notes regarding SASL not protecting certain aspects of - Reworded notes regarding SASL not protecting certain aspects of
the LDAP bind PDU. the LDAP bind PDU.
Sermersheim Internet-Draft - Expires Jul 2004 Page 53
Lightweight Directory Access Protocol Version 3
- Noted that Servers are encouraged to prevent directory - Noted that Servers are encouraged to prevent directory
modifications by clients that have authenticated anonymously modifications by clients that have authenticated anonymously
[AuthMeth]. [AuthMeth].
- Added a note regarding the scenario where an identity is changed - Added a note regarding the scenario where an identity is changed
(deleted, privileges or credentials modified, etc.). (deleted, privileges or credentials modified, etc.).
- Warned against following referrals that may have been injected in - Warned against following referrals that may have been injected in
the data stream. the data stream.
- Added a note regarding malformed and long encodings. - Added a note regarding malformed and long encodings.
C.1.30 Appendix A C.1.31 Appendix A
- Added "EXTESIBILITY IMPLIED" to ASN.1 definition. - Added "EXTESIBILITY IMPLIED" to ASN.1 definition.
- Removed AttributeType. It is not used. - Removed AttributeType. It is not used.
C.2 Changes made to made to RFC 2830: C.2 Changes made to made to RFC 2830:
This section summarizes the substantive changes made to Sections of This section summarizes the substantive changes made to Sections of
RFC 2830. Readers should consult [AuthMeth] for summaries of changes RFC 2830. Readers should consult [AuthMeth] for summaries of changes
to other sections. to other sections.
skipping to change at line 2928 skipping to change at line 3076
- Removed requirement that only a narrow set of result codes can be - Removed requirement that only a narrow set of result codes can be
returned. Some result codes are required in certain scenarios, but returned. Some result codes are required in certain scenarios, but
any other may be returned if appropriate. any other may be returned if appropriate.
C.2.1 Section 4.13.3.1 C.2.1 Section 4.13.3.1
- Reworded most of this section and added the requirement that after - Reworded most of this section and added the requirement that after
the TLS connection has been closed, the server MUST NOT send the TLS connection has been closed, the server MUST NOT send
responses to any request message received before the TLS closure. responses to any request message received before the TLS closure.
Sermersheim Internet-Draft - Expires Jul 2004 Page 54 Sermersheim Internet-Draft - Expires Jul 2004 Page 57
Lightweight Directory Access Protocol Version 3
C.3 Changes made to made to [LIMR]:
- In general, all technical language was transferred in whole.
Supporting and background language seen as redundant due to its
presence in this document was omitted.
Sermersheim Internet-Draft - Expires Jul 2004 Page 58
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
Intellectual Property Rights Intellectual Property Rights
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 or other rights that might be claimed to intellectual property 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; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
skipping to change at line 2980 skipping to change at line 3137
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Sermersheim Internet-Draft - Expires Jul 2004 Page 59
 End of changes. 

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