draft-ietf-ldapbis-protocol-31.txt   draft-ietf-ldapbis-protocol-32.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-31.txt May 2005 Document: draft-ietf-ldapbis-protocol-32.txt Oct 2005
Obsoletes: RFCs 2251, 2830, 3771 Obsoletes: RFCs 2251, 2830, 3771
LDAP: The Protocol LDAP: The Protocol
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions By submitting this Internet-Draft, each
of section 3 of RFC 3667. By submitting this Internet-Draft, each
author represents that any applicable patent or other IPR claims of author represents that any applicable patent or other IPR claims of
which he or she is aware have been or will be disclosed, and any of which he or she is aware have been or will be disclosed, and any of
which he or she becomes aware will be disclosed, in accordance with which he or she becomes aware will be disclosed, in accordance with
Section 6 of BCP 79. Section 6 of BCP 79.
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
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress". material or to cite them other than as "work in progress".
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
<http://www.ietf.org/ietf/1id-abstracts.txt>. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
<http://www.ietf.org/shadow.html>. http://www.ietf.org/shadow.html.
This Internet-Draft will expire in November 2005. This Internet-Draft will expire in February 2005.
Technical discussion of this document will take place on the IETF Technical discussion of this document will take place on the IETF
LDAP Revision Working Group (LDAPbis) mailing list <ietf- LDAP Revision Working Group (LDAPbis) mailing list <ietf-
ldapbis@openldap.org>. Please send editorial comments directly to the ldapbis@openldap.org>. Please send editorial comments directly to the
editor <jimse@novell.com>. editor <jimse@novell.com>.
Copyright Notice
Copyright (C) The Internet Society (2005). All Rights Reserved.
Abstract Abstract
This document describes the protocol elements, along with their This document describes the protocol elements, along with their
semantics and encodings, of the Lightweight Directory Access Protocol semantics and encodings, of the Lightweight Directory Access Protocol
(LDAP). LDAP provides access to distributed directory services that (LDAP). LDAP provides access to distributed directory services that
act in accordance with X.500 data and service models. These protocol act in accordance with X.500 data and service models. These protocol
elements are based on those described in the X.500 Directory Access elements are based on those described in the X.500 Directory Access
Protocol (DAP). Protocol (DAP).
Lightweight Directory Access Protocol Version 3
Table of Contents Table of Contents
Sermersheim Internet-Draft - Expires April 2006 Page 1
Lightweight Directory Access Protocol Version 3
1. Introduction....................................................3 1. Introduction....................................................3
1.1. Relationship to Other LDAP Specifications.....................3 1.1. Relationship to Other LDAP Specifications.....................3
2. Conventions.....................................................3 2. Conventions.....................................................3
3. Protocol Model..................................................4 3. Protocol Model..................................................4
3.1 Operation and LDAP Message Layer Relationship..................5 3.1 Operation and LDAP Message Layer Relationship..................5
4. Elements of Protocol............................................5 4. Elements of Protocol............................................5
4.1. Common Elements...............................................5 4.1. Common Elements...............................................5
4.1.1. Message Envelope............................................5 4.1.1. Message Envelope............................................5
4.1.2. String Types................................................7 4.1.2. String Types................................................7
4.1.3. Distinguished Name and Relative Distinguished Name..........7 4.1.3. Distinguished Name and Relative Distinguished Name..........7
skipping to change at line 106 skipping to change at line 102
10. IANA Considerations...........................................44 10. IANA Considerations...........................................44
11. Editor's Address..............................................45 11. Editor's Address..............................................45
Appendix A - LDAP Result Codes....................................46 Appendix A - LDAP Result Codes....................................46
A.1 Non-Error Result Codes........................................46 A.1 Non-Error Result Codes........................................46
A.2 Result Codes..................................................46 A.2 Result Codes..................................................46
Appendix B - Complete ASN.1 Definition............................51 Appendix B - Complete ASN.1 Definition............................51
Appendix C - Changes..............................................57 Appendix C - Changes..............................................57
C.1 Changes made to RFC 2251:.....................................57 C.1 Changes made to RFC 2251:.....................................57
C.2 Changes made to RFC 2830:.....................................62 C.2 Changes made to RFC 2830:.....................................62
C.3 Changes made to RFC 3771:.....................................63 C.3 Changes made to RFC 3771:.....................................63
Sermersheim Internet-Draft - Expires April 2006 Page 2
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
1. Introduction 1. Introduction
The Directory is "a collection of open systems cooperating to provide The Directory is "a collection of open systems cooperating to provide
directory services" [X.500]. A directory user, which may be a human directory services" [X.500]. A directory user, which may be a human
or other entity, accesses the Directory through a client (or or other entity, accesses the Directory through a client (or
Directory User Agent (DUA)). The client, on behalf of the directory Directory User Agent (DUA)). The client, on behalf of the directory
user, interacts with one or more servers (or Directory System Agents user, interacts with one or more servers (or Directory System Agents
(DSA)). Clients interact with servers using a directory access (DSA)). Clients interact with servers using a directory access
skipping to change at line 158 skipping to change at line 156
to be interpreted as described in [Keyword]. to be interpreted as described in [Keyword].
Character names in this document use the notation for code points and Character names in this document use the notation for code points and
names from the Unicode Standard [Unicode]. For example, the letter names from the Unicode Standard [Unicode]. For example, the letter
"a" may be represented as either <U+0061> or <LATIN SMALL LETTER A>. "a" may be represented as either <U+0061> or <LATIN SMALL LETTER A>.
Note: a glossary of terms used in Unicode can be found in [Glossary]. Note: a glossary of terms used in Unicode can be found in [Glossary].
Information on the Unicode character encoding model can be found in Information on the Unicode character encoding model can be found in
[CharModel]. [CharModel].
Sermersheim Internet-Draft - Expires April 2006 Page 3
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
The term "transport connection" refers to the underlying transport The term "transport connection" refers to the underlying transport
services used to carry the protocol exchange, as well as associations services used to carry the protocol exchange, as well as associations
established by these services. established by these services.
The term "TLS layer" refers to TLS services used in providing The term "TLS layer" refers to TLS services used in providing
security services, as well as associations established by these security services, as well as associations established by these
services. services.
skipping to change at line 210 skipping to change at line 209
exchanged between a client and server in any order. If required, exchanged between a client and server in any order. If required,
synchronous behavior may be controlled by client applications. synchronous behavior may be controlled by client applications.
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.
Sermersheim Internet-Draft - Expires April 2006 Page 4
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
3.1 Operation and LDAP Message Layer Relationship 3.1. Operation and LDAP Message Layer Relationship
Protocol operations are exchanged at the LDAP message layer. When the Protocol operations are exchanged at the LDAP message layer. When the
transport connection is closed, any uncompleted operations at the transport connection is closed, any uncompleted operations at the
LDAP message layer, when possible, are abandoned, and when not LDAP message layer, when possible, are abandoned, and when not
possible, are completed without transmission of the response. Also, possible, are completed without transmission of the response. Also,
when the transport connection is closed, the client MUST NOT assume when the transport connection is closed, the client MUST NOT assume
that any uncompleted update operations have succeeded or failed. that any uncompleted update operations have succeeded or failed.
4. Elements of Protocol 4. Elements of Protocol
skipping to change at line 258 skipping to change at line 258
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
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:
Sermersheim Internet-Draft - Expires April 2006 Page 5
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
LDAPMessage ::= SEQUENCE { LDAPMessage ::= SEQUENCE {
messageID MessageID, messageID MessageID,
protocolOp CHOICE { protocolOp CHOICE {
bindRequest BindRequest, bindRequest BindRequest,
bindResponse BindResponse, bindResponse BindResponse,
unbindRequest UnbindRequest, unbindRequest UnbindRequest,
searchRequest SearchRequest, searchRequest SearchRequest,
searchResEntry SearchResultEntry, searchResEntry SearchResultEntry,
skipping to change at line 313 skipping to change at line 314
and MUST immediately terminate the LDAP session as described in and MUST immediately terminate the LDAP session as described in
Section 5.3. Section 5.3.
In other cases where the client or server cannot parse an LDAP PDU, In other cases where the client or server cannot parse an LDAP PDU,
it SHOULD abruptly terminate the LDAP session (Section 5.3) where it SHOULD abruptly terminate the LDAP session (Section 5.3) where
further communication (including providing notice) would be further communication (including providing notice) would be
pernicious. Otherwise, server implementations MUST return an pernicious. Otherwise, server implementations MUST return an
appropriate response to the request, with the resultCode set to appropriate response to the request, with the resultCode set to
protocolError. protocolError.
Sermersheim Internet-Draft - Expires April 2006 Page 6
Lightweight Directory Access Protocol Version 3 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 messageID of any other request in progress in the same LDAP the messageID of any other request in progress in the same LDAP
session. The zero value is reserved for the unsolicited notification session. The zero value is reserved for the unsolicited notification
skipping to change at line 367 skipping to change at line 369
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
-- Constrained to <distinguishedName> [LDAPDN] -- Constrained to <distinguishedName> [LDAPDN]
Sermersheim Internet-Draft - Expires April 2006 Page 7
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
A RelativeLDAPDN is defined to be the representation of a Relative A RelativeLDAPDN is defined to be the representation of a Relative
Distinguished Name (RDN) after encoding according to the Distinguished Name (RDN) after encoding according to the
specification in [LDAPDN]. specification in [LDAPDN].
RelativeLDAPDN ::= LDAPString RelativeLDAPDN ::= LDAPString
-- Constrained to <name-component> [LDAPDN] -- Constrained to <name-component> [LDAPDN]
4.1.4. Attribute Descriptions 4.1.4. Attribute Descriptions
skipping to change at line 420 skipping to change at line 424
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
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.
Sermersheim Internet-Draft - Expires April 2006 Page 8
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
AttributeValueAssertion ::= SEQUENCE { AttributeValueAssertion ::= SEQUENCE {
attributeDesc AttributeDescription, attributeDesc AttributeDescription,
assertionValue AssertionValue } assertionValue AssertionValue }
AssertionValue ::= OCTET STRING AssertionValue ::= OCTET STRING
The syntax of the AssertionValue depends on the context of the LDAP The syntax of the AssertionValue depends on the context of the LDAP
operation being performed. For example, the syntax of the EQUALITY operation being performed. For example, the syntax of the EQUALITY
skipping to change at line 471 skipping to change at line 476
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 containing the elements found requests, servers will return responses containing the elements found
in LDAPResult to indicate the final status of the protocol operation in LDAPResult to indicate the final status of the protocol operation
request. request.
Sermersheim Internet-Draft - Expires April 2006 Page 9
Lightweight Directory Access Protocol Version 3 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),
skipping to change at line 525 skipping to change at line 531
entryAlreadyExists (68), entryAlreadyExists (68),
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 April 2006 Page 10
Lightweight Directory Access Protocol Version 3 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. Servers
may return substituted result codes to prevent unauthorized
disclosures.
The diagnosticMessage field of this construct may, at the server's The diagnosticMessage field of this construct may, at the server's
option, be used to return a string containing a textual, human- option, be used to return a string containing a textual, human-
readable (terminal control and page formatting characters should be readable (terminal control and page formatting characters should be
avoided) diagnostic message. As this diagnostic message is not avoided) diagnostic message. As this diagnostic message is not
standardized, implementations MUST NOT rely on the values returned. standardized, implementations MUST NOT rely on the values returned.
Diagnostic messages typically supplement the resultCode with Diagnostic messages typically supplement the resultCode with
additional information. If the server chooses not to return a textual additional information. If the server chooses not to return a textual
diagnostic, the diagnosticMessage field MUST be empty. diagnostic, the diagnosticMessage field MUST be empty.
skipping to change at line 578 skipping to change at line 588
not have responses). At least one URI MUST be present in the not have responses). At least one URI MUST be present in the
Referral. Referral.
During a Search operation, after the baseObject is located, and During a Search operation, after the baseObject is located, and
entries are being evaluated, the referral is not returned. Instead, entries are being evaluated, the referral is not returned. Instead,
continuation references, described in Section 4.5.3, are returned continuation references, described in Section 4.5.3, are returned
when other servers would need to be contacted to complete the when other servers would need to be contacted to complete the
operation. operation.
Referral ::= SEQUENCE SIZE (1..MAX) OF uri URI Referral ::= SEQUENCE SIZE (1..MAX) OF uri URI
Sermersheim Internet-Draft - Expires April 2006 Page 11
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
URI ::= LDAPString -- limited to characters permitted in URI ::= LDAPString -- limited to characters permitted in
-- URIs -- URIs
If the client wishes to progress the operation, it contacts one of If the client wishes to progress the operation, it contacts one of
the supported services found in the referral. If multiple URIs are the supported services found in the referral. If multiple URIs are
present, the client assumes that any supported URI may be used to present, the client assumes that any supported URI may be used to
progress the operation. progress the operation.
skipping to change at line 632 skipping to change at line 644
- If the <scope> part is missing, the scope of the original Search - If the <scope> part is missing, the scope of the original Search
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.
Sermersheim Internet-Draft - Expires April 2006 Page 12
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
UTF-8 encoded characters appearing in the string representation of a UTF-8 encoded characters appearing in the string representation of a
DN, search filter, or other fields of the referral value may not be DN, search filter, or other fields of the referral value may not be
legal for URIs (e.g. spaces) and MUST be escaped using the % method legal for URIs (e.g. spaces) and MUST be escaped using the % method
in [URI]. in [URI].
4.1.11. Controls 4.1.11. Controls
Controls provide a mechanism whereby the semantics and arguments of Controls provide a mechanism whereby the semantics and arguments of
skipping to change at line 686 skipping to change at line 699
- If the server does not recognize the control type, determines that - If the server does not recognize the control type, determines that
it is not appropriate for the operation, or is otherwise unwilling it is not appropriate for the operation, or is otherwise unwilling
to perform the operation with the control, and the criticality to perform the operation with the control, and the criticality
field is FALSE, the server MUST ignore the control. field is FALSE, the server MUST ignore the control.
- Regardless of criticality, if a control is applied to an - Regardless of criticality, if a control is applied to an
operation, it is applied consistently and impartially to the operation, it is applied consistently and impartially to the
entire operation. entire operation.
Sermersheim Internet-Draft - Expires April 2006 Page 13
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
The controlValue may contain information associated with the The controlValue may contain information associated with the
controlType. Its format is defined by the specification of the controlType. Its format is defined by the specification of the
control. Implementations MUST be prepared to handle arbitrary control. Implementations MUST be prepared to handle arbitrary
contents of the controlValue octet string, including zero bytes. It contents of the controlValue octet string, including zero bytes. It
is absent only if there is no value information which is associated is absent only if there is no value information which is associated
with a control of its type. When a controlValue is defined in terms with a control of its type. When a controlValue is defined in terms
of ASN.1, and BER encoded according to Section 5.1, it also follows of ASN.1, and BER encoded according to Section 5.1, it also follows
the extensibility rules in Section 4. the extensibility rules in Section 4.
skipping to change at line 737 skipping to change at line 751
- whether the controlValue field is present, and if so, the format - whether the controlValue field is present, and if so, the format
of its contents, of its 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 April 2006 Page 14
Lightweight Directory Access Protocol Version 3 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.
Operational, authentication, and security-related semantics of this Operational, authentication, and security-related semantics of this
operation are given in [AuthMeth]. operation are given in [AuthMeth].
The Bind request is defined as follows: The Bind request is defined as follows:
skipping to change at line 775 skipping to change at line 791
to be used at the LDAP message layer. This document describes to be used at the LDAP message layer. 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 a does not support the specified version, it MUST respond with a
BindResponse where the resultCode is set to protocolError. BindResponse where the resultCode is set to protocolError.
- name: If not empty, the name of the Directory object that the - name: If not empty, the name of the Directory object that the
client wishes to bind as. This field may take on a null value (a client wishes to bind as. This field may take on a null value (a
zero length string) for the purposes of anonymous binds zero length string) for the purposes of anonymous binds
([AuthMeth] Section 5.1) or when using Simple Authentication and ([AuthMeth] Section 5.1) or when using Simple Authentication and
Security Layer [SASL] authentication ([AuthMeth] Section 3.3.2). Security Layer [SASL] authentication ([AuthMeth] Section 5.2).
Where the server attempts to locate the named object, it SHALL NOT Where the server attempts to locate the named object, it SHALL NOT
perform alias dereferencing. perform alias dereferencing.
- authentication: information used in authentication. This type is - authentication: information used in authentication. This type is
extensible as defined in Section 3.7 of [LDAPIANA]. Servers that extensible as defined in Section 3.7 of [LDAPIANA]. Servers that
do not support a choice supplied by a client return a BindResponse do not support a choice supplied by a client return a BindResponse
with the resultCode set to authMethodNotSupported. with the resultCode set to authMethodNotSupported.
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 as "query" strings by applying the [SASLprep] profile of passwords as "query" strings by applying the [SASLprep] profile of
the [Stringprep] algorithm. Passwords consisting of other data the [Stringprep] algorithm. Passwords consisting of other data
(such as random octets) MUST NOT be altered. The determination of (such as random octets) MUST NOT be altered. The determination of
whether a password is textual is a local client matter. whether a password is textual is a local client matter.
Sermersheim Internet-Draft - Expires April 2006 Page 15
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
4.2.1. Processing of the Bind Request 4.2.1. Processing of the Bind Request
Before processing a BindRequest, all uncompleted operations MUST Before processing a BindRequest, all uncompleted operations MUST
either complete or be abandoned. The server may either wait for the either complete or be abandoned. The server may either wait for the
uncompleted operations to complete, or abandon them. The server then uncompleted operations to complete, or abandon them. The server then
proceeds to authenticate the client in either a single-step, or proceeds to authenticate the client in either a single-step, or
multi-step Bind process. Each step requires the server to return a multi-step Bind process. Each step requires the server to return a
BindResponse to indicate the status of authentication. BindResponse to indicate the status of authentication.
skipping to change at line 822 skipping to change at line 839
LDAP session, it may terminate the LDAP session, re-establish it and LDAP session, it may terminate the LDAP session, re-establish it and
begin again by first sending a BindRequest. This will aid in begin again by first sending a BindRequest. 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 to change the authentication Clients may send multiple Bind requests to change the authentication
and/or security associations or to complete a multi-stage Bind and/or security associations or to complete a multi-stage Bind
process. Authentication from earlier binds is subsequently ignored. process. Authentication from earlier binds is subsequently ignored.
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 ([AuthMeth] Section client to invoke the BindRequest multiple times ([AuthMeth] Section
8.2). Clients MUST NOT invoke operations between two Bind requests 5.2). Clients MUST NOT invoke operations between two Bind requests
made as part of a multi-stage Bind. made as part of a multi-stage Bind.
A client may abort a SASL bind negotiation by sending a BindRequest A client may abort a SASL bind negotiation by sending a BindRequest
with a different value in the mechanism field of SaslCredentials, or with a different value in the mechanism field of SaslCredentials, or
an AuthenticationChoice other than sasl. an AuthenticationChoice other than sasl.
If the client sends a BindRequest with the sasl mechanism field as an If the client sends a BindRequest with the sasl mechanism field as an
empty string, the server MUST return a BindResponse with the empty string, the server MUST return a BindResponse with the
resultCode set to authMethodNotSupported. This will allow clients to resultCode set to authMethodNotSupported. 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
skipping to change at line 846 skipping to change at line 863
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.
Sermersheim Internet-Draft - Expires April 2006 Page 16
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
A successful Bind operation is indicated by a BindResponse with a A successful Bind operation is indicated by a BindResponse with a
resultCode set to success. Otherwise, an appropriate result code is resultCode set to success. Otherwise, an appropriate result code is
set in the BindResponse. For BindResponse, the protocolError result set in the BindResponse. For BindResponse, the protocolError result
code may be used to indicate that the version number supplied by the code may be used to indicate that the version number supplied by the
client is unsupported. client is unsupported.
If the client receives a BindResponse where the resultCode is set to If the client receives a BindResponse where the resultCode is set to
protocolError, it is to assume that the server does not support this protocolError, it is to assume that the server does not support this
skipping to change at line 896 skipping to change at line 914
4.4. Unsolicited Notification 4.4. Unsolicited Notification
An unsolicited notification is an LDAPMessage sent from the server to An unsolicited notification is an LDAPMessage sent from the server to
the client which is not in response to any LDAPMessage received by the client which is not in response to any LDAPMessage received by
the server. It is used to signal an extraordinary condition in the the server. It is used to signal an extraordinary condition in the
server or in the LDAP session between the client and the server. The server or in the LDAP session 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.
Sermersheim Internet-Draft - Expires April 2006 Page 17
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
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 set to the extendedResp the messageID is zero and protocolOp is set to the extendedResp
choice using the ExtendedResponse type (See Section 4.12). The choice using the ExtendedResponse type (See Section 4.12). The
responseName field of the ExtendedResponse always contains an LDAPOID responseName field of the ExtendedResponse always contains an LDAPOID
which is unique for this notification. which is unique for this notification.
One unsolicited notification (Notice of Disconnection) is defined in One unsolicited notification (Notice of Disconnection) is defined in
this document. The specification of an unsolicited notification this document. The specification of an unsolicited notification
skipping to change at line 950 skipping to change at line 969
The Search operation is used to request a server to return, subject The Search operation is used to request a server to return, subject
to access controls and other restrictions, a set of entries matching to access controls and other restrictions, a set of entries matching
a complex search criterion. This can be used to read attributes from a complex search criterion. This can be used to read attributes from
a single entry, from entries immediately subordinate to a particular a single entry, from entries immediately subordinate to a particular
entry, or a whole subtree of entries. entry, or a whole subtree of entries.
4.5.1. Search Request 4.5.1. Search Request
The Search request is defined as follows: The Search request is defined as follows:
Sermersheim Internet-Draft - Expires April 2006 Page 18
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
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 {
skipping to change at line 1000 skipping to change at line 1020
initial [0] AssertionValue, -- can occur at most once initial [0] AssertionValue, -- can occur at most once
any [1] AssertionValue, any [1] AssertionValue,
final [2] AssertionValue } -- can occur at most once final [2] AssertionValue } -- can occur at most once
} }
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 }
Sermersheim Internet-Draft - Expires April 2006 Page 19
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
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 singleLevel Search operation with a filter client requesting a singleLevel 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 baseObject Search X.500 "read"-like operation can be emulated by a baseObject Search
operation with the same filter. A server which provides a gateway to operation with the same filter. A server which provides a gateway to
X.500 is not required to use the Read or List operations, although it 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 same may choose to do so, and if it does, it must provide the same
semantics as the X.500 Search operation. semantics as the X.500 Search operation.
4.5.1.1 SearchRequest.baseObject 4.5.1.1. SearchRequest.baseObject
The name of the base object entry (or possibly the root) relative to The name of the base object entry (or possibly the root) relative to
which the Search is to be performed. which the Search is to be performed.
4.5.1.2 SearchRequest.scope 4.5.1.2. SearchRequest.scope
Specifies the scope of the Search to be performed. The semantics (as Specifies the scope of the Search to be performed. The semantics (as
described in [X.511]) of the defined values of this field are: described in [X.511]) of the defined values of this field are:
baseObject: The scope is constrained to the entry named by baseObject: The scope is constrained to the entry named by
baseObject. baseObject.
singleLevel: The scope is constrained to the immediate singleLevel: The scope is constrained to the immediate
subordinates of the entry named by baseObject. subordinates of the entry named by baseObject.
wholeSubtree: the scope is constrained to the entry named by the wholeSubtree: the scope is constrained to the entry named by the
baseObject, and all its subordinates. baseObject, and all its subordinates.
4.5.1.3 SearchRequest.derefAliases 4.5.1.3. SearchRequest.derefAliases
An indicator as to whether or not alias entries (as defined in An indicator as to whether or not alias entries (as defined in
[Models]) are to be dereferenced during stages of the Search [Models]) are to be dereferenced during stages of the Search
operation. operation.
The act of dereferencing an alias includes recursively dereferencing The act of dereferencing an alias includes recursively dereferencing
aliases which refer to aliases. aliases which refer to aliases.
Servers MUST detect looping while dereferencing aliases in order to Servers MUST detect looping while dereferencing aliases in order to
prevent denial of service attacks of this nature. prevent denial of service attacks of this nature.
The semantics of the defined values of this field are: The semantics of the defined values of this field are:
neverDerefAliases: Do not dereference aliases in searching or in neverDerefAliases: Do not dereference aliases in searching or in
locating the base object of the Search. locating the base object of the Search.
Sermersheim Internet-Draft - Expires April 2006 Page 20
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
derefInSearching: While searching subordinates of the base object, derefInSearching: While searching subordinates of the base object,
dereference any alias within the search scope. Dereferenced dereference any alias within the search scope. Dereferenced
objects become the vertices of further search scopes where the objects become the vertices of further search scopes where the
Search operation is also applied. If the search scope is Search operation is also applied. If the search scope is
wholeSubtree, the Search continues in the subtree(s) of any wholeSubtree, the Search continues in the subtree(s) of any
dereferenced object. If the search scope is singleLevel, the dereferenced object. If the search scope is singleLevel, the
search is applied to any dereferenced objects, and is not applied search is applied to any dereferenced objects, and is not applied
to their subordinates. Servers SHOULD eliminate duplicate entries to their subordinates. 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 the object of the Search, but not when searching subordinates of the
base object. base object.
derefAlways: Dereference aliases both in searching and in locating derefAlways: Dereference aliases both in searching and in locating
the base object of the Search. the base object of the Search.
4.5.1.4 SearchRequest.sizeLimit 4.5.1.4. SearchRequest.sizeLimit
A size limit that restricts the maximum number of entries to be A size limit that restricts the maximum number of entries to be
returned as a result of the Search. A value of zero in this field returned as a result of the Search. A value of zero in this field
indicates that no client-requested size limit restrictions are in indicates that no client-requested size limit restrictions are in
effect for the Search. Servers may also enforce a maximum number of effect for the Search. Servers may also enforce a maximum number of
entries to return. entries to return.
4.5.1.5 SearchRequest.timeLimit 4.5.1.5. SearchRequest.timeLimit
A time limit that restricts the maximum time (in seconds) allowed for A time limit that restricts the maximum time (in seconds) allowed for
a Search. A value of zero in this field indicates that no client- a Search. A value of zero in this field indicates that no client-
requested time limit restrictions are in effect for the Search. requested time limit restrictions are in effect for the Search.
Servers may also enforce a maximum time limit for the Search. Servers may also enforce a maximum time limit for the Search.
4.5.1.6 SearchRequest.typesOnly 4.5.1.6. SearchRequest.typesOnly
An indicator as to whether Search results are to contain both An indicator as to whether Search results are to contain both
attribute descriptions and values, or just attribute descriptions. attribute descriptions and values, or just attribute descriptions.
Setting this field to TRUE causes only attribute descriptions (no Setting this field to TRUE causes only attribute descriptions (no
values) to be returned. Setting this field to FALSE causes both values) to be returned. Setting this field to FALSE causes both
attribute descriptions and values to be returned. attribute descriptions and values to be returned.
Sermersheim Internet-Draft - Expires April 2006 Page 21
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
4.5.1.7 SearchRequest.filter 4.5.1.7. SearchRequest.filter
A filter that defines the conditions that must be fulfilled in order A filter that defines the conditions that must be fulfilled in order
for the Search to match a given entry. for the Search to match a given entry.
The 'and', 'or' and 'not' choices can be used to form combinations of The 'and', 'or' and 'not' choices can be used to form combinations of
filters. At least one filter element MUST be present in an 'and' or filters. At least one filter element MUST be present in an 'and' or
'or' choice. The others match against individual attribute values of 'or' choice. The others match against individual attribute values of
entries in the scope of the Search. (Implementor's note: the 'not' entries in the scope of the Search. (Implementor's note: the 'not'
filter is an example of a tagged choice in an implicitly-tagged filter is an example of a tagged choice in an implicitly-tagged
module. In BER this is treated as if the tag was explicit.) module. In BER this is treated as if the tag was explicit.)
skipping to change at line 1146 skipping to change at line 1170
For example, if a server did not recognize the attribute type For example, if a server did not recognize the attribute type
shoeSize, the filters (shoeSize=*), (shoeSize=12), (shoeSize>=12) and shoeSize, the filters (shoeSize=*), (shoeSize=12), (shoeSize>=12) and
(shoeSize<=12) would each evaluate to Undefined. (shoeSize<=12) would each evaluate to Undefined.
Servers MUST NOT return errors if attribute descriptions or matching Servers MUST NOT return errors if attribute descriptions or matching
rule ids are not recognized, assertion values are invalid, or the rule ids are not recognized, assertion values are invalid, or the
assertion syntax is not supported. More details of filter processing assertion syntax is not supported. More details of filter processing
are given in Clause 7.8 of [X.511]. are given in Clause 7.8 of [X.511].
Sermersheim Internet-Draft - Expires April 2006 Page 22
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
4.5.1.7.1 SearchRequest.filter.equalityMatch 4.5.1.7.1. SearchRequest.filter.equalityMatch
The matching rule for an equalityMatch filter is defined by the The matching rule for an equalityMatch filter is defined by the
EQUALITY matching rule for the attribute type or subtype. The filter EQUALITY matching rule for the attribute type or subtype. The filter
is TRUE when the EQUALITY rule returns TRUE as applied to the is TRUE when the EQUALITY rule returns TRUE as applied to the
attribute or subtype and the asserted value. attribute or subtype and the asserted value.
4.5.1.7.2 SearchRequest.filter.substrings 4.5.1.7.2. SearchRequest.filter.substrings
There SHALL be at most one 'initial', and at most one 'final' in the There SHALL be at most one 'initial', and at most one 'final' in the
'substrings' of a SubstringFilter. If 'initial' is present, it SHALL 'substrings' of a SubstringFilter. If 'initial' is present, it SHALL
be the first element of 'substrings'. If 'final' is present, it SHALL be the first element of 'substrings'. If 'final' is present, it SHALL
be the last element of 'substrings'. be the last element of 'substrings'.
The matching rule for an AssertionValue in a substrings filter item The matching rule for an AssertionValue in a substrings filter item
is defined by the SUBSTR matching rule for the attribute type or is defined by the SUBSTR matching rule for the attribute type or
subtype. The filter is TRUE when the SUBSTR rule returns TRUE as subtype. The filter is TRUE when the SUBSTR rule returns TRUE as
applied to the attribute or subtype and the asserted value. applied to the attribute or subtype and the asserted value.
Note that the AssertionValue in a substrings filter item conforms to Note that the AssertionValue in a substrings filter item conforms to
the assertion syntax of the EQUALITY matching rule for the attribute the assertion syntax of the EQUALITY matching rule for the attribute
type rather than the assertion syntax of the SUBSTR matching rule for type rather than the assertion syntax of the SUBSTR matching rule for
the attribute type. Conceptually, the entire SubstringFilter is the attribute type. Conceptually, the entire SubstringFilter is
converted into an assertion value of the substrings matching rule converted into an assertion value of the substrings matching rule
prior to applying the rule. prior to applying the rule.
4.5.1.7.3 SearchRequest.filter.greaterOrEqual 4.5.1.7.3. SearchRequest.filter.greaterOrEqual
The matching rule for a greaterOrEqual filter is defined by the The matching rule for a greaterOrEqual filter is defined by the
ORDERING matching rule for the attribute type or subtype. The filter ORDERING matching rule for the attribute type or subtype. The filter
is TRUE when the ORDERING rule returns FALSE as applied to the is TRUE when the ORDERING rule returns FALSE as applied to the
attribute or subtype and the asserted value. attribute or subtype and the asserted value.
4.5.1.7.4 SearchRequest.filter.lessOrEqual 4.5.1.7.4. SearchRequest.filter.lessOrEqual
The matching rules for a lessOrEqual filter are defined by the The matching rules for a lessOrEqual filter are defined by the
ORDERING and EQUALITY matching rules for the attribute type or ORDERING and EQUALITY matching rules for the attribute type or
subtype. The filter is TRUE when either the ORDERING or EQUALITY rule subtype. The filter is TRUE when either the ORDERING or EQUALITY rule
returns TRUE as applied to the attribute or subtype and the asserted returns TRUE as applied to the attribute or subtype and the asserted
value. value.
4.5.1.7.5 SearchRequest.filter.present 4.5.1.7.5. SearchRequest.filter.present
A present filter is TRUE when there is an attribute or subtype of the A present filter is TRUE when there is an attribute or subtype of the
specified attribute description present in an entry, FALSE when no specified attribute description present in an entry, FALSE when no
attribute or subtype of the specified attribute description is attribute or subtype of the specified attribute description is
present in an entry, and Undefined otherwise. present in an entry, and Undefined otherwise.
Sermersheim Internet-Draft - Expires April 2006 Page 23
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
4.5.1.7.6 SearchRequest.filter.approxMatch 4.5.1.7.6. SearchRequest.filter.approxMatch
An approxMatch filter is TRUE when there is a value of the attribute An approxMatch filter is TRUE when there is a value of the attribute
type or subtype for which some locally-defined approximate matching type or subtype for which some locally-defined approximate matching
algorithm (e.g. spelling variations, phonetic match, etc.) returns algorithm (e.g. spelling variations, phonetic match, etc.) returns
TRUE. If a value matches for equality, it also satisfies an TRUE. If a value matches for equality, it also satisfies an
approximate match. If approximate matching is not supported for the approximate match. If approximate matching is not supported for the
attribute, this filter item should be treated as an equalityMatch. attribute, this filter item should be treated as an equalityMatch.
4.5.1.7.7 SearchRequest.filter.extensibleMatch 4.5.1.7.7. SearchRequest.filter.extensibleMatch
The fields of the extensibleMatch filter item are evaluated as The fields of the extensibleMatch filter item are evaluated as
follows: follows:
- If the matchingRule field is absent, the type field MUST be - If the matchingRule field is absent, the type field MUST be
present, and an equality match is performed for that type. present, and an equality match is performed for that type.
- If the type field is absent and the matchingRule is present, the - If the type field is absent and the matchingRule is present, the
matchValue is compared against all attributes in an entry which matchValue is compared against all attributes in an entry which
support that matchingRule. support that matchingRule.
skipping to change at line 1240 skipping to change at line 1266
entries and another applies to entries and DN attributes as well. entries and another applies to entries and DN attributes as well.
The matchingRule used for evaluation determines the syntax for the The matchingRule used for evaluation determines the syntax for the
assertion value. Once the matchingRule and attribute(s) have been assertion value. Once the matchingRule and attribute(s) have been
determined, the filter item evaluates to TRUE if it matches at least determined, the filter item evaluates to TRUE if it matches at least
one attribute type or subtype in the entry, FALSE if it does not one attribute type or subtype in the entry, FALSE if it does not
match any attribute type or subtype in the entry, and Undefined if match any attribute type or subtype in the entry, and Undefined if
the matchingRule is not recognized, the matchingRule is unsuitable the matchingRule is not recognized, the matchingRule is unsuitable
for use with the specified type, or the assertionValue is invalid. for use with the specified type, or the assertionValue is invalid.
4.5.1.7 SearchRequest.attributes 4.5.1.7. SearchRequest.attributes
A selection list of the attributes to be returned from each entry A selection list of the attributes to be returned from each entry
which matches the search filter. Attributes which are subtypes of which matches the search filter. Attributes which are subtypes of
listed attributes are implicitly included. LDAPString values of this listed attributes are implicitly included. 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]):
attributeSelector = attributedescription / selectorspecial attributeSelector = attributedescription / selectorspecial
Sermersheim Internet-Draft - Expires April 2006 Page 24
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
selectorspecial = noattrs / alluserattrs selectorspecial = noattrs / alluserattrs
noattrs = %x31.2E.31 ; "1.1" noattrs = %x31.2E.31 ; "1.1"
alluserattrs = %x2A ; asterisk ("*") alluserattrs = %x2A ; asterisk ("*")
The <attributedescription> production is defined in Section 2.5 of The <attributedescription> production is defined in Section 2.5 of
[Models]. [Models].
skipping to change at line 1302 skipping to change at line 1330
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 and/or SearchResultReference messages, followed by SearchResultEntry and/or SearchResultReference messages, followed by
a single SearchResultDone message. a single SearchResultDone message.
SearchResultEntry ::= [APPLICATION 4] SEQUENCE { SearchResultEntry ::= [APPLICATION 4] SEQUENCE {
objectName LDAPDN, objectName LDAPDN,
attributes PartialAttributeList } attributes PartialAttributeList }
Sermersheim Internet-Draft - Expires April 2006 Page 25
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
PartialAttributeList ::= SEQUENCE OF 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
skipping to change at line 1356 skipping to change at line 1386
baseObject but was unable or unwilling to search one or more non- baseObject but was unable or unwilling to search one or more non-
local entries, the server may return one or more local entries, the server may return one or more
SearchResultReference messages, each containing a reference to SearchResultReference messages, each containing a reference to
another set of servers for continuing the operation. A server MUST another set of servers for continuing the operation. A server MUST
NOT return any SearchResultReference messages if it has not located NOT return any SearchResultReference messages if it has not located
the baseObject and thus has not searched any entries; in this case it the baseObject and thus has not searched any entries; in this case it
would return a SearchResultDone containing either a referral or would return a SearchResultDone containing either a referral or
noSuchObject result code (depending on the server's knowledge of the noSuchObject result code (depending on the server's knowledge of the
entry named in the baseObject). entry named in the baseObject).
Sermersheim Internet-Draft - Expires April 2006 Page 26
Lightweight Directory Access Protocol Version 3 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.
skipping to change at line 1412 skipping to change at line 1443
of the LDAP URL will be "base". of the LDAP URL will be "base".
- It is RECOMMENDED that the <scope> part be present to avoid - It is RECOMMENDED that the <scope> part be present to avoid
ambiguity. In the absence of a <scope> part, the scope of the ambiguity. In the absence of a <scope> part, the scope of the
original Search request is assumed. original Search request is assumed.
- 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.
Sermersheim Internet-Draft - Expires April 2006 Page 27
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
- 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.
UTF-8 encoded characters appearing in the string representation of a UTF-8 encoded characters appearing in the string representation of a
skipping to change at line 1462 skipping to change at line 1494
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:
Sermersheim Internet-Draft - Expires April 2006 Page 28
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
SearchResultEntry for CN=Manager,DC=Example,DC=NET SearchResultEntry for CN=Manager,DC=Example,DC=NET
SearchResultReference { SearchResultReference {
ldap://hostb/OU=People,DC=Example,DC=NET??base ldap://hostb/OU=People,DC=Example,DC=NET??base
ldap://hostc/OU=People,DC=Example,DC=NET??base } ldap://hostc/OU=People,DC=Example,DC=NET??base }
SearchResultReference { SearchResultReference {
ldap://hostd/OU=Roles,DC=Example,DC=NET??base } ldap://hostd/OU=Roles,DC=Example,DC=NET??base }
SearchResultDone (success) SearchResultDone (success)
skipping to change at line 1517 skipping to change at line 1550
(such as the object class definition and DIT content rule), the (such as the object class definition and DIT content rule), the
resulting entry after the entire list of modifications is resulting entry after the entire list of modifications is
performed MUST conform to the requirements of the directory model performed MUST conform to the requirements of the directory model
and controlling schema [Models]. and controlling schema [Models].
- operation: Used to specify the type of modification being - operation: Used to specify the type of modification being
performed. Each operation type acts on the following performed. Each operation type acts on the following
modification. The values of this field have the following modification. The values of this field have the following
semantics respectively: semantics respectively:
Sermersheim Internet-Draft - Expires April 2006 Page 29
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
add: add values listed to the modification attribute, add: add values listed to the modification attribute,
creating the attribute if necessary; creating the attribute if necessary;
delete: delete values listed from the modification attribute. delete: delete values listed from the modification attribute.
If no values are listed, or if all current values of the If no values are listed, or if all current values of the
attribute are listed, the entire attribute is removed; attribute are listed, the entire attribute is removed;
replace: replace all existing values of the modification replace: replace all existing values of the modification
skipping to change at line 1573 skipping to change at line 1607
For attribute types which specify no equality matching, the rules in For attribute types which specify no equality matching, the rules in
Section 2.5.1 of [Models] are followed. Section 2.5.1 of [Models] are followed.
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
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.
Sermersheim Internet-Draft - Expires April 2006 Page 30
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
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 }
skipping to change at line 1627 skipping to change at line 1662
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.
4.8. Delete Operation 4.8. Delete Operation
The Delete operation allows a client to request the removal of an The Delete operation allows a client to request the removal of an
entry from the Directory. The Delete Request is defined as follows: entry from the Directory. The Delete Request is defined as follows:
DelRequest ::= [APPLICATION 10] LDAPDN DelRequest ::= [APPLICATION 10] LDAPDN
Sermersheim Internet-Draft - Expires April 2006 Page 31
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
The Delete Request consists of the name of the entry to be deleted. The Delete Request consists of the name of the entry to be deleted.
The server SHALL NOT dereference aliases while resolving the name of The server SHALL NOT dereference aliases while resolving the name of
the target entry to be removed. the target entry to be removed.
Only leaf entries (those with no subordinate entries) can be deleted Only leaf entries (those with no subordinate entries) can be deleted
with this operation. with this operation.
Upon receipt of a Delete Request, a server will attempt to perform Upon receipt of a Delete Request, a server will attempt to perform
skipping to change at line 1681 skipping to change at line 1718
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.
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:
Sermersheim Internet-Draft - Expires April 2006 Page 32
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
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
already an entry with that name, the operation would fail with the already an entry with that name, the operation would fail with the
entryAlreadyExists result code. entryAlreadyExists result code.
skipping to change at line 1737 skipping to change at line 1775
- 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 value assertion to be compared. - ava: holds the attribute value assertion to be compared.
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:
Sermersheim Internet-Draft - Expires April 2006 Page 33
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
CompareResponse ::= [APPLICATION 15] LDAPResult CompareResponse ::= [APPLICATION 15] LDAPResult
The resultCode is set to compareTrue, compareFalse, or an appropriate The resultCode is set to compareTrue, compareFalse, or an appropriate
error. compareTrue indicates that the assertion value in the ava error. compareTrue indicates that the assertion value in the ava
field matches a value of the attribute or subtype according to the field matches a value of the attribute or subtype according to the
attribute's EQUALITY matching rule. compareFalse indicates that the attribute's EQUALITY matching rule. compareFalse indicates that the
assertion value in the ava field and the values of the attribute or assertion value in the ava field and the values of the attribute or
subtype did not match. Other result codes indicate either that the subtype did not match. Other result codes indicate either that the
skipping to change at line 1791 skipping to change at line 1830
PDUs are transmitted. PDUs are transmitted.
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.
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).
Sermersheim Internet-Draft - Expires April 2006 Page 34
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
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
skipping to change at line 1827 skipping to change at line 1867
OCTET STRING. OCTET STRING.
The server will respond to this with an LDAPMessage containing an The server will respond to this with an LDAPMessage containing an
ExtendedResponse. ExtendedResponse.
ExtendedResponse ::= [APPLICATION 24] SEQUENCE { ExtendedResponse ::= [APPLICATION 24] SEQUENCE {
COMPONENTS OF LDAPResult, COMPONENTS OF LDAPResult,
responseName [10] LDAPOID OPTIONAL, responseName [10] LDAPOID OPTIONAL,
responseValue [11] OCTET STRING OPTIONAL } responseValue [11] OCTET STRING OPTIONAL }
The responseName is typically not required to be present as the The responseName field, when present, contains an LDAPOID which is
syntax and semantics of the response (including the format of the unique for this extended operation or response. This field is
responseValue) is implicitly known and associated with the request by optional (even when the extension specification specifies an LDAPOID
the messageID. to be returned in the field). The field will be absent whenever the
server is unable or unwilling to determine the appropriate LDAPOID to
return, for instance when the requestName cannot be parsed or its
value is not recognized.
If the Extended operation associated with the requestName is not Where the requestName is not recognized, the server returns
supported by the server, the server MUST NOT provide a responseName protocolError (The server may return protocolError in other cases).
nor a responseValue and MUST return with resultCode set to
protocolError.
The requestValue and responseValue fields contain any information The requestValue and responseValue fields contain information
associated with the operation. The format of these fields is defined associated with the operation. The format of these fields is defined
by the specification of the Extended operation. Implementations MUST by the specification of the Extended operation. Implementations MUST
be prepared to handle arbitrary contents of these fields, including be prepared to handle arbitrary contents of these fields, including
zero bytes. Values that are defined in terms of ASN.1 and BER encoded zero bytes. Values that are defined in terms of ASN.1 and BER encoded
according to Section 5.1, also follow the extensibility rules in according to Section 5.1, also follow the extensibility rules in
Section 4. Section 4.
Sermersheim Internet-Draft - Expires April 2006 Page 35
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
Servers list the requestName of Extended Requests they recognize in Servers list the requestName of Extended Requests they recognize in
the 'supportedExtension' attribute in the root DSE (Section 5.1 of the 'supportedExtension' attribute in the root DSE (Section 5.1 of
[Models]). [Models]).
Extended operations may be specified in other documents. The Extended operations may be specified in other documents. The
specification of an Extended operation consists of: specification of an Extended operation consists of:
- the OBJECT IDENTIFIER assigned to the requestName, - the OBJECT IDENTIFIER assigned to the requestName,
- the OBJECT IDENTIFIER (if any) assigned to the responseName (note - the OBJECT IDENTIFIER (if any) assigned to the responseName (note
that the same OBJECT IDENTIFIER my be used for both the that the same OBJECT IDENTIFIER may be used for both the
requestName and responseName), requestName and responseName),
- the format of the contents of the requestValue and responseValue - the format of the contents of the requestValue and responseValue
(if any), and (if any), and
- the semantics of the operation. - the semantics of the operation.
4.13. IntermediateResponse Message 4.13. IntermediateResponse Message
While the Search operation provides a mechanism to return multiple While the Search operation provides a mechanism to return multiple
skipping to change at line 1900 skipping to change at line 1942
unless the client issues a request that specifically solicits their unless the client issues a request that specifically solicits their
return. This document defines two forms of solicitation: Extended return. This document defines two forms of solicitation: Extended
operation and request control. IntermediateResponse messages are operation and request control. IntermediateResponse messages are
specified in documents describing the manner in which they are specified in documents describing the manner in which they are
solicited (i.e. in the Extended operation or request control solicited (i.e. in the Extended operation or request control
specification that uses them). These specifications include: specification that uses them). These specifications include:
- the OBJECT IDENTIFIER (if any) assigned to the responseName, - the OBJECT IDENTIFIER (if any) assigned to the responseName,
- the format of the contents of the responseValue (if any), and - the format of the contents of the responseValue (if any), and
Sermersheim Internet-Draft - Expires April 2006 Page 36
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
- the semantics associated with the IntermediateResponse message. - the semantics associated with the IntermediateResponse message.
Extensions that allow the return of multiple types of Extensions that allow the return of multiple types of
IntermediateResponse messages SHALL identify those types using unique IntermediateResponse messages SHALL identify those types using unique
responseName values (note that one of these may specify no value). responseName values (note that one of these may specify no value).
Sections 4.13.1 and 4.13.2 describe additional requirements on the Sections 4.13.1 and 4.13.2 describe additional requirements on the
inclusion of responseName and responseValue in IntermediateResponse inclusion of responseName and responseValue in IntermediateResponse
skipping to change at line 1945 skipping to change at line 1989
included in a request with an LDAP Extended operation that uses included in a request with an LDAP Extended operation that uses
IntermediateResponse messages. IntermediateResponse messages.
4.14. StartTLS Operation 4.14. StartTLS Operation
The Start Transport Layer Security (StartTLS) operation's purpose is The Start Transport Layer Security (StartTLS) operation's purpose is
to initiate installation of a TLS layer. The StartTLS operation is to initiate installation of a TLS layer. The StartTLS operation is
defined using the Extended operation mechanism described in Section defined using the Extended operation mechanism described in Section
4.12. 4.12.
Sermersheim Internet-Draft - Expires April 2006 Page 37
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
4.14.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 message to the server. The StartTLS request is defined in request message to the server. The StartTLS request is defined in
terms of an ExtendedRequest. The requestName is terms of an ExtendedRequest. The requestName is
"1.3.6.1.4.1.1466.20037", and the requestValue field is always "1.3.6.1.4.1.1466.20037", and the requestValue field is always
absent. absent.
skipping to change at line 1970 skipping to change at line 2015
Detected sequencing problems (particularly those detailed in Section Detected sequencing problems (particularly those detailed in Section
3.1.1 of [AuthMeth]) result in the resultCode being set to 3.1.1 of [AuthMeth]) result in the resultCode being set to
operationsError. operationsError.
If the server does not support TLS (whether by design or by current If the server does not support TLS (whether by design or by current
configuration), it returns with the resultCode set to protocolError configuration), it returns with the resultCode set to protocolError
as described in Section 4.12. as described in Section 4.12.
4.14.2. StartTLS Response 4.14.2. StartTLS Response
When a StartTLS request is made, servers supporting the operation When a StartTLS request is received, servers supporting the operation
MUST return a StartTLS response message to the requestor. The MUST return a StartTLS response message to the requestor. The
responseName, if present, is also "1.3.6.1.4.1.1466.20037". The responseName is "1.3.6.1.4.1.1466.20037" when provided (See 4.12).
responseValue is absent. The responseValue is always absent.
If the server is willing and able to negotiate TLS, it returns with If the server is willing and able to negotiate TLS, it returns the
the resultCode set to success. Refer to Section 4 of [AuthMeth] for StartTLS response with the resultCode set to success. Upon client
details. receipt of a successful StartTLS response, protocol peers may
commence with TLS negotiation as discussed in Section 3 of
[AuthMeth].
If the server is otherwise unwilling or unable to perform this If the server is otherwise unwilling or unable to perform this
operation, the server is to return an appropriate result code operation, the server is to return an appropriate result code
indicating the nature of the problem. For example, if the TLS indicating the nature of the problem. For example, if the TLS
subsystem is not presently available, the server may indicate so by subsystem is not presently available, the server may indicate so by
returning with the resultCode set to unavailable. returning with the resultCode set to unavailable. In cases where a
non-success result code is returned, the LDAP session is left without
a TLS layer.
4.14.3. Removal of the TLS Layer 4.14.3. Removal of the TLS Layer
Either the client or server MAY remove the TLS layer and leave the Either the client or server MAY remove the TLS layer and leave the
LDAP message layer intact by sending and receiving a TLS closure LDAP message layer intact by sending and receiving a TLS closure
alert. alert.
Sermersheim Internet-Draft - Expires April 2006 Page 38
Lightweight Directory Access Protocol Version 3
The initiating protocol peer sends the TLS closure alert and MUST The initiating protocol peer sends the TLS closure alert and MUST
wait until it receives a TLS closure alert from the other peer before wait until it receives a TLS closure alert from the other peer before
sending further LDAP PDUs. sending further LDAP PDUs.
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 LDAP message layer to remain intact. In this choose to allow the LDAP message layer to remain intact. In this
case, it MUST immediately transmit a TLS closure alert. Following case, it MUST immediately transmit a TLS closure alert. Following
this, it MAY send and receive LDAP PDUs. this, it MAY send and receive LDAP PDUs.
Protocol peers MAY terminate the LDAP session after sending or Protocol peers MAY terminate the LDAP session after sending or
receiving a TLS closure alert. receiving a TLS closure alert.
5. Protocol Encoding, Connection, and Transfer 5. Protocol Encoding, Connection, and Transfer
skipping to change at line 2045 skipping to change at line 2095
+----------------------+ +----------------------+
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. Sermersheim Internet-Draft - Expires April 2006 Page 39
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
- 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.
skipping to change at line 2097 skipping to change at line 2148
In either case, when the LDAP session is terminated, uncompleted In either case, when the LDAP session is terminated, uncompleted
operations are handled as specified in Section 3.1. operations are handled as specified in Section 3.1.
6. Security Considerations 6. Security Considerations
This version of the protocol provides facilities for simple This version of the protocol provides facilities for simple
authentication using a cleartext password, as well as any [SASL] authentication using a cleartext password, as well as any [SASL]
mechanism. Installing SASL and/or TLS layers can provide integrity mechanism. Installing SASL and/or TLS layers can provide integrity
and other data security services. and other data security services.
Sermersheim Internet-Draft - Expires April 2006 Page 40
Lightweight Directory Access Protocol Version 3
It is also permitted that the server can return its credentials to It is also permitted that the server can return its credentials to
the client, if it chooses to do so. the client, if it chooses to do so.
Lightweight Directory Access Protocol Version 3
Use of cleartext password is strongly discouraged where the Use of cleartext password is strongly discouraged where the
underlying transport service cannot guarantee confidentiality and may underlying transport service cannot guarantee confidentiality and may
result in disclosure of the password to unauthorized parties. result in disclosure of the password to unauthorized parties.
Servers are encouraged to prevent directory modifications by clients Servers are encouraged to prevent directory modifications by clients
that have authenticated anonymously [AuthMeth]. that have authenticated anonymously [AuthMeth].
Security considerations for authentication methods, SASL mechanisms, Security considerations for authentication methods, SASL mechanisms,
and TLS are described in [AuthMeth]. and TLS are described in [AuthMeth].
skipping to change at line 2147 skipping to change at line 2199
minimally, to exclude the return of sensitive data. minimally, to exclude the return of sensitive data.
Implementations which cache attributes and entries obtained via LDAP Implementations which cache attributes and entries obtained via LDAP
MUST ensure that access controls are maintained if that information MUST ensure that access controls are maintained if that information
is to be provided to multiple clients, since servers may have access is to be provided to multiple clients, since servers may have access
control policies which prevent the return of entries or attributes in control policies which prevent the return of entries or attributes in
Search results except to particular authenticated clients. For Search results except to particular authenticated clients. For
example, caches could serve result information only to the client example, caches could serve result information only to the client
whose request caused it to be in the cache. whose request caused it to be in the cache.
Sermersheim Internet-Draft - Expires April 2006 Page 41
Lightweight Directory Access Protocol Version 3
Servers may return referrals or Search result references which Servers may return referrals or Search result references which
redirect clients to peer servers. It is possible for a rogue redirect clients to peer servers. It is possible for a rogue
application to inject such referrals into the data stream in an application to inject such referrals into the data stream in an
attempt to redirect a client to a rogue server. Clients are advised attempt to redirect a client to a rogue server. Clients are advised
to be aware of this, and possibly reject referrals when to be aware of this, and possibly reject referrals when
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.
Lightweight Directory Access Protocol Version 3
The matchedDN and diagnosticMessage fields, as well as some The matchedDN and diagnosticMessage fields, as well as some
resultCode values (e.g., attributeOrValueExists and resultCode values (e.g., attributeOrValueExists and
entryAlreadyExists), could disclose the presence or absence of entryAlreadyExists), could disclose the presence or absence of
specific data in the directory which is subject to access and other specific data in the directory which is subject to access and other
administrative controls. Server implementations should restrict administrative controls. Server implementations should restrict
access to protected information equally under both normal and error access to protected information equally under both normal and error
conditions. conditions.
Protocol peers MUST be prepared to handle invalid and arbitrary Protocol peers MUST be prepared to handle invalid and arbitrary
length protocol encodings. Invalid protocol encodings include: BER length protocol encodings. Invalid protocol encodings include: BER
skipping to change at line 2199 skipping to change at line 2252
This document is a product of the IETF LDAPBIS Working Group. This document is a product of the IETF LDAPBIS Working Group.
Significant contributors of technical review and content include Kurt Significant contributors of technical review and content include Kurt
Zeilenga, Steven Legg, and Hallvard Furuseth. Zeilenga, Steven Legg, and Hallvard Furuseth.
8. Normative References 8. Normative References
[ABNF] Crocker, D. and P. Overell, "Augmented BNF for Syntax [ABNF] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", draft-crocker-abnf-rfc2234bis- Specifications: ABNF", draft-crocker-abnf-rfc2234bis-
xx.txt, (a work in progress). xx.txt, (a work in progress).
Sermersheim Internet-Draft - Expires April 2006 Page 42
Lightweight Directory Access Protocol Version 3
[ASN.1] ITU-T Recommendation X.680 (07/2002) | ISO/IEC 8824-1:2002 [ASN.1] ITU-T Recommendation X.680 (07/2002) | ISO/IEC 8824-1:2002
"Information Technology - Abstract Syntax Notation One "Information Technology - Abstract Syntax Notation One
(ASN.1): Specification of basic notation" (ASN.1): Specification of basic notation"
[AuthMeth] Harrison, R., "LDAP: Authentication Methods and Connection [AuthMeth] Harrison, R., "LDAP: Authentication Methods and Connection
Level Security Mechanisms", draft-ietf-ldapbis-authmeth- Level Security Mechanisms", draft-ietf-ldapbis-authmeth-
xx.txt, (a work in progress). xx.txt, (a work in progress).
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 2256 skipping to change at line 2310
progress). progress).
[StringPrep] Hoffman P. and M. Blanchet, "Preparation of [StringPrep] Hoffman P. and M. Blanchet, "Preparation of
Internationalized Strings ('stringprep')", draft-hoffman- Internationalized Strings ('stringprep')", draft-hoffman-
rfc3454bis-xx.txt, a work in progress. rfc3454bis-xx.txt, a work in progress.
[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).
Sermersheim Internet-Draft - Expires April 2006 Page 43
Lightweight Directory Access Protocol Version 3
[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.
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 2306 skipping to change at line 2361
[PROTOS-LDAP] University of Oulu, "PROTOS Test-Suite: c06-ldapv3" [PROTOS-LDAP] University of Oulu, "PROTOS Test-Suite: c06-ldapv3"
<http://www.ee.oulu.fi/research/ouspg/protos/testing/c06/l <http://www.ee.oulu.fi/research/ouspg/protos/testing/c06/l
dapv3/> dapv3/>
[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
Sermersheim Internet-Draft - Expires April 2006 Page 44
Lightweight Directory Access Protocol Version 3
It is requested that the Internet Assigned Numbers Authority (IANA) It is requested that the Internet Assigned Numbers Authority (IANA)
update the LDAP result code registry to indicate that this document update the LDAP result code registry to indicate that this document
provides the definitive technical specification for result codes 0- provides the definitive technical specification for result codes 0-
36, 48-54, 64-70, 80-90. It is also noted that one resultCode value 36, 48-54, 64-70, 80-90. It is also noted that one resultCode value
(strongAuthRequired) has been renamed (to strongerAuthRequired). (strongAuthRequired) has been renamed (to strongerAuthRequired).
It is requested that the IANA update the LDAP Protocol Mechanism It is requested that the IANA update the LDAP Protocol Mechanism
registry to indicate that this document and [AuthMeth] provides the registry to indicate that this document and [AuthMeth] provides the
definitive technical specification for the StartTLS definitive technical specification for the StartTLS
(1.3.6.1.4.1.1466.20037) Extended operation. (1.3.6.1.4.1.1466.20037) Extended operation.
Lightweight Directory Access Protocol Version 3
It is requested that the IANA update the occurrence of "RFC XXXX" in It is requested that the IANA update the occurrence of "RFC XXXX" in
Appendix B with this RFC number at publication. this section and Appendix B with this RFC number at publication.
It is requested that IANA assign upon Standards Action an LDAP Object
Identifier [LDAPIANA] to identify the ASN.1 module defined in this
document.
Subject: Request for LDAP Object Identifier Registration
Person & email address to contact for further information:
Jim Sermersheim <jimse@novell.com>
Specification: RFC XXXX
Author/Change Controller: IESG
Comments:
Identifies the LDAP ASN.1 module
[[Note to RFC Editor: please replace the occurrence of <IANA-
ASSIGNED-DIRECTORY-NUMBER> in Appendix B with the IANA assigned
OID.]]
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 April 2006 Page 45
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
they do not recognize as an unknown error condition. they do not recognize as an unknown error condition.
Servers may substitute some result codes due to access controls which The descriptions provided here do not fully account for result code
prevent their disclosure. substitutions used to prevent unauthorized disclosures (such as
substitution of noSuchObject for insufficientAccessRights, or
invalidCredentials for insufficientAccessRights).
A.1 Non-Error Result Codes A.1. Non-Error Result Codes
These result codes (called "non-error" result codes) do not indicate These result codes (called "non-error" result codes) do not indicate
an error condition: an error condition:
success (0), success (0),
compareFalse (5), compareFalse (5),
compareTrue (6), compareTrue (6),
referral (10), and referral (10), and
saslBindInProgress (14). saslBindInProgress (14).
The success, compareTrue, and compareFalse result codes indicate The success, compareTrue, and compareFalse result codes indicate
successful completion (and, hence, are referred to as "successful" successful completion (and, hence, are referred to as "successful"
result codes). result codes).
The referral and saslBindInProgress result codes indicate the client The referral and saslBindInProgress result codes indicate the client
needs to take additional action to complete the operation. needs to take additional action to complete the operation.
A.2 Result Codes A.2. Result Codes
Existing LDAP result codes are described as follows: Existing LDAP result codes are described as follows:
success (0) success (0)
Indicates the successful completion of an operation. Note: Indicates the successful completion of an operation. Note:
this code is not used with the Compare operation. See this code is not used with the Compare operation. See
compareFalse (5) and compareTrue (6). compareFalse (5) and compareTrue (6).
operationsError (1) operationsError (1)
Indicates that the operation is not properly sequenced with Indicates that the operation is not properly sequenced with
relation to other operations (of same or different type). relation to other operations (of same or different type).
For example, this code is returned if the client attempts to For example, this code is returned if the client attempts to
StartTLS [TLS] while there are other uncompleted operations StartTLS [TLS] while there are other uncompleted operations
or if a TLS layer was already installed. or if a TLS layer was already installed.
protocolError (2) protocolError (2)
Indicates the server received data which is not well-formed. Indicates the server received data which is not well-formed.
Sermersheim Internet-Draft - Expires April 2006 Page 46
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
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.
For Extended operations only, this code is also used to For Extended operations only, this code is also used to
indicate that the server does not support (by design or indicate that the server does not support (by design or
configuration) the Extended operation associated with the configuration) the Extended operation associated with the
requestName. requestName.
skipping to change at line 2439 skipping to change at line 2516
Indicates that a referral needs to be chased to complete the Indicates that a referral needs to be chased to complete the
operation (see Section 4.1.10). operation (see Section 4.1.10).
adminLimitExceeded (11) adminLimitExceeded (11)
Indicates that an administrative limit has been exceeded. Indicates that an administrative limit has been exceeded.
unavailableCriticalExtension (12) unavailableCriticalExtension (12)
Indicates a critical control is unrecognized (see Section Indicates a critical control is unrecognized (see Section
4.1.11). 4.1.11).
Sermersheim Internet-Draft - Expires April 2006 Page 47
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
confidentialityRequired (13) confidentialityRequired (13)
Indicates that data confidentiality protections are required. Indicates that data confidentiality protections are required.
saslBindInProgress (14) saslBindInProgress (14)
Indicates the server requires the client to send a new bind Indicates the server requires the client to send a new bind
request, with the same SASL mechanism, to continue the request, with the same SASL mechanism, to continue the
authentication process (see Section 4.2). authentication process (see Section 4.2).
skipping to change at line 2494 skipping to change at line 2572
the code may used to indicate an alias has been dereferenced the code may used to indicate an alias has been dereferenced
which names no object. which names no object.
invalidDNSyntax (34) invalidDNSyntax (34)
Indicates that an LDAPDN or RelativeLDAPDN field (e.g. search Indicates that an LDAPDN or RelativeLDAPDN field (e.g. search
base, target entry, ModifyDN newrdn, etc.) of a request does base, target entry, ModifyDN newrdn, etc.) of a request does
not conform to the required syntax or contains attribute not conform to the required syntax or contains attribute
values which do not conform to the syntax of the attribute's values which do not conform to the syntax of the attribute's
type. type.
Sermersheim Internet-Draft - Expires April 2006 Page 48
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
aliasDereferencingProblem (36) aliasDereferencingProblem (36)
Indicates that a problem occurred while dereferencing an Indicates that a problem occurred while dereferencing an
alias. Typically an alias was encountered in a situation alias. Typically an alias was encountered in a situation
where it was not allowed or where access was denied. where it was not allowed or where access was denied.
inappropriateAuthentication (48) inappropriateAuthentication (48)
Indicates the server requires the client which had attempted Indicates the server requires the client which had attempted
to bind anonymously or without supplying credentials to to bind anonymously or without supplying credentials to
skipping to change at line 2549 skipping to change at line 2628
notAllowedOnRDN (67) notAllowedOnRDN (67)
Indicates that the operation is inappropriately attempting to Indicates that the operation is inappropriately attempting to
remove a value which forms the entry's relative distinguished remove a value which forms the entry's relative distinguished
name. name.
entryAlreadyExists (68) entryAlreadyExists (68)
Indicates that the request cannot be fulfilled (added, moved, Indicates that the request cannot be fulfilled (added, moved,
or renamed) as the target entry already exists. or renamed) as the target entry already exists.
Sermersheim Internet-Draft - Expires April 2006 Page 49
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
objectClassModsProhibited (69) objectClassModsProhibited (69)
Indicates that an attempt to modify the object class(es) of Indicates that an attempt to modify the object class(es) of
an entry's 'objectClass' attribute is prohibited. an entry's 'objectClass' attribute is prohibited.
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 performed as it would Indicates that the operation cannot be performed as it would
affect multiple servers (DSAs). affect 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 April 2006 Page 50
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 {1 3 6 1 1 <IANA-
ASSIGNED-DIRECTORY-NUMBER>}
-- Copyright (C) The Internet Society (2005). This version of -- Copyright (C) The Internet Society (2005). This version of
-- this ASN.1 module is part of RFC XXXX; see the RFC itself -- this ASN.1 module is part of RFC XXXX; see the RFC itself
-- for full legal notices. -- for full legal notices.
DEFINITIONS DEFINITIONS
IMPLICIT TAGS IMPLICIT TAGS
EXTENSIBILITY IMPLIED ::= EXTENSIBILITY IMPLIED ::=
BEGIN BEGIN
LDAPMessage ::= SEQUENCE { LDAPMessage ::= SEQUENCE {
skipping to change at line 2619 skipping to change at line 2701
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]
Sermersheim Internet-Draft - Expires April 2006 Page 51
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
RelativeLDAPDN ::= LDAPString -- Constrained to <name-component> RelativeLDAPDN ::= LDAPString -- Constrained to <name-component>
-- [LDAPDN] -- [LDAPDN]
AttributeDescription ::= LDAPString AttributeDescription ::= LDAPString
-- Constrained to <attributedescription> -- Constrained to <attributedescription>
-- [Models] -- [Models]
AttributeValue ::= OCTET STRING AttributeValue ::= OCTET STRING
skipping to change at line 2645 skipping to change at line 2729
PartialAttribute ::= SEQUENCE { PartialAttribute ::= SEQUENCE {
type AttributeDescription, type AttributeDescription,
vals SET OF value AttributeValue } vals SET OF value AttributeValue }
Attribute ::= PartialAttribute(WITH COMPONENTS { Attribute ::= PartialAttribute(WITH COMPONENTS {
..., ...,
vals (SIZE(1..MAX))}) vals (SIZE(1..MAX))})
MatchingRuleId ::= LDAPString MatchingRuleId ::= LDAPString
Sermersheim Internet-Draft - Expires April 2006 Page 52
Lightweight Directory Access Protocol Version 3 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),
skipping to change at line 2701 skipping to change at line 2787
-- 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 }
Referral ::= SEQUENCE SIZE (1..MAX) OF uri URI Referral ::= SEQUENCE SIZE (1..MAX) OF uri URI
Sermersheim Internet-Draft - Expires April 2006 Page 53
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
URI ::= LDAPString -- limited to characters permitted in URI ::= LDAPString -- limited to characters permitted in
-- URIs -- URIs
Controls ::= SEQUENCE OF control Control Controls ::= SEQUENCE OF control Control
Control ::= SEQUENCE { Control ::= SEQUENCE {
controlType LDAPOID, controlType LDAPOID,
criticality BOOLEAN DEFAULT FALSE, criticality BOOLEAN DEFAULT FALSE,
skipping to change at line 2755 skipping to change at line 2843
derefAlways (3) }, derefAlways (3) },
sizeLimit INTEGER (0 .. maxInt), sizeLimit INTEGER (0 .. maxInt),
timeLimit INTEGER (0 .. maxInt), timeLimit INTEGER (0 .. maxInt),
typesOnly BOOLEAN, typesOnly BOOLEAN,
filter Filter, filter Filter,
attributes AttributeSelection } attributes AttributeSelection }
AttributeSelection ::= SEQUENCE OF selector LDAPString AttributeSelection ::= SEQUENCE OF selector LDAPString
-- The LDAPString is constrained to -- The LDAPString is constrained to
-- <attributeSelector> in Section 4.5.1.7 -- <attributeSelector> in Section 4.5.1.7
Sermersheim Internet-Draft - Expires April 2006 Page 54
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
Filter ::= CHOICE { Filter ::= CHOICE {
and [0] SET SIZE (1..MAX) OF filter Filter, and [0] SET SIZE (1..MAX) OF filter Filter,
or [1] SET SIZE (1..MAX) OF filter Filter, or [1] SET SIZE (1..MAX) OF filter Filter,
not [2] Filter, not [2] Filter,
equalityMatch [3] AttributeValueAssertion, equalityMatch [3] AttributeValueAssertion,
substrings [4] SubstringFilter, substrings [4] SubstringFilter,
greaterOrEqual [5] AttributeValueAssertion, greaterOrEqual [5] AttributeValueAssertion,
lessOrEqual [6] AttributeValueAssertion, lessOrEqual [6] AttributeValueAssertion,
skipping to change at line 2811 skipping to change at line 2901
delete (1), delete (1),
replace (2), replace (2),
... }, ... },
modification PartialAttribute } } modification PartialAttribute } }
ModifyResponse ::= [APPLICATION 7] LDAPResult ModifyResponse ::= [APPLICATION 7] LDAPResult
AddRequest ::= [APPLICATION 8] SEQUENCE { AddRequest ::= [APPLICATION 8] SEQUENCE {
entry LDAPDN, entry LDAPDN,
attributes AttributeList } attributes AttributeList }
Sermersheim Internet-Draft - Expires April 2006 Page 55
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
AttributeList ::= SEQUENCE OF attribute Attribute AttributeList ::= SEQUENCE OF attribute Attribute
AddResponse ::= [APPLICATION 9] LDAPResult AddResponse ::= [APPLICATION 9] LDAPResult
DelRequest ::= [APPLICATION 10] LDAPDN DelRequest ::= [APPLICATION 10] LDAPDN
DelResponse ::= [APPLICATION 11] LDAPResult DelResponse ::= [APPLICATION 11] LDAPResult
skipping to change at line 2851 skipping to change at line 2943
ExtendedResponse ::= [APPLICATION 24] SEQUENCE { ExtendedResponse ::= [APPLICATION 24] SEQUENCE {
COMPONENTS OF LDAPResult, COMPONENTS OF LDAPResult,
responseName [10] LDAPOID OPTIONAL, responseName [10] LDAPOID OPTIONAL,
responseValue [11] OCTET STRING OPTIONAL } responseValue [11] OCTET STRING OPTIONAL }
IntermediateResponse ::= [APPLICATION 25] SEQUENCE { IntermediateResponse ::= [APPLICATION 25] SEQUENCE {
responseName [0] LDAPOID OPTIONAL, responseName [0] LDAPOID OPTIONAL,
responseValue [1] OCTET STRING OPTIONAL } responseValue [1] OCTET STRING OPTIONAL }
END END
Sermersheim Internet-Draft - Expires April 2006 Page 56
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, RFC This appendix summarizes substantive changes made to RFC 2251, RFC
2830, and RFC 3771. 2830, and RFC 3771.
C.1 Changes made to RFC 2251: C.1. Changes made to RFC 2251:
This section summarizes the substantive changes made to Sections 1, This section summarizes the substantive changes made to Sections 1,
2, 3.1, and 4 through the remainder of RFC 2251. Readers should 2, 3.1, and 4 through the remainder of RFC 2251. Readers should
consult [Models] and [AuthMeth] for summaries of changes to other consult [Models] and [AuthMeth] for summaries of changes to other
sections. sections.
C.1.1 Section 1 (Status of this Memo) C.1.1. Section 1 (Status of this Memo)
- Removed IESG note. Post publication of RFC 2251, mandatory LDAP - Removed IESG note. Post publication of RFC 2251, mandatory LDAP
authentication mechanisms have been standardized which are authentication mechanisms have been standardized which are
sufficient to remove this note. See [AuthMeth] for authentication sufficient to remove this note. See [AuthMeth] for authentication
mechanisms. mechanisms.
C.1.2 Section 3.1 (Protocol Model) and others C.1.2. Section 3.1 (Protocol Model) and others
- Removed notes giving history between LDAP v1, v2 and v3. Instead, - Removed notes giving history between LDAP v1, v2 and v3. Instead,
added sufficient language so that this document can stand on its added sufficient language so that this document can stand on its
own. own.
C.1.3 Section 4 (Elements of Protocol) C.1.3. Section 4 (Elements of Protocol)
- Clarified where the extensibility features of ASN.1 apply to the - Clarified where the extensibility features of ASN.1 apply to the
protocol. This change affected various ASN.1 types by the protocol. This change affected various ASN.1 types by the
inclusion of ellipses (...) to certain elements. inclusion of ellipses (...) to certain elements.
- Removed the requirement that servers which implement version 3 or - Removed the requirement that servers which implement version 3 or
later MUST provide the 'supportedLDAPVersion' attribute. This later MUST provide the 'supportedLDAPVersion' attribute. This
statement provided no interoperability advantages. statement provided no interoperability advantages.
C.1.4 Section 4.1.1 (Message Envelope) C.1.4. Section 4.1.1 (Message Envelope)
- 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 transport connection when a Notice of Disconnection and drop the transport connection when a
PDU is malformed in a certain way. This has been updated such that PDU is malformed in a certain way. This has been updated such that
the server SHOULD return the Notice of Disconnection, and MUST the server SHOULD return the Notice of Disconnection, and MUST
terminate the LDAP Session. terminate the LDAP Session.
C.1.5 Section 4.1.1.1 (Message ID) C.1.5. Section 4.1.1.1 (Message ID)
- Required that the messageID of requests MUST be non-zero as the - Required that the messageID of requests MUST be non-zero as the
zero is reserved for Notice of Disconnection. zero is reserved for Notice of Disconnection.
Sermersheim Internet-Draft - Expires April 2006 Page 57
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
- Specified when it is and isn't appropriate to return an already - Specified 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 (String Types) C.1.6. Section 4.1.2 (String Types)
- Stated that LDAPOID is constrained to <numericoid> from [Models]. - Stated that LDAPOID is constrained to <numericoid> from [Models].
C.1.7 Section 4.1.5.1 (Binary Option) and others C.1.7. Section 4.1.5.1 (Binary Option) and others
- Removed the Binary Option from the specification. There are - Removed the Binary Option from the specification. There are
numerous interoperability problems associated with this method of numerous interoperability problems associated with this method of
alternate attribute type encoding. Work to specify a suitable alternate attribute type encoding. Work to specify a suitable
replacement is ongoing. replacement is ongoing.
C.1.8 Section 4.1.8 (Attribute) C.1.8. Section 4.1.8 (Attribute)
- Combined the definitions of PartialAttribute and Attribute here, - Combined the definitions of PartialAttribute and Attribute here,
and defined Attribute in terms of PartialAttribute. and defined Attribute in terms of PartialAttribute.
C.1.9 Section 4.1.10 (Result Message) C.1.9. Section 4.1.10 (Result Message)
- Renamed "errorMessage" to "diagnosticMessage" as it is allowed to - Renamed "errorMessage" to "diagnosticMessage" as it is allowed to
be sent for non-error results. be sent for non-error results.
- Moved some language into Appendix A, and refer the reader there. - Moved some language into Appendix A, and refer the reader there.
- Allowed matchedDN to be present for other result codes than those - Allowed matchedDN to be present for other result codes than those
listed in RFC 2251. listed in RFC 2251.
- renamed the code "strongAuthRequired" to "strongerAuthRequired" to - renamed the code "strongAuthRequired" to "strongerAuthRequired" to
clarify that this code may often be returned to indicate that a clarify that this code may often be returned to indicate that a
stronger authentication is needed to perform a given operation. stronger authentication is needed to perform a given operation.
C.1.10 Section 4.1.11 (Referral) C.1.10. Section 4.1.11 (Referral)
- 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.
- Removed imperatives which required clients to use URLs in specific - Removed imperatives which required clients to use URLs in specific
ways to progress an operation. These did nothing for ways to progress an operation. These did nothing for
interoperability. interoperability.
C.1.11 Section 4.1.12 (Controls) C.1.11. Section 4.1.12 (Controls)
- 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.
Sermersheim Internet-Draft - Expires April 2006 Page 58
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
- Noted that the criticality field is only applied to request - Noted that the criticality field is only applied to request
messages (except UnbindRequest), and must be ignored when present messages (except UnbindRequest), and must be ignored when present
on response messages and UnbindRequest. on response messages and UnbindRequest.
- Specified that non-critical controls may be ignored at the - Specified that non-critical controls may be ignored at the
server's discretion. There was confusion in the original wording server's discretion. There was confusion in the original wording
which led some to believe that recognized controls may not be which led some to believe that recognized controls may not be
ignored as long as they were associated with a proper request. ignored as long as they were associated with a proper request.
- Added language regarding combinations of controls and the ordering - Added language regarding combinations of controls and the ordering
of controls on a message. of controls on a message.
- Specified that when the semantics of the combination of controls - Specified that when the semantics of the combination of controls
is undefined or unknown, it results in a protocolError. is undefined or unknown, it results in a protocolError.
- 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.12 Section 4.2 (Bind Operation) C.1.12. Section 4.2 (Bind Operation)
- Mandated that servers return protocolError when the version is not - Mandated that servers return protocolError when the version is not
supported. supported.
- Disambiguated behavior when the simple authentication is used, the - Disambiguated behavior when the simple authentication is used, the
name is empty and the password is non-empty. name is empty and the password is non-empty.
- Required servers to not dereference aliases for Bind. This was - Required servers to not dereference aliases for Bind. 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.
- Required that textual passwords be transferred as UTF-8 encoded - Required that textual passwords be transferred as UTF-8 encoded
Unicode, and added recommendations on string preparation. This was Unicode, and added recommendations on string preparation. This was
to help ensure interoperability of passwords being sent from to help ensure interoperability of passwords being sent from
different clients. different clients.
C.1.13 Section 4.2.1 (Sequencing of the Bind Request) C.1.13. Section 4.2.1 (Sequencing of the Bind Request)
- This section was largely reorganized for readability and language - This section was largely reorganized for readability and language
was added to clarify the authentication state of failed and was added to clarify the authentication state of failed and
abandoned Bind operations. abandoned Bind operations.
- Removed: "If a SASL transfer encryption or integrity mechanism has - Removed: "If a SASL transfer encryption or integrity mechanism has
been negotiated, that mechanism does not support the changing of been negotiated, that mechanism does not support the changing of
credentials from one identity to another, then the client MUST credentials from one identity to another, then the client MUST
instead establish a new connection." instead establish a new connection."
If there are dependencies between multiple negotiations of a If there are dependencies between multiple negotiations of a
particular SASL mechanism, the technical specification for that particular SASL mechanism, the technical specification for that
SASL mechanism details how applications are to deal with them. SASL mechanism details how applications are to deal with them.
LDAP should not require any special handling. LDAP should not require any special handling.
- Dropped MUST imperative in paragraph 3 to align with [Keywords]. - Dropped MUST imperative in paragraph 3 to align with [Keywords].
- Mandated that clients not send non-Bind operations while a Bind is - Mandated that clients not send non-Bind operations while a Bind is
in progress, and suggested that servers not process them if they in progress, and suggested that servers not process them if they
are received. This is needed to ensure proper sequencing of the are received. This is needed to ensure proper sequencing of the
Bind in relationship to other operations. Bind in relationship to other operations.
Sermersheim Internet-Draft - Expires April 2006 Page 59
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
C.1.14 Section 4.2.3 (Bind Response) C.1.14. Section 4.2.3 (Bind Response)
- 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.
- Prohibited the server from specifying serverSaslCreds when not - Prohibited the server from specifying serverSaslCreds when not
appropriate. appropriate.
C.1.15 Section 4.3 (Unbind Operation) C.1.15. Section 4.3 (Unbind Operation)
- Specified that both peers are to cease transmission and terminate - Specified that both peers are to cease transmission and terminate
the LDAP session for the Unbind operation. the LDAP session for the Unbind operation.
C.1.16 Section 4.4 (Unsolicited Notification) C.1.16. Section 4.4 (Unsolicited Notification)
- Added instructions for future specifications of Unsolicited - Added instructions for future specifications of Unsolicited
Notifications. Notifications.
C.1.17 Section 4.5.1 (Search Request) C.1.17. Section 4.5.1 (Search Request)
- SearchRequest attributes is now defined as an AttributeSelection - SearchRequest attributes is now defined as an AttributeSelection
type rather than AttributeDescriptionList, and an ABNF is type rather than AttributeDescriptionList, and an ABNF is
provided. provided.
- SearchRequest attributes may contain duplicate attribute - SearchRequest attributes may contain duplicate attribute
descriptions. This was previously prohibited. Now servers are descriptions. This was previously prohibited. Now servers are
instructed to ignore subsequent names when they are duplicated. instructed to ignore subsequent names when they are duplicated.
This was relaxed in order to allow different short names and also This was relaxed in order to allow different short names and also
OIDs to be requested for an attribute. OIDs to be requested for an attribute.
- The present search filter now evaluates to Undefined when the - The present search filter now evaluates to Undefined when the
skipping to change at line 3050 skipping to change at line 3147
- 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.
- Disambiguated the semantics of the derefAliases choices. There was - Disambiguated the semantics of the derefAliases choices. There was
question as to whether derefInSearching applied to the base object question as to whether derefInSearching applied to the base object
in a wholeSubtree Search. in a wholeSubtree Search.
- Added instructions for equalityMatch, substrings, greaterOrEqual, - Added instructions for equalityMatch, substrings, greaterOrEqual,
lessOrEqual, and approxMatch. lessOrEqual, and approxMatch.
C.1.18 Section 4.5.2 (Search Result) C.1.18. Section 4.5.2 (Search Result)
- Recommended that servers not use attribute short names when it - Recommended that servers not use attribute short names when it
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.
Sermersheim Internet-Draft - Expires April 2006 Page 60
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
C.1.19 Section 4.5.3 (Continuation References in the Search Result) C.1.19. Section 4.5.3 (Continuation References in the Search Result)
- Made changes similar to those made to Section 4.1.11. - Made changes similar to those made to Section 4.1.11.
C.1.20 Section 4.5.3.1 (Example) C.1.20. Section 4.5.3.1 (Example)
- 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.21 Section 4.6 (Modify Operation) C.1.21. Section 4.6 (Modify Operation)
- Replaced AttributeTypeAndValues with Attribute as they are - Replaced AttributeTypeAndValues with Attribute as they are
equivalent. equivalent.
- Specified the types of modification changes which might - Specified the types of modification changes which might
temporarily violate schema. Some readers were under the impression temporarily violate schema. Some readers were under the impression
that any temporary schema violation was allowed. that any temporary schema violation was allowed.
C.1.22 Section 4.7 (Add Operation) C.1.22. Section 4.7 (Add Operation)
- Aligned Add operation with X.511 in that the attributes of the RDN - Aligned Add operation with X.511 in that the attributes of the RDN
are used in conjunction with the listed attributes to create the are used in conjunction with the listed attributes to create the
entry. Previously, Add required that the distinguished values be entry. Previously, Add required that the distinguished values be
present in the listed attributes. present in the listed attributes.
- Removed requirement that the objectClass attribute MUST be - Removed requirement that the objectClass attribute MUST be
specified as some DSE types do not require this attribute. specified as some DSE types do not require this attribute.
Instead, generic wording was added, requiring the added entry to Instead, generic wording was added, requiring the added entry to
adhere to the data model. adhere to the data model.
- Removed recommendation regarding placement of objects. This is - Removed recommendation regarding placement of objects. This is
covered in the data model document. covered in the data model document.
C.1.23 Section 4.9 (Modify DN Operation) C.1.23. Section 4.9 (Modify DN Operation)
- 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 not - Specified what happens when the attributes of the newrdn are not
present on the entry. present on the entry.
C.1.24 Section 4.10 (Compare Operation) C.1.24. Section 4.10 (Compare Operation)
- Specified that compareFalse means that the Compare took place and - Specified that compareFalse means that the Compare took place and
the result is false. There was confusion which lead people to the result is false. There was confusion which lead people to
believe that an Undefined match resulted in compareFalse. believe that an Undefined match resulted in compareFalse.
- 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.
Sermersheim Internet-Draft - Expires April 2006 Page 61
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
C.1.25 Section 4.11 (Abandon Operation) C.1.25. Section 4.11 (Abandon Operation)
- 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.26 Section 4.12 (Extended Operation) C.1.26. Section 4.12 (Extended Operation)
- 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.
- 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.27 Section 5.2 (Transfer Protocols) C.1.27. Section 5.2 (Transfer Protocols)
- Moved referral-specific instructions into referral-related - Moved referral-specific instructions into referral-related
sections. sections.
C.1.28 Section 7 (Security Considerations) C.1.28. Section 7 (Security Considerations)
- Reworded notes regarding SASL not protecting certain aspects of - Reworded notes regarding SASL not protecting certain aspects of
the LDAP Bind messages. the LDAP Bind messages.
- 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 possibility of changes to security - Added a note regarding the possibility of changes to security
factors (authentication, authorization, data confidentiality). factors (authentication, authorization, data confidentiality).
- 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.
- Noted that servers should protect information equally, whether in - Noted that servers should protect information equally, whether in
an error condition or not, and mentioned specifically; matchedDN, an error condition or not, and mentioned specifically; matchedDN,
diagnosticMessage, and resultCodes. diagnosticMessage, and resultCodes.
- Added a note regarding malformed and long encodings. - Added a note regarding malformed and long encodings.
C.1.29 Appendix A (Complete ASN.1 Definition) C.1.29. Appendix A (Complete ASN.1 Definition)
- Added "EXTENSIBILITY IMPLIED" to ASN.1 definition. - Added "EXTENSIBILITY IMPLIED" to ASN.1 definition.
- Removed AttributeType. It is not used. - Removed AttributeType. It is not used.
C.2 Changes made to RFC 2830: C.2. Changes 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.
Sermersheim Internet-Draft - Expires April 2006 Page 62
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
C.2.1 Section 2.3 (Response other than "success") C.2.1. Section 2.3 (Response other than "success")
- Removed wording indicating that referrals can be returned from - Removed wording indicating that referrals can be returned from
StartTLS. StartTLS.
- 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.
- Removed requirement that the ExtendedResponse.responseName MUST be
present. There are circumstances where this is impossible, and
requiring this is at odds with language in Section 4.12.
C.2.1 Section 4 (Closing a TLS Connection) C.2.1. Section 4 (Closing a TLS Connection)
- Reworded most of this section to align with definitions of the - Reworded most of this section to align with definitions of the
LDAP protocol layers. LDAP protocol layers.
- Removed instructions on abrupt closure as this is covered in other - Removed instructions on abrupt closure as this is covered in other
areas of the document (specifically, Section 5.3) areas of the document (specifically, Section 5.3)
C.3 Changes made to RFC 3771: C.3. Changes made to RFC 3771:
- Rewrote to fit into this document. In general, semantics were - Rewrote to fit into this document. In general, semantics were
preserved. Supporting and background language seen as redundant preserved. Supporting and background language seen as redundant
due to its presence in this document was omitted. due to its presence in this document was omitted.
- Specified that Intermediate responses to a request may be of - Specified that Intermediate responses to a request may be of
different types, and one of the response types may be specified to different types, and one of the response types may be specified to
have no response value. have no response value.
Sermersheim Internet-Draft - Expires April 2006 Page 63
Lightweight Directory Access Protocol Version 3 Lightweight Directory Access Protocol Version 3
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
<http://www.ietf.org/ipr>. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf- this standard. Please address the information to the IETF at ietf-
ipr@ietf.org. ipr@ietf.org.
Disclaimer of Validity Disclaimer of Validity
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2005). This document is subject Copyright (C) The Internet Society (2005).
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
Acknowledgement Acknowledgement
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
Sermersheim Internet-Draft - Expires April 2006 Page 64
 End of changes. 150 change blocks. 
109 lines changed or deleted 215 lines changed or added

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