draft-ietf-ldapbis-url-02.txt   draft-ietf-ldapbis-url-03.txt 
Network Working Group Mark Smith, Editor Network Working Group Mark Smith, Editor
Request for Comments: DRAFT Netscape Communications Corp. Request for Comments: DRAFT Netscape Communications Corp.
Obsoletes: RFC 2255 Tim Howes Obsoletes: RFC 2255 Tim Howes
Expires: 9 February 2003 Loudcloud, Inc. Expires: 28 August 2003 Opsware, Inc.
9 August 2002 28 February 2003
LDAP: Uniform Resource Locator LDAP: Uniform Resource Locator
<draft-ietf-ldapbis-url-02.txt> <draft-ietf-ldapbis-url-03.txt>
1. Status of this Memo 1. Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is subject to all provisions
all provisions of Section 10 of RFC2026. of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. 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/1id-abstracts.html
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
Discussion of this document should take place on the LDAP (v3) Discussion of this document should take place on the LDAP (v3)
Revision (ldapbis) Working Group mailing list <ietf- Revision (ldapbis) Working Group mailing list <ietf-
ldapbis@openldap.org>. ldapbis@openldap.org>.
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
2. Abstract 2. Abstract
This document describes a format for an LDAP Uniform Resource Locator This document describes a format for an LDAP Uniform Resource Locator
(URL). An LDAP URL describes an LDAP search operation that is used (URL). An LDAP URL describes an LDAP search operation that is used
to retrieve information from an LDAP directory, or, in the context of to retrieve information from an LDAP directory, or, in the context of
an LDAPv3 referral or reference, an LDAP URL describes a service an LDAPv3 referral or reference, an LDAP URL describes a service
where an LDAP operation may be progressed. where an LDAP operation may be progressed.
3. Table of Contents 3. Table of Contents
1. Status of this Memo............................................1 1. Status of this Memo............................................1
2. Abstract.......................................................1 2. Abstract.......................................................1
3. Table of Contents..............................................2 3. Table of Contents..............................................2
4. Introduction...................................................2 4. Introduction...................................................2
5. URL Definition.................................................2 5. URL Definition.................................................2
6. Defaults for Fields of the LDAP URL............................4 6. Defaults for Fields of the LDAP URL............................5
7. Examples.......................................................5 7. Examples.......................................................5
8. Security Considerations........................................7 8. Security Considerations........................................7
9. Acknowledgements...............................................8 9. Acknowledgements...............................................8
10. Normative References...........................................8 10. Normative References...........................................9
11. Authors' Address...............................................9 11. Informative References.........................................9
12. Full Copyright Statement.......................................9 12. Authors' Address...............................................9
13. Appendix A: Changes Since RFC 2255.............................10 13. Full Copyright Statement.......................................10
13.1. Technical Changes...........................................10 14. Appendix A: Changes Since RFC 2255.............................10
13.2. Editorial Changes...........................................10 14.1. Technical Changes...........................................10
14. Appendix B: Changes Since Previous Document Revision...........11 14.2. Editorial Changes...........................................11
14.1. Technical Changes...........................................11 15. Appendix B: Changes Since Previous Document Revision...........13
14.2. Editorial Changes...........................................12 15.1. Technical Changes...........................................13
15.2. Editorial Changes...........................................13
4. Introduction 4. Introduction
LDAP is the Lightweight Directory Access Protocol, defined in LDAP is the Lightweight Directory Access Protocol, defined in
[Protocol]. This document specifies the LDAP URL format for version [Protocol]. This document specifies the LDAP URL format for version
3 of LDAP and clarifies how LDAP URLs are resolved. This document 3 of LDAP and clarifies how LDAP URLs are resolved. This document
also defines an extension mechanism for LDAP URLs, so that future also defines an extension mechanism for LDAP URLs, so that future
documents can extend their functionality, for example, to provide documents can extend their functionality, for example, to provide
access to new LDAPv3 extensions as they are defined. Note: not all access to new LDAPv3 extensions as they are defined. Note: not all
of the parameters of the LDAP search operation described in of the parameters of the LDAP search operation described in
skipping to change at page 3, line 5 skipping to change at page 3, line 5
The key words "MUST", "MAY", and "SHOULD" used in this document are The key words "MUST", "MAY", and "SHOULD" used in this document are
to be interpreted as described in [RFC2119]. to be interpreted as described in [RFC2119].
5. URL Definition 5. URL Definition
An LDAP URL begins with the protocol prefix "ldap" and is defined by An LDAP URL begins with the protocol prefix "ldap" and is defined by
the following grammar, following the ABNF notation defined in the following grammar, following the ABNF notation defined in
[RFC2234]. [RFC2234].
ldapurl = scheme "://" [hostport] ["/" dn ldapurl = scheme COLON SLASH SLASH [hostport] [SLASH dn
["?" [attributes] ["?" [scope] [QUESTION [attributes] [QUESTION [scope]
["?" [filter] ["?" extensions]]]]] [QUESTION [filter] [QUESTION extensions]]]]]
scheme = "ldap" scheme = "ldap"
hostport = <hostport from Section 3.2.2 of [RFC2396]> hostport = <hostport from Section 3.2.2 of [RFC2396]>
; as updated by [RFC2732] to allow IPv6 literal addresses
dn = <distinguishedName from Section 3 of [LDAPDN]> dn = <distinguishedName from Section 3 of [LDAPDN]>
attributes = attrdesc *("," attrdesc) attributes = attrdesc *(COMMA attrdesc)
attrdesc = <AttributeDescription from Section 4.1.4 of [Protocol]> / "*" attrdesc = <AttributeDescription from Section 4.1.4 of [Protocol]>
/ ASTERIX
scope = "base" / "one" / "sub" scope = "base" / "one" / "sub"
filter = <filter from Section 4 of [Filters]> filter = <filter from Section 4 of [Filters]>
extensions = extension *("," extension) extensions = extension *(COMMA extension)
extension = ["!"] extype ["=" exvalue] extension = [EXCLAMATION] extype [EQUALS exvalue]
extype = oid / oiddescr extype = oid / oiddescr
exvalue = <LDAPString from section 4.1.2 of [Protocol]> exvalue = <LDAPString from section 4.1.2 of [Protocol]>
oid = <LDAPOID from section 4.1.2 of [Protocol]> oid = <LDAPOID from section 4.1.2 of [Protocol]>
oiddescr = <name from section 3.3 of [LDAPIANA]> oiddescr = <name from section 3.3 of [LDAPIANA]>
EXCLAMATION = %x21 ; exclamation mark ("!")
ASTERIX = %x2A ; asterix ("*")
COLON = %x3A ; colon (":")
QUESTION = %x3F ; question mark ("?")
SLASH = %x5C; forward slash ("/")
The "ldap" prefix indicates an entry or entries residing in the LDAP The "ldap" prefix indicates an entry or entries residing in the LDAP
server running on the given hostname at the given portnumber. server running on the given hostname at the given portnumber. Note
that the hostport may contain literal IPv6 addresses as specified in
[RFC2732].
The dn is an LDAP Distinguished Name using the string format The dn is an LDAP Distinguished Name using the string format
described in [LDAPDN]. It identifies the base object of the LDAP described in [LDAPDN]. It identifies the base object of the LDAP
search or the target of a non-search operation. search or the target of a non-search operation.
The attributes construct is used to indicate which attributes should The attributes construct is used to indicate which attributes should
be returned from the entry or entries. Individual attrdesc names are be returned from the entry or entries. Individual attrdesc names are
as defined for AttributeDescription in [Protocol]. as defined for AttributeDescription in [Protocol].
The scope construct is used to specify the scope of the search to The scope construct is used to specify the scope of the search to
skipping to change at page 4, line 25 skipping to change at page 4, line 36
extension cannot be processed successfully by the client, the client extension cannot be processed successfully by the client, the client
SHOULD ignore the extension. SHOULD ignore the extension.
The extension type (extype) MAY be specified using the oid form The extension type (extype) MAY be specified using the oid form
(e.g., 1.2.3.4) or the oiddesc form (e.g., myLDAPURLExtension). Use (e.g., 1.2.3.4) or the oiddesc form (e.g., myLDAPURLExtension). Use
of the oiddesc form SHOULD be restricted to registered object of the oiddesc form SHOULD be restricted to registered object
identifier descriptive names. See [LDAPIANA] for registration identifier descriptive names. See [LDAPIANA] for registration
details and usage guidelines for descriptive names. details and usage guidelines for descriptive names.
No LDAP URL extensions are defined in this document. Other documents No LDAP URL extensions are defined in this document. Other documents
or a future version of this document MAY define other extensions. or a future version of this document MAY define one or more
extensions.
Note that characters that are not safe (e.g., spaces) (as defined in A generated LDAP URL MUST consist only of the restricted set of
section 2.1 of [RFC2396]), and the single Reserved character '?' characters included in the uric production that is defined in section
occurring inside a dn, filter, or other element of an LDAP URL MUST 2 of [RFC2396]. Implementations SHOULD accept other valid UTF-8
be escaped using the % method described in section 2.4 of [RFC2396]. strings as input. An octet MUST be escaped using the % method
If a comma character ',' occurs inside an extension value, the described in section 2.4 of [RFC2396] in any of these situations:
character MUST also be escaped using the % method.
The octet is not in the reserved set defined in section 2.2 of
[RFC2396] or in the unreserved set defined in section 2.3 of
[RFC2396].
It is the single Reserved character '?' and occurs inside a dn,
filter, or other element of an LDAP URL.
It is a comma character ',' that occurs inside an extension value.
6. Defaults for Fields of the LDAP URL 6. Defaults for Fields of the LDAP URL
Some fields of the LDAP URL are optional, as described above. In the Some fields of the LDAP URL are optional, as described above. In the
absence of any other specification, the following general defaults absence of any other specification, the following general defaults
SHOULD be used when a field is absent. Note: other documents MAY SHOULD be used when a field is absent. Note: other documents MAY
specify different defaulting rules; for example, section 4.1.11 of specify different defaulting rules; for example, section 4.1.11 of
[Protocol] specifies a different rule for determining the correct DN [Protocol] specifies a different rule for determining the correct DN
to use when it is absent in an LDAP URL that is returned as a to use when it is absent in an LDAP URL that is returned as a
referral. referral.
skipping to change at page 6, line 23 skipping to change at page 6, line 40
The objectClass attribute is requested to be returned along with the The objectClass attribute is requested to be returned along with the
entries, and the default filter of "(objectclass=*)" is used. entries, and the default filter of "(objectclass=*)" is used.
The next example is an LDAP URL to retrieve the mail attribute for The next example is an LDAP URL to retrieve the mail attribute for
the LDAP entry named "o=Question?,c=US" is given below, illustrating the LDAP entry named "o=Question?,c=US" is given below, illustrating
the use of the escaping mechanism on the reserved character '?'. the use of the escaping mechanism on the reserved character '?'.
ldap://ldap2.example.com/o=Question%3f,c=US?mail ldap://ldap2.example.com/o=Question%3f,c=US?mail
The next example illustrates the interaction between LDAP and URL The next example illustrates the interaction between the LDAP string
quoting mechanisms. representation of filters quoting mechanism and URL quoting
mechanisms.
ldap://ldap3.example.com/o=Babsco,c=US???(int=%5c00%5c00%5c00%5c04) ldap://ldap3.example.com/o=Babsco,c=US???(int=%5c00%5c00%5c00%5c04)
The filter in this example uses the LDAP escaping mechanism of \ to The filter in this example uses the LDAP escaping mechanism of \ to
encode three zero or null bytes in the value. In LDAP, the filter encode three zero or null bytes in the value. In LDAP, the filter
would be written as (int=\00\00\00\04). Because the \ character must would be written as (int=\00\00\00\04). Because the \ character must
be escaped in a URL, the \'s are escaped as %5c in the URL encoding. be escaped in a URL, the \'s are escaped as %5c in the URL encoding.
The next example illustrates the interaction between the LDAP string
representation of DNs quoting mechanism and URL quoting mechanisms.
ldap://ldap.example.com/o=An%20Example%5c2c%20Inc.,c=US
The DN encoded in the above URL is:
o=An Example\2c Inc.,c=US
That is, the left-most RDN value is:
An Example, Inc.
The following three URLs that are equivalent, assuming that the The following three URLs that are equivalent, assuming that the
defaulting rules specified in section 4 of this document are used: defaulting rules specified in section 4 of this document are used:
ldap://ldap.example.net ldap://ldap.example.net
ldap://ldap.example.net/ ldap://ldap.example.net/
ldap://ldap.example.net/? ldap://ldap.example.net/?
These three URLs all point to the root DSE on the ldap.example.net These three URLs all point to the root DSE on the ldap.example.net
server. server.
skipping to change at page 8, line 20 skipping to change at page 8, line 50
the University of Michigan and the National Science Foundation is the University of Michigan and the National Science Foundation is
gratefully acknowledged. gratefully acknowledged.
This document is an update to RFC 2255 by Tim Howes and Mark Smith. This document is an update to RFC 2255 by Tim Howes and Mark Smith.
Changes included in this revised specification are based upon Changes included in this revised specification are based upon
discussions among the authors, discussions within the LDAP (v3) discussions among the authors, discussions within the LDAP (v3)
Revision Working Group (ldapbis), and discussions within other IETF Revision Working Group (ldapbis), and discussions within other IETF
Working Groups. The contributions of individuals in these working Working Groups. The contributions of individuals in these working
groups is gratefully acknowledged. Several people in particular have groups is gratefully acknowledged. Several people in particular have
made valuable comments on this document; RL "Bob" Morgan, Mark Wahl, made valuable comments on this document; RL "Bob" Morgan, Mark Wahl,
Kurt Zeilenga, and Jim Sermersheim deserve special thanks for their Kurt Zeilenga, Jim Sermersheim, and Hallvard Furuseth deserve special
contributions. thanks for their contributions.
10. Normative References 10. Normative References
[LDAPDN] Zeilenga, K. (editor), "LDAP: String Representation of [LDAPDN] Zeilenga, K. (editor), "LDAP: String Representation of
Distinguished Names", draft-ietf-ldapbis-dn-xx.txt, a work in Distinguished Names", draft-ietf-ldapbis-dn-xx.txt, a work in
progress. progress.
[LDAPIANA] Zeilenga, K., "IANA Considerations for LDAP", draft-ietf- [LDAPIANA] Zeilenga, K., "IANA Considerations for LDAP", draft-ietf-
ldapbis-iana-xx.txt, a work in progress. ldapbis-iana-xx.txt, a work in progress.
skipping to change at page 8, line 49 skipping to change at page 9, line 31
[RFC2234] Crocker, D., Overell, P., "Augmented BNF for Syntax [RFC2234] Crocker, D., Overell, P., "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997. Specifications: ABNF", RFC 2234, November 1997.
[RFC2279] Yergeau, F., "UTF-8, a transformation format of ISO 10646", [RFC2279] Yergeau, F., "UTF-8, a transformation format of ISO 10646",
RFC 2279, January 1998. RFC 2279, January 1998.
[RFC2396] Berners-Lee, T., Fielding, R., and Masinter, L., "Uniform [RFC2396] Berners-Lee, T., Fielding, R., and Masinter, L., "Uniform
Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998. Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998.
[RFC2732] Hinden, R., Carpenter, B., Masinter, L., "Format for
Literal IPv6 Addresses in URL's", RFC 2732, December 1999.
[AuthMeth] Harrison, R. (editor), "LDAP: Authentication Methods", [AuthMeth] Harrison, R. (editor), "LDAP: Authentication Methods",
draft-ietf-ldapbis-authmeth-xx.txt, a work in progress. a work in draft-ietf-ldapbis-authmeth-xx.txt, a work in progress. a work in
progress. progress.
[Roadmap] K. Zeilenga (editor), "LDAP: Technical Specification Road [Roadmap] K. Zeilenga (editor), "LDAP: Technical Specification Road
Map", draft-ietf-ldapbis-roadmap-xx.txt, a work in progress. Map", draft-ietf-ldapbis-roadmap-xx.txt, a work in progress.
11. Authors' Address 11. Informative References
None.
12. Authors' Address
Mark Smith, Editor Mark Smith, Editor
Netscape Communications Corp. Netscape Communications Corp.
360 W. Caribbean Drive 360 W. Caribbean Drive
Sunnyvale, CA 94089 Sunnyvale, CA 94089
USA USA
+1 650 937-3477 +1 650 937-3477
mcs@netscape.com mcs@netscape.com
Tim Howes Tim Howes
Loudcloud, Inc. Opsware, Inc.
599 N. Mathilda Ave. 599 N. Mathilda Ave.
Sunnyvale, CA 94086 Sunnyvale, CA 94085
USA USA
+1 408 744-7509 +1 408 744-7509
howes@loudcloud.com howes@opsware.com
12. Full Copyright Statement 13. Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
skipping to change at page 10, line 5 skipping to change at page 10, line 42
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
13. Appendix A: Changes Since RFC 2255 14. Appendix A: Changes Since RFC 2255
13.1. Technical Changes 14.1. Technical Changes
"URL Definition" section: added missing "*" as an alternative for the The following technical changes were made to the contents of the "URL
attrdesc part of the URL. It is believed that existing Definition" section:
implementations of RFC 2255 already support this. Added angle
brackets around free-form prose in the "dn", "hostport", "attrdesc", Revised all of the ABNF to use common productions from [Models].
"filter", and "exvalue" rules. Changed the ABNF for ldapurl to group
the dn component with the preceding slash. Changed the extype rule Added note and references to [RFC2732] to allow literal IPv6
to be an LDAPOID from [Protocol] or an OID description from addresses inside the hostport portion of the URL.
[LDAPIANA]. Changed the text about extension types so it references
[LDAPIANA]. Reordered rules to more closely follow the order the Added missing ASTERIX as an alternative for the attrdesc part of the
elements appear in the URL. URL. It is believed that existing implementations of RFC 2255
already support this.
Added angle brackets around free-form prose in the "dn", "hostport",
"attrdesc", "filter", and "exvalue" rules.
Changed the ABNF for ldapurl to group the dn component with the
preceding slash.
Changed the extype rule to be an LDAPOID from [Protocol] or an OID
description from [LDAPIANA].
Changed the text about extension types so it references [LDAPIANA].
Reordered rules to more closely follow the order the elements appear
in the URL.
"Bindname Extension": removed due to lack of known implementations. "Bindname Extension": removed due to lack of known implementations.
13.2. Editorial Changes 14.2. Editorial Changes
Changed document title to include "LDAP:" prefix.
IESG Note: removed note about lack of satisfactory mandatory
authentication mechanisms.
"Status of this Memo" section: updated boilerplate to match current
I-D guidelines.
"Abstract" section: separated from introductory material. "Abstract" section: separated from introductory material.
"Table of Contents" section: added. "Table of Contents" section: added.
"Introduction" section: new section; separated from the Abstract. "Introduction" section: new section; separated from the Abstract.
Changed the text indicate that RFC 2255 is replaced by this document Changed the text indicate that RFC 2255 is replaced by this document
(instead of RFC 1959). Added text to indicate that LDAP URLs are (instead of RFC 1959). Added text to indicate that LDAP URLs are
used for references and referrals. Fixed typo (replaced the nonsense used for references and referrals. Fixed typo (replaced the nonsense
phrase "to perform to retrieve" with "used to retrieve"). Added a phrase "to perform to retrieve" with "used to retrieve"). Added a
note to let the reader know that not all of the parameters of the note to let the reader know that not all of the parameters of the
LDAP search operation described in [Protocol] can be expressed using LDAP search operation described in [Protocol] can be expressed using
this format. this format.
IESG Note: removed note about lack of satisfactory mandatory
authentication mechanisms.
"URL Definition" section: removed second copy of ldapurl grammar and "URL Definition" section: removed second copy of ldapurl grammar and
following two paragraphs (editorial error in RFC 2255). Fixed line following two paragraphs (editorial error in RFC 2255). Fixed line
break within '!' sequence. Reworded last paragraph to clarify which break within '!' sequence. Reworded last paragraph to clarify which
characters must be URL escaped. Added text to indicate that LDAP characters must be URL escaped. Added text to indicate that LDAP
URLs are used for references and referrals. Added text that refers URLs are used for references and referrals. Added text that refers
to the ABNF from RFC 2234. to the ABNF from RFC 2234.
"Defaults for Fields of the LDAP URL" section: added; formed by "Defaults for Fields of the LDAP URL" section: added; formed by
moving text about defaults out of the "URL Definition" section. moving text about defaults out of the "URL Definition" section.
skipping to change at page 11, line 13 skipping to change at page 12, line 23
only if the open connection is compatible with the URL. Added text only if the open connection is compatible with the URL. Added text
to indicate that use of security services is encouraged and that they to indicate that use of security services is encouraged and that they
SHOULD be used when updates are involved. Removed "dn" from SHOULD be used when updates are involved. Removed "dn" from
discussion of authentication methods. Added note that the client MAY discussion of authentication methods. Added note that the client MAY
interrogate the server to determine the most appropriate method. interrogate the server to determine the most appropriate method.
"Examples" section: Modified examples to use example.com and "Examples" section: Modified examples to use example.com and
example.net hostnames. Added missing '?' to the LDAP URL example example.net hostnames. Added missing '?' to the LDAP URL example
whose filter contains three null bytes. Removed space after one whose filter contains three null bytes. Removed space after one
comma within a DN. Revised the bindname example to use e-bindname. comma within a DN. Revised the bindname example to use e-bindname.
Added some examples to show URL equivalence with respect to the dn Added an example that demonstrates the interaction between DN
portion of the URL. escaping and URL escaping. Added some examples to show URL
equivalence with respect to the dn portion of the URL.
"Security Considerations" section: Added a note about connection "Security Considerations" section: Added a note about connection
reuse. Added a note about using strong authentication methods for reuse. Added a note about using strong authentication methods for
updates. Added a reference to RFC 2829. Added note that simply updates. Added a reference to RFC 2829. Added note that simply
opening a connection may violate some users' privacy requirements. opening a connection may violate some users' privacy requirements.
"Acknowledgements" section: added statement about this being an "Acknowledgements" section: added statement about this being an
update to RFC 2255. Added Kurt Zeilenga and Jim Sermersheim. update to RFC 2255. Added Kurt Zeilenga, Jim Sermersheim, and
Hallvard Furuseth.
"Normative References" section: renamed from "References" per new RFC "Normative References" section: renamed from "References" per new RFC
guidelines. Changed from [1] style to [Protocol] style throughout the guidelines. Changed from [1] style to [Protocol] style throughout the
document. Added references to RFCs 2234 and 2829. Updated RFC 1738 document. Added references to RFCs 2234 and 2829. Updated RFC 1738
references to the appropriate sections within RFC 2396. Updated the references to the appropriate sections within RFC 2396. Updated the
references to refer to LDAPBis WG documents. Removed the reference to references to refer to LDAPBis WG documents. Removed the reference to
the LDAP Attribute Syntaxes document and added references to the LDAP the LDAP Attribute Syntaxes document and added references to the LDAP
IANA and Roadmap documents. IANA and Roadmap documents.
"Informative References" section: added for clarity.
Header and "Authors' Address" sections: added "editor" next to Mark Header and "Authors' Address" sections: added "editor" next to Mark
Smith's name. Updated affiliation and contact information. Smith's name. Updated affiliation and contact information.
Copyright: updated the year. Copyright: updated the year.
14. Appendix B: Changes Since Previous Document Revision 15. Appendix B: Changes Since Previous Document Revision
This appendix lists all changes relative to the last published This appendix lists all changes relative to the last published
revision, draft-ietf-ldapbis-url-01.txt. Note that these changes are revision, draft-ietf-ldapbis-url-02.txt. Note that when appropriate
also included in Appendix A, but are included here for those who have these changes are also included in Appendix A, but are also included
already reviewed draft-ietf-ldapbis-url-01.txt. here for the benefit of the people who have already reviewed draft-
ietf-ldapbis-url-02.txt. This section will be removed before this
document is published as an RFC.
14.1. Technical Changes 15.1. Technical Changes
None. "URL Definition" section: revised all of the ABNF to use common
productions from [Models] and added note and references to [RFC2732]
to allow literal IPv6 addresses inside the hostport portion of the
URL.
14.2. Editorial Changes 15.2. Editorial Changes
"Abstract" section: separated from introductory material. "Status of this Memo" section: updated boilerplate to match current
I-D guidelines.
"Table of Contents" section: moved to correct location (after "URL Definition" section: replaced misleading phrase "MAY define
Abstract). other extensions" with "MAY define one or more extensions" (this
document no longer defines any extensions). Rewrote the last
paragraph of this section to more clearly describe the escaping rules
and to reference [RFC2396] accurately.
"Introduction" section: new section; separated from the Abstract. "Examples" section: added an example that demonstrates the
interaction between DN escaping and URL escaping and clarified the
text that introduces the LDAP filter escaping interaction example.
Copyright: updated the year to 2002. "Acknowledgements" section: added Hallvard Furuseth.
"URL Definition" section: updated section references to match current "Normative References" section: added a reference to [RFC2732].
LDAPBis drafts.
"Normative References" section: renamed from "References" per new RFC "Informative References" section: added for clarity.
guidelines. Replaced [RFC2251bis] style references with textual ones
like [Protocol] for LDAPBis documents and updated reference format to
match that used in other LDAPBis drafts. Removed references to
LDAPBis Attribute Syntaxes document and added a reference to the
Roadmap document. Added "BCP 14" to the RFC 2119 reference.
"Authors' Address" section: updated Mark Smith's postal address. Copyright: updated the year to 2003.
This Internet Draft expires on 9 February 2003. "Authors' Address" section: updated Tim's contact information.
Appendix A: added an older editorial change that was accidently
overlooked (Changed document title to include "LDAP:" prefix).
This Internet Draft expires on 28 August 2003.
 End of changes. 

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