draft-ietf-ldapbis-url-03.txt   draft-ietf-ldapbis-url-04.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: 28 August 2003 Opsware, Inc. Expires: 25 April 2004 Opsware, Inc.
28 February 2003 25 October 2003
LDAP: Uniform Resource Locator LDAP: Uniform Resource Locator
<draft-ietf-ldapbis-url-03.txt> <draft-ietf-ldapbis-url-04.txt>
1. Status of this Memo 1. Status of this Memo
This document is an Internet-Draft and is subject to all provisions This document is an Internet-Draft and is subject to 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.
skipping to change at page 2, line 12 skipping to change at page 2, line 12
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
5.1. Escaping Using the Method.................................4
6. Defaults for Fields of the LDAP URL............................5 6. Defaults for Fields of the LDAP URL............................5
7. Examples.......................................................5 7. Examples.......................................................6
8. Security Considerations........................................7 8. Security Considerations........................................8
9. Acknowledgements...............................................8 9. Normative References...........................................8
10. Normative References...........................................9 10. Informative References.........................................9
11. Informative References.........................................9 11. Intellectual Property Rights...................................9
12. Authors' Address...............................................9 12. Acknowledgements...............................................10
13. Full Copyright Statement.......................................10 13. Authors' Address...............................................10
14. Appendix A: Changes Since RFC 2255.............................10 14. Full Copyright Statement.......................................11
14.1. Technical Changes...........................................10 15. Appendix A: Changes Since RFC 2255.............................11
14.2. Editorial Changes...........................................11 15.1. Technical Changes...........................................11
15. Appendix B: Changes Since Previous Document Revision...........13 15.2. Editorial Changes...........................................12
15.1. Technical Changes...........................................13 16. Appendix B: Changes Since Previous Document Revision...........13
15.2. Editorial Changes...........................................13 16.1. Technical Changes...........................................14
16.2. Editorial Changes...........................................14
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 12 skipping to change at page 3, line 14
the following grammar, following the ABNF notation defined in the following grammar, following the ABNF notation defined in
[RFC2234]. [RFC2234].
ldapurl = scheme COLON SLASH SLASH [hostport] [SLASH dn ldapurl = scheme COLON SLASH SLASH [hostport] [SLASH dn
[QUESTION [attributes] [QUESTION [scope] [QUESTION [attributes] [QUESTION [scope]
[QUESTION [filter] [QUESTION 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 ; as updated by [RFC2732] to allow IPv6 literal addresses
dn = <distinguishedName from Section 3 of [LDAPDN]> dn = <distinguishedName from Section 3 of [LDAPDN]>
; see the "Escaping Using the % Method" section below.
attributes = attrdesc *(COMMA attrdesc) attributes = attrdesc *(COMMA attrdesc)
attrdesc = <AttributeDescription from Section 4.1.4 of [Protocol]> attrdesc = <AttributeDescription from Section 4.1.4 of [Protocol]>
/ ASTERIX / ASTERISK
; see the "Escaping Using the % Method" section below.
scope = "base" / "one" / "sub" scope = "base" / "one" / "sub"
filter = <filter from Section 4 of [Filters]> filter = <filter from Section 4 of [Filters]>
; see the "Escaping Using the % Method" section below.
extensions = extension *(COMMA extension) extensions = extension *(COMMA extension)
extension = [EXCLAMATION] extype [EQUALS 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]>
; see the "Escaping Using the % Method" section below.
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 [RFC3383]>
EXCLAMATION = %x21 ; exclamation mark ("!") EXCLAMATION = %x21 ; exclamation mark ("!")
ASTERIX = %x2A ; asterix ("*") ASTERISK = %x2A ; asterisk ("*")
COLON = %x3A ; colon (":") COLON = %x3A ; colon (":")
QUESTION = %x3F ; question mark ("?") QUESTION = %x3F ; question mark ("?")
SLASH = %x5C; forward slash ("/") 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. Note server running on the given hostname at the given portnumber. Note
that the hostport may contain literal IPv6 addresses as specified in that the hostport may contain literal IPv6 addresses as specified in
[RFC2732]. [RFC2732].
The dn is an LDAP Distinguished Name using the string format The dn is an LDAP Distinguished Name using the string format
skipping to change at page 4, line 32 skipping to change at page 4, line 38
extension is non-critical, the client MUST ignore the extension. extension is non-critical, the client MUST ignore the extension.
If a critical extension cannot be processed successfully by the If a critical extension cannot be processed successfully by the
client, the client MUST NOT process the URL. If a non-critical client, the client MUST NOT process the URL. If a non-critical
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 [RFC3383] for registration details
details and usage guidelines for descriptive names. 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 one or more or a future version of this document MAY define one or more
extensions. extensions.
5.1. Escaping Using the % Method
A generated LDAP URL MUST consist only of the restricted set of A generated LDAP URL MUST consist only of the restricted set of
characters included in the uric production that is defined in section characters included in the uric production that is defined in section
2 of [RFC2396]. Implementations SHOULD accept other valid UTF-8 2 of [RFC2396]. Implementations SHOULD accept other valid UTF-8
strings as input. An octet MUST be escaped using the % method strings [UTF-8] as input. An octet MUST be escaped using the %
described in section 2.4 of [RFC2396] in any of these situations: method described in section 2.4 of [RFC2396] in any of these
situations:
The octet is not in the reserved set defined in section 2.2 of 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] or in the unreserved set defined in section 2.3 of
[RFC2396]. [RFC2396].
It is the single Reserved character '?' and occurs inside a dn, It is the single Reserved character '?' and occurs inside a dn,
filter, or other element of an LDAP URL. filter, or other element of an LDAP URL.
It is a comma character ',' that occurs inside an extension value. It is a comma character ',' that occurs inside an extension value.
skipping to change at page 6, line 44 skipping to change at page 7, line 11
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 the LDAP string The next example illustrates the interaction between the LDAP string
representation of filters quoting mechanism and URL quoting representation of filters quoting mechanism and URL quoting
mechanisms. mechanisms.
ldap://ldap3.example.com/o=Babsco,c=US???(int=%5c00%5c00%5c00%5c04) ldap://ldap3.example.com/o=Babsco,c=US???(four-octet=%5c00%5c00%5c00%5c04)
IP The filter in this example uses the LDAP escaping mechanism of \
The filter in this example uses the LDAP escaping mechanism of \ to 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 (four-octet=\00\00\00\04). Because the \
would be written as (int=\00\00\00\04). Because the \ character must character must be escaped in a URL, the \'s are escaped as %5c in the
be escaped in a URL, the \'s are escaped as %5c in the URL encoding. URL encoding.
The next example illustrates the interaction between the LDAP string The next example illustrates the interaction between the LDAP string
representation of DNs quoting mechanism and URL quoting mechanisms. representation of DNs quoting mechanism and URL quoting mechanisms.
ldap://ldap.example.com/o=An%20Example%5c2c%20Inc.,c=US ldap://ldap.example.com/o=An%20Example%5c2c%20Inc.,c=US
The DN encoded in the above URL is: The DN encoded in the above URL is:
o=An Example\2c Inc.,c=US o=An Example\2c Inc.,c=US
skipping to change at page 8, line 35 skipping to change at page 8, line 50
authentication methods SHOULD be used. Please refer to the Security authentication methods SHOULD be used. Please refer to the Security
Considerations section of [AuthMeth] for more information. Considerations section of [AuthMeth] for more information.
The LDAP URL format allows the specification of an arbitrary LDAP The LDAP URL format allows the specification of an arbitrary LDAP
search operation to be performed when evaluating the LDAP URL. search operation to be performed when evaluating the LDAP URL.
Following an LDAP URL may cause unexpected results, for example, the Following an LDAP URL may cause unexpected results, for example, the
retrieval of large amounts of data, the initiation of a long-lived retrieval of large amounts of data, the initiation of a long-lived
search, etc. The security implications of resolving an LDAP URL are search, etc. The security implications of resolving an LDAP URL are
the same as those of resolving an LDAP search query. the same as those of resolving an LDAP search query.
9. Acknowledgements 9. Normative References
The LDAP URL format was originally defined at the University of
Michigan. This material is based upon work supported by the National
Science Foundation under Grant No. NCR-9416667. The support of both
the University of Michigan and the National Science Foundation is
gratefully acknowledged.
This document is an update to RFC 2255 by Tim Howes and Mark Smith.
Changes included in this revised specification are based upon
discussions among the authors, discussions within the LDAP (v3)
Revision Working Group (ldapbis), and discussions within other IETF
Working Groups. The contributions of individuals in these working
groups is gratefully acknowledged. Several people in particular have
made valuable comments on this document; RL "Bob" Morgan, Mark Wahl,
Kurt Zeilenga, Jim Sermersheim, and Hallvard Furuseth deserve special
thanks for their contributions.
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-
ldapbis-iana-xx.txt, a work in progress.
[Filters] Smith, M. and Howes, T., "LDAP: String Representation of [Filters] Smith, M. and Howes, T., "LDAP: String Representation of
Search Filters", draft-ietf-ldapbis-filter-xx.txt, a work in Search Filters", draft-ietf-ldapbis-filter-xx.txt, a work in
progress. [RFC2119] Bradner, S., "Key Words for use in RFCs to progress.
Indicate Requirement Levels," RFC 2119, BCP 14, March 1997.
[RFC2119] Bradner, S., "Key Words for use in RFCs to Indicate
Requirement Levels," RFC 2119, BCP 14, March 1997.
[Protocol] Sermersheim, J. (editor), "LDAP: The Protocol", draft- [Protocol] Sermersheim, J. (editor), "LDAP: The Protocol", draft-
ietf-ldapbis-protocol-xx.txt, a work in progress. ietf-ldapbis-protocol-xx.txt, a work in progress.
[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",
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 [RFC2732] Hinden, R., Carpenter, B., Masinter, L., "Format for
Literal IPv6 Addresses in URL's", RFC 2732, December 1999. Literal IPv6 Addresses in URL's", RFC 2732, December 1999.
[RFC3383] Zeilenga, K., "Internet Assigned Numbers Authority (IANA)
Considerations for the Lightweight Directory Access Protocol
(LDAP)", RFC 3383, September 2002.
[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. Informative References [UTF-8] Yergeau, F., "UTF-8, a transformation format of ISO 10646",
draft-yergeau-rfc2279bis-xx.txt, a work in progress.
10. Informative References
None. None.
12. Authors' Address 11. Intellectual Property Rights
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any 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 such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
12. Acknowledgements
The LDAP URL format was originally defined at the University of
Michigan. This material is based upon work supported by the National
Science Foundation under Grant No. NCR-9416667. The support of both
the University of Michigan and the National Science Foundation is
gratefully acknowledged.
This document is an update to RFC 2255 by Tim Howes and Mark Smith.
Changes included in this revised specification are based upon
discussions among the authors, discussions within the LDAP (v3)
Revision Working Group (ldapbis), and discussions within other IETF
Working Groups. The contributions of individuals in these working
groups is gratefully acknowledged. Several people in particular have
made valuable comments on this document; RL "Bob" Morgan, Mark Wahl,
Kurt Zeilenga, Jim Sermersheim, and Hallvard Furuseth deserve special
thanks for their contributions.
13. 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 MarkCSmithWork@aol.com
Tim Howes Tim Howes
Opsware, Inc. Opsware, Inc.
599 N. Mathilda Ave. 599 N. Mathilda Ave.
Sunnyvale, CA 94085 Sunnyvale, CA 94085
USA USA
+1 408 744-7509 +1 408 744-7509
howes@opsware.com howes@opsware.com
13. Full Copyright Statement 14. Full Copyright Statement
Copyright (C) The Internet Society (2003). 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
skipping to change at page 10, line 42 skipping to change at page 11, line 34
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.
14. Appendix A: Changes Since RFC 2255 15. Appendix A: Changes Since RFC 2255
14.1. Technical Changes 15.1. Technical Changes
The following technical changes were made to the contents of the "URL The following technical changes were made to the contents of the "URL
Definition" section: Definition" section:
Revised all of the ABNF to use common productions from [Models]. Revised all of the ABNF to use common productions from [Models].
Added note and references to [RFC2732] to allow literal IPv6 Added note and references to [RFC2732] to allow literal IPv6
addresses inside the hostport portion of the URL. addresses inside the hostport portion of the URL.
Added missing ASTERIX as an alternative for the attrdesc part of the Added missing ASTERISK as an alternative for the attrdesc part of the
URL. It is believed that existing implementations of RFC 2255 URL. It is believed that existing implementations of RFC 2255
already support this. already support this.
Added angle brackets around free-form prose in the "dn", "hostport", Added angle brackets around free-form prose in the "dn", "hostport",
"attrdesc", "filter", and "exvalue" rules. "attrdesc", "filter", and "exvalue" rules.
Changed the ABNF for ldapurl to group the dn component with the Changed the ABNF for ldapurl to group the dn component with the
preceding slash. preceding slash.
Changed the extype rule to be an LDAPOID from [Protocol] or an OID Changed the extype rule to be an LDAPOID from [Protocol] or an OID
description from [LDAPIANA]. description from [RFC3383].
Changed the text about extension types so it references [LDAPIANA]. Changed the text about extension types so it references [RFC3383].
Reordered rules to more closely follow the order the elements appear Reordered rules to more closely follow the order the elements appear
in the URL. in the URL.
"Bindname Extension": removed due to lack of known implementations. "Bindname Extension": removed due to lack of known implementations.
14.2. Editorial Changes 15.2. Editorial Changes
Changed document title to include "LDAP:" prefix. Changed document title to include "LDAP:" prefix.
IESG Note: removed note about lack of satisfactory mandatory IESG Note: removed note about lack of satisfactory mandatory
authentication mechanisms. authentication mechanisms.
"Status of this Memo" section: updated boilerplate to match current "Status of this Memo" section: updated boilerplate to match current
I-D guidelines. I-D guidelines.
"Abstract" section: separated from introductory material. "Abstract" section: separated from introductory material.
skipping to change at page 12, line 23 skipping to change at page 13, line 13
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 an example that demonstrates the interaction between DN Changed the name of an attribute used in one example from "int" to
escaping and URL escaping. Added some examples to show URL "four-octet" to avoid potential confusion. Added an example that
equivalence with respect to the dn portion of the URL. demonstrates the interaction between DN 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, Jim Sermersheim, and update to RFC 2255. Added Kurt Zeilenga, Jim Sermersheim, and
Hallvard Furuseth. 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, 2829, and 3383. Updated
references to the appropriate sections within RFC 2396. Updated the RFC 1738 references to the appropriate sections within RFC 2396.
references to refer to LDAPBis WG documents. Removed the reference to Updated the references to refer to LDAPBis WG documents. Removed the
the LDAP Attribute Syntaxes document and added references to the LDAP reference to the LDAP Attribute Syntaxes document and added a
IANA and Roadmap documents. reference to the Roadmap document.
"Informative References" section: added for clarity. "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.
15. Appendix B: Changes Since Previous Document Revision 16. 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 previously published
revision, draft-ietf-ldapbis-url-02.txt. Note that when appropriate revision, draft-ietf-ldapbis-url-03.txt. Note that when appropriate
these changes are also included in Appendix A, but are also included these changes are also included in Appendix A, but are also included
here for the benefit of the people who have already reviewed draft- here for the benefit of the people who have already reviewed draft-
ietf-ldapbis-url-02.txt. This section will be removed before this ietf-ldapbis-url-03.txt. This section will be removed before this
document is published as an RFC. document is published as an RFC.
15.1. Technical Changes 16.1. Technical Changes
"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.
15.2. Editorial Changes
"Status of this Memo" section: updated boilerplate to match current None.
I-D guidelines.
"URL Definition" section: replaced misleading phrase "MAY define 16.2. Editorial Changes
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.
"Examples" section: added an example that demonstrates the "URL Definition" section: added comments in the ABNF to point the
interaction between DN escaping and URL escaping and clarified the reader to the "Escaping Using the % Method" section, which was
text that introduces the LDAP filter escaping interaction example. changed into a section of its own to highlight the importance of
escaping the URL components correctly.
"Acknowledgements" section: added Hallvard Furuseth. "Examples" section: changed the name of an attribute used in one
example from "int" to "four-octet" to avoid potential confusion.
"Normative References" section: added a reference to [RFC2732]. Replaced all occurrences of "asterix" with the correctly spelled
"asterisk."
"Informative References" section: added for clarity. "Normative References" section: changed UTF-8 reference to point to
the UTF-8 Internet Draft; replace [LDAPIANA] Internet Draft reference
with a reference to RFC 3383.
Copyright: updated the year to 2003. "Intellectual Property Rights" section: added.
"Authors' Address" section: updated Tim's contact information. Author's Addresses section: New email address for Mark Smith.
Appendix A: added an older editorial change that was accidently "Full Copyright Statement" section: updated text to match latest IETF
overlooked (Changed document title to include "LDAP:" prefix). guidelines.
This Internet Draft expires on 28 August 2003. This Internet Draft expires on 25 April 2004.
 End of changes. 

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