7 Network Working Group Mark Smith, Editor
8 Request for Comments: DRAFT Netscape Communications Corp.
9 Obsoletes: RFC 2255 Tim Howes
10 Expires: 25 April 2004 Opsware, Inc.
15 LDAP: Uniform Resource Locator
16 <draft-ietf-ldapbis-url-04.txt>
20 1. Status of this Memo
22 This document is an Internet-Draft and is subject to all provisions
23 of Section 10 of RFC2026.
25 Internet-Drafts are working documents of the Internet Engineering
26 Task Force (IETF), its areas, and its working groups. Note that
27 other groups may also distribute working documents as Internet-
30 Internet-Drafts are draft documents valid for a maximum of six months
31 and may be updated, replaced, or obsoleted by other documents at any
32 time. It is inappropriate to use Internet- Drafts as reference
33 material or to cite them other than as "work in progress."
35 The list of current Internet-Drafts can be accessed at
36 http://www.ietf.org/1id-abstracts.html
38 The list of Internet-Draft Shadow Directories can be accessed at
39 http://www.ietf.org/shadow.html
41 Discussion of this document should take place on the LDAP (v3)
42 Revision (ldapbis) Working Group mailing list <ietf-
43 ldapbis@openldap.org>.
45 Copyright (C) The Internet Society (2003). All Rights Reserved.
49 This document describes a format for an LDAP Uniform Resource Locator
50 (URL). An LDAP URL describes an LDAP search operation that is used
51 to retrieve information from an LDAP directory, or, in the context of
52 an LDAPv3 referral or reference, an LDAP URL describes a service
53 where an LDAP operation may be progressed.
58 Smith & Howes Intended Category: Standards Track [Page 1]
60 INTERNET-DRAFT LDAP: Uniform Resource Locator 25 October 2003
65 1. Status of this Memo............................................1
66 2. Abstract.......................................................1
67 3. Table of Contents..............................................2
68 4. Introduction...................................................2
69 5. URL Definition.................................................2
70 5.1. Escaping Using the Method.................................4
71 6. Defaults for Fields of the LDAP URL............................5
72 7. Examples.......................................................6
73 8. Security Considerations........................................8
74 9. Normative References...........................................8
75 10. Informative References.........................................9
76 11. Intellectual Property Rights...................................9
77 12. Acknowledgements...............................................10
78 13. Authors' Address...............................................10
79 14. Full Copyright Statement.......................................11
80 15. Appendix A: Changes Since RFC 2255.............................11
81 15.1. Technical Changes...........................................11
82 15.2. Editorial Changes...........................................12
83 16. Appendix B: Changes Since Previous Document Revision...........13
84 16.1. Technical Changes...........................................14
85 16.2. Editorial Changes...........................................14
89 LDAP is the Lightweight Directory Access Protocol, defined in
90 [Protocol]. This document specifies the LDAP URL format for version
91 3 of LDAP and clarifies how LDAP URLs are resolved. This document
92 also defines an extension mechanism for LDAP URLs, so that future
93 documents can extend their functionality, for example, to provide
94 access to new LDAPv3 extensions as they are defined. Note: not all
95 of the parameters of the LDAP search operation described in
96 [Protocol] can be expressed using the format defined in this
99 This document is an integral part of the LDAP Technical Specification
102 This document replaces RFC 2255. See Appendix A for a list of changes
103 relative to RFC 2255.
105 The key words "MUST", "MAY", and "SHOULD" used in this document are
106 to be interpreted as described in [RFC2119].
110 An LDAP URL begins with the protocol prefix "ldap" and is defined by
114 Smith & Howes Intended Category: Standards Track [Page 2]
116 INTERNET-DRAFT LDAP: Uniform Resource Locator 25 October 2003
119 the following grammar, following the ABNF notation defined in
122 ldapurl = scheme COLON SLASH SLASH [hostport] [SLASH dn
123 [QUESTION [attributes] [QUESTION [scope]
124 [QUESTION [filter] [QUESTION extensions]]]]]
126 hostport = <hostport from Section 3.2.2 of [RFC2396]>
127 ; as updated by [RFC2732] to allow IPv6 literal addresses
128 dn = <distinguishedName from Section 3 of [LDAPDN]>
129 ; see the "Escaping Using the % Method" section below.
130 attributes = attrdesc *(COMMA attrdesc)
131 attrdesc = <AttributeDescription from Section 4.1.4 of [Protocol]>
133 ; see the "Escaping Using the % Method" section below.
134 scope = "base" / "one" / "sub"
135 filter = <filter from Section 4 of [Filters]>
136 ; see the "Escaping Using the % Method" section below.
137 extensions = extension *(COMMA extension)
138 extension = [EXCLAMATION] extype [EQUALS exvalue]
139 extype = oid / oiddescr
140 exvalue = <LDAPString from section 4.1.2 of [Protocol]>
141 ; see the "Escaping Using the % Method" section below.
142 oid = <LDAPOID from section 4.1.2 of [Protocol]>
143 oiddescr = <name from section 3.3 of [RFC3383]>
145 EXCLAMATION = %x21 ; exclamation mark ("!")
146 ASTERISK = %x2A ; asterisk ("*")
147 COLON = %x3A ; colon (":")
148 QUESTION = %x3F ; question mark ("?")
149 SLASH = %x5C; forward slash ("/")
152 The "ldap" prefix indicates an entry or entries residing in the LDAP
153 server running on the given hostname at the given portnumber. Note
154 that the hostport may contain literal IPv6 addresses as specified in
157 The dn is an LDAP Distinguished Name using the string format
158 described in [LDAPDN]. It identifies the base object of the LDAP
159 search or the target of a non-search operation.
161 The attributes construct is used to indicate which attributes should
162 be returned from the entry or entries. Individual attrdesc names are
163 as defined for AttributeDescription in [Protocol].
165 The scope construct is used to specify the scope of the search to
166 perform in the given LDAP server. The allowable scopes are "base"
170 Smith & Howes Intended Category: Standards Track [Page 3]
172 INTERNET-DRAFT LDAP: Uniform Resource Locator 25 October 2003
175 for a base object search, "one" for a one-level search, or "sub" for
178 The filter is used to specify the search filter to apply to entries
179 within the specified scope during the search. It has the format
180 specified in [Filters].
182 The extensions construct provides the LDAP URL with an extensibility
183 mechanism, allowing the capabilities of the URL to be extended in the
184 future. Extensions are a simple comma-separated list of type=value
185 pairs, where the =value portion MAY be omitted for options not
186 requiring it. Each type=value pair is a separate extension. These
187 LDAP URL extensions are not necessarily related to any of the LDAPv3
188 extension mechanisms. Extensions may be supported or unsupported by
189 the client resolving the URL. An extension prefixed with a '!'
190 character (ASCII 33) is critical. An extension not prefixed with a
191 '!' character is non-critical.
193 If an extension is supported by the client, the client MUST obey the
194 extension if the extension is critical. The client SHOULD obey
195 supported extensions that are non-critical.
197 If an extension is unsupported by the client, the client MUST NOT
198 process the URL if the extension is critical. If an unsupported
199 extension is non-critical, the client MUST ignore the extension.
201 If a critical extension cannot be processed successfully by the
202 client, the client MUST NOT process the URL. If a non-critical
203 extension cannot be processed successfully by the client, the client
204 SHOULD ignore the extension.
206 The extension type (extype) MAY be specified using the oid form
207 (e.g., 1.2.3.4) or the oiddesc form (e.g., myLDAPURLExtension). Use
208 of the oiddesc form SHOULD be restricted to registered object
209 identifier descriptive names. See [RFC3383] for registration details
210 and usage guidelines for descriptive names.
212 No LDAP URL extensions are defined in this document. Other documents
213 or a future version of this document MAY define one or more
216 5.1. Escaping Using the % Method
218 A generated LDAP URL MUST consist only of the restricted set of
219 characters included in the uric production that is defined in section
220 2 of [RFC2396]. Implementations SHOULD accept other valid UTF-8
221 strings [UTF-8] as input. An octet MUST be escaped using the %
222 method described in section 2.4 of [RFC2396] in any of these
226 Smith & Howes Intended Category: Standards Track [Page 4]
228 INTERNET-DRAFT LDAP: Uniform Resource Locator 25 October 2003
233 The octet is not in the reserved set defined in section 2.2 of
234 [RFC2396] or in the unreserved set defined in section 2.3 of
237 It is the single Reserved character '?' and occurs inside a dn,
238 filter, or other element of an LDAP URL.
240 It is a comma character ',' that occurs inside an extension value.
242 6. Defaults for Fields of the LDAP URL
244 Some fields of the LDAP URL are optional, as described above. In the
245 absence of any other specification, the following general defaults
246 SHOULD be used when a field is absent. Note: other documents MAY
247 specify different defaulting rules; for example, section 4.1.11 of
248 [Protocol] specifies a different rule for determining the correct DN
249 to use when it is absent in an LDAP URL that is returned as a
253 The default LDAP port is TCP port 389. If no hostport is given,
254 the client must have some apriori knowledge of an appropriate LDAP
258 If no dn is given, the default is the zero-length DN, "".
261 If the attributes part is omitted, all user attributes of the
262 entry or entries should be requested (e.g., by setting the
263 attributes field AttributeDescriptionList in the LDAP search
264 request to a NULL list, or (in LDAPv3) by requesting the special
268 If scope is omitted, a scope of "base" is assumed.
271 If filter is omitted, a filter of "(objectClass=*)" is assumed.
274 If extensions is omitted, no extensions are assumed.
282 Smith & Howes Intended Category: Standards Track [Page 5]
284 INTERNET-DRAFT LDAP: Uniform Resource Locator 25 October 2003
289 The following are some example LDAP URLs using the format defined
290 above. The first example is an LDAP URL referring to the University
291 of Michigan entry, available from an LDAP server of the client's
294 ldap:///o=University%20of%20Michigan,c=US
296 The next example is an LDAP URL referring to the University of
297 Michigan entry in a particular ldap server:
299 ldap://ldap1.example.net/o=University%20of%20Michigan,c=US
301 Both of these URLs correspond to a base object search of the
302 "o=University of Michigan,c=US" entry using a filter of
303 "(objectclass=*)", requesting all attributes.
305 The next example is an LDAP URL referring to only the postalAddress
306 attribute of the University of Michigan entry:
308 ldap://ldap1.example.net/o=University%20of%20Michigan,
311 The corresponding LDAP search operation is the same as in the
312 previous example, except that only the postalAddress attribute is
315 The next example is an LDAP URL referring to the set of entries found
316 by querying the given LDAP server on port 6666 and doing a subtree
317 search of the University of Michigan for any entry with a common name
318 of "Babs Jensen", retrieving all attributes:
320 ldap://ldap1.example.net:6666/o=University%20of%20Michigan,
321 c=US??sub?(cn=Babs%20Jensen)
323 The next example is an LDAP URL referring to all children of the c=GB
326 ldap://ldap1.example.com/c=GB?objectClass?one
328 The objectClass attribute is requested to be returned along with the
329 entries, and the default filter of "(objectclass=*)" is used.
331 The next example is an LDAP URL to retrieve the mail attribute for
332 the LDAP entry named "o=Question?,c=US" is given below, illustrating
333 the use of the escaping mechanism on the reserved character '?'.
338 Smith & Howes Intended Category: Standards Track [Page 6]
340 INTERNET-DRAFT LDAP: Uniform Resource Locator 25 October 2003
343 ldap://ldap2.example.com/o=Question%3f,c=US?mail
345 The next example illustrates the interaction between the LDAP string
346 representation of filters quoting mechanism and URL quoting
349 ldap://ldap3.example.com/o=Babsco,c=US???(four-octet=%5c00%5c00%5c00%5c04)
350 IP The filter in this example uses the LDAP escaping mechanism of \
351 to encode three zero or null bytes in the value. In LDAP, the filter
352 would be written as (four-octet=\00\00\00\04). Because the \
353 character must be escaped in a URL, the \'s are escaped as %5c in the
356 The next example illustrates the interaction between the LDAP string
357 representation of DNs quoting mechanism and URL quoting mechanisms.
359 ldap://ldap.example.com/o=An%20Example%5c2c%20Inc.,c=US
361 The DN encoded in the above URL is:
363 o=An Example\2c Inc.,c=US
365 That is, the left-most RDN value is:
369 The following three URLs that are equivalent, assuming that the
370 defaulting rules specified in section 4 of this document are used:
372 ldap://ldap.example.net
373 ldap://ldap.example.net/
374 ldap://ldap.example.net/?
376 These three URLs all point to the root DSE on the ldap.example.net
379 The final two examples show use of a hypothetical, experimental bind
380 name extension (the value associated with the extension is an LDAP DN).
382 ldap:///??sub??e-bindname=cn=Manager%2cdc=example%2cdc=com
383 ldap:///??sub??!e-bindname=cn=Manager%2cdc=example%2cdc=com
385 The two URLs are the same, except that the second one marks the e-
386 bindname extension as critical. Notice the use of the % encoding
387 method to encode the commas within the distinguished name value in
388 the e-bindname extension.
394 Smith & Howes Intended Category: Standards Track [Page 7]
396 INTERNET-DRAFT LDAP: Uniform Resource Locator 25 October 2003
399 8. Security Considerations
401 General URL security considerations discussed in [RFC2396] are
402 relevant for LDAP URLs.
404 The use of security mechanisms when processing LDAP URLs requires
405 particular care, since clients may encounter many different servers
406 via URLs, and since URLs are likely to be processed automatically,
407 without user intervention. A client SHOULD have a user-configurable
408 policy about which servers to connect to using which security
409 mechanisms, and SHOULD NOT make connections that are inconsistent
410 with this policy. If a client chooses to reuse an existing
411 connection when resolving one or more LDAP URL, it MUST ensure that
412 the connection is compatible with the URL and that no security
413 policies are violated.
415 Sending authentication information, no matter the mechanism, may
416 violate a user's privacy requirements. In the absence of specific
417 policy permitting authentication information to be sent to a server,
418 a client should use an anonymous connection. (Note that clients
419 conforming to previous LDAP URL specifications, where all connections
420 are anonymous and unprotected, are consistent with this
421 specification; they simply have the default security policy.) Simply
422 opening a connection to another server may violate some users'
423 privacy requirements, so clients should provide the user with a way
424 to control URL processing.
426 Some authentication methods, in particular reusable passwords sent to
427 the server, may reveal easily-abused information to the remote server
428 or to eavesdroppers in transit, and should not be used in URL
429 processing unless explicitly permitted by policy. Confirmation by
430 the human user of the use of authentication information is
431 appropriate in many circumstances. Use of strong authentication
432 methods that do not reveal sensitive information is much preferred.
433 If the URL represents a referral for an update operation, strong
434 authentication methods SHOULD be used. Please refer to the Security
435 Considerations section of [AuthMeth] for more information.
437 The LDAP URL format allows the specification of an arbitrary LDAP
438 search operation to be performed when evaluating the LDAP URL.
439 Following an LDAP URL may cause unexpected results, for example, the
440 retrieval of large amounts of data, the initiation of a long-lived
441 search, etc. The security implications of resolving an LDAP URL are
442 the same as those of resolving an LDAP search query.
444 9. Normative References
446 [LDAPDN] Zeilenga, K. (editor), "LDAP: String Representation of
450 Smith & Howes Intended Category: Standards Track [Page 8]
452 INTERNET-DRAFT LDAP: Uniform Resource Locator 25 October 2003
455 Distinguished Names", draft-ietf-ldapbis-dn-xx.txt, a work in
458 [Filters] Smith, M. and Howes, T., "LDAP: String Representation of
459 Search Filters", draft-ietf-ldapbis-filter-xx.txt, a work in
462 [RFC2119] Bradner, S., "Key Words for use in RFCs to Indicate
463 Requirement Levels," RFC 2119, BCP 14, March 1997.
465 [Protocol] Sermersheim, J. (editor), "LDAP: The Protocol", draft-
466 ietf-ldapbis-protocol-xx.txt, a work in progress.
468 [RFC2234] Crocker, D., Overell, P., "Augmented BNF for Syntax
469 Specifications: ABNF", RFC 2234, November 1997.
471 [RFC2396] Berners-Lee, T., Fielding, R., and Masinter, L., "Uniform
472 Resource Identifiers (URI): Generic Syntax", RFC 2396, August 1998.
474 [RFC2732] Hinden, R., Carpenter, B., Masinter, L., "Format for
475 Literal IPv6 Addresses in URL's", RFC 2732, December 1999.
477 [RFC3383] Zeilenga, K., "Internet Assigned Numbers Authority (IANA)
478 Considerations for the Lightweight Directory Access Protocol
479 (LDAP)", RFC 3383, September 2002.
481 [AuthMeth] Harrison, R. (editor), "LDAP: Authentication Methods",
482 draft-ietf-ldapbis-authmeth-xx.txt, a work in progress. a work in
485 [Roadmap] K. Zeilenga (editor), "LDAP: Technical Specification Road
486 Map", draft-ietf-ldapbis-roadmap-xx.txt, a work in progress.
488 [UTF-8] Yergeau, F., "UTF-8, a transformation format of ISO 10646",
489 draft-yergeau-rfc2279bis-xx.txt, a work in progress.
491 10. Informative References
495 11. Intellectual Property Rights
497 The IETF takes no position regarding the validity or scope of any
498 intellectual property or other rights that might be claimed to
499 pertain to the implementation or use of the technology described in
500 this document or the extent to which any license under such rights
501 might or might not be available; neither does it represent that it
502 has made any effort to identify any such rights. Information on the
506 Smith & Howes Intended Category: Standards Track [Page 9]
508 INTERNET-DRAFT LDAP: Uniform Resource Locator 25 October 2003
511 IETF's procedures with respect to rights in standards-track and
512 standards-related documentation can be found in BCP-11. Copies of
513 claims of rights made available for publication and any assurances of
514 licenses to be made available, or the result of an attempt made to
515 obtain a general license or permission for the use of such
516 proprietary rights by implementors or users of this specification can
517 be obtained from the IETF Secretariat.
519 The IETF invites any interested party to bring to its attention any
520 copyrights, patents or patent applications, or other proprietary
521 rights which may cover technology that may be required to practice
522 this standard. Please address the information to the IETF Executive
527 The LDAP URL format was originally defined at the University of
528 Michigan. This material is based upon work supported by the National
529 Science Foundation under Grant No. NCR-9416667. The support of both
530 the University of Michigan and the National Science Foundation is
531 gratefully acknowledged.
533 This document is an update to RFC 2255 by Tim Howes and Mark Smith.
534 Changes included in this revised specification are based upon
535 discussions among the authors, discussions within the LDAP (v3)
536 Revision Working Group (ldapbis), and discussions within other IETF
537 Working Groups. The contributions of individuals in these working
538 groups is gratefully acknowledged. Several people in particular have
539 made valuable comments on this document; RL "Bob" Morgan, Mark Wahl,
540 Kurt Zeilenga, Jim Sermersheim, and Hallvard Furuseth deserve special
541 thanks for their contributions.
546 Netscape Communications Corp.
547 360 W. Caribbean Drive
551 MarkCSmithWork@aol.com
562 Smith & Howes Intended Category: Standards Track [Page 10]
564 INTERNET-DRAFT LDAP: Uniform Resource Locator 25 October 2003
569 14. Full Copyright Statement
571 Copyright (C) The Internet Society (2003). All Rights Reserved.
573 This document and translations of it may be copied and furnished to
574 others, and derivative works that comment on or otherwise explain it
575 or assist in its implementation may be prepared, copied, published
576 and distributed, in whole or in part, without restriction of any
577 kind, provided that the above copyright notice and this paragraph are
578 included on all such copies and derivative works. However, this
579 document itself may not be modified in any way, such as by removing
580 the copyright notice or references to the Internet Society or other
581 Internet organizations, except as needed for the purpose of
582 developing Internet standards in which case the procedures for
583 copyrights defined in the Internet Standards process must be
584 followed, or as required to translate it into languages other than
587 The limited permissions granted above are perpetual and will not be
588 revoked by the Internet Society or its successors or assigns.
590 This document and the information contained herein is provided on an
591 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
592 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
593 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
594 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
595 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
597 15. Appendix A: Changes Since RFC 2255
599 15.1. Technical Changes
601 The following technical changes were made to the contents of the "URL
604 Revised all of the ABNF to use common productions from [Models].
606 Added note and references to [RFC2732] to allow literal IPv6
607 addresses inside the hostport portion of the URL.
609 Added missing ASTERISK as an alternative for the attrdesc part of the
610 URL. It is believed that existing implementations of RFC 2255
611 already support this.
613 Added angle brackets around free-form prose in the "dn", "hostport",
614 "attrdesc", "filter", and "exvalue" rules.
618 Smith & Howes Intended Category: Standards Track [Page 11]
620 INTERNET-DRAFT LDAP: Uniform Resource Locator 25 October 2003
623 Changed the ABNF for ldapurl to group the dn component with the
626 Changed the extype rule to be an LDAPOID from [Protocol] or an OID
627 description from [RFC3383].
629 Changed the text about extension types so it references [RFC3383].
630 Reordered rules to more closely follow the order the elements appear
633 "Bindname Extension": removed due to lack of known implementations.
636 15.2. Editorial Changes
638 Changed document title to include "LDAP:" prefix.
640 IESG Note: removed note about lack of satisfactory mandatory
641 authentication mechanisms.
643 "Status of this Memo" section: updated boilerplate to match current
646 "Abstract" section: separated from introductory material.
648 "Table of Contents" section: added.
650 "Introduction" section: new section; separated from the Abstract.
651 Changed the text indicate that RFC 2255 is replaced by this document
652 (instead of RFC 1959). Added text to indicate that LDAP URLs are
653 used for references and referrals. Fixed typo (replaced the nonsense
654 phrase "to perform to retrieve" with "used to retrieve"). Added a
655 note to let the reader know that not all of the parameters of the
656 LDAP search operation described in [Protocol] can be expressed using
659 "URL Definition" section: removed second copy of ldapurl grammar and
660 following two paragraphs (editorial error in RFC 2255). Fixed line
661 break within '!' sequence. Reworded last paragraph to clarify which
662 characters must be URL escaped. Added text to indicate that LDAP
663 URLs are used for references and referrals. Added text that refers
664 to the ABNF from RFC 2234.
666 "Defaults for Fields of the LDAP URL" section: added; formed by
667 moving text about defaults out of the "URL Definition" section.
669 "URL Processing" section: clarified that connections MAY be reused
670 only if the open connection is compatible with the URL. Added text
674 Smith & Howes Intended Category: Standards Track [Page 12]
676 INTERNET-DRAFT LDAP: Uniform Resource Locator 25 October 2003
679 to indicate that use of security services is encouraged and that they
680 SHOULD be used when updates are involved. Removed "dn" from
681 discussion of authentication methods. Added note that the client MAY
682 interrogate the server to determine the most appropriate method.
684 "Examples" section: Modified examples to use example.com and
685 example.net hostnames. Added missing '?' to the LDAP URL example
686 whose filter contains three null bytes. Removed space after one
687 comma within a DN. Revised the bindname example to use e-bindname.
688 Changed the name of an attribute used in one example from "int" to
689 "four-octet" to avoid potential confusion. Added an example that
690 demonstrates the interaction between DN escaping and URL escaping.
691 Added some examples to show URL equivalence with respect to the dn
694 "Security Considerations" section: Added a note about connection
695 reuse. Added a note about using strong authentication methods for
696 updates. Added a reference to RFC 2829. Added note that simply
697 opening a connection may violate some users' privacy requirements.
699 "Acknowledgements" section: added statement about this being an
700 update to RFC 2255. Added Kurt Zeilenga, Jim Sermersheim, and
703 "Normative References" section: renamed from "References" per new RFC
704 guidelines. Changed from [1] style to [Protocol] style throughout the
705 document. Added references to RFCs 2234, 2829, and 3383. Updated
706 RFC 1738 references to the appropriate sections within RFC 2396.
707 Updated the references to refer to LDAPBis WG documents. Removed the
708 reference to the LDAP Attribute Syntaxes document and added a
709 reference to the Roadmap document.
711 "Informative References" section: added for clarity.
713 Header and "Authors' Address" sections: added "editor" next to Mark
714 Smith's name. Updated affiliation and contact information.
716 Copyright: updated the year.
719 16. Appendix B: Changes Since Previous Document Revision
721 This appendix lists all changes relative to the previously published
722 revision, draft-ietf-ldapbis-url-03.txt. Note that when appropriate
723 these changes are also included in Appendix A, but are also included
724 here for the benefit of the people who have already reviewed draft-
725 ietf-ldapbis-url-03.txt. This section will be removed before this
726 document is published as an RFC.
730 Smith & Howes Intended Category: Standards Track [Page 13]
732 INTERNET-DRAFT LDAP: Uniform Resource Locator 25 October 2003
735 16.1. Technical Changes
740 16.2. Editorial Changes
742 "URL Definition" section: added comments in the ABNF to point the
743 reader to the "Escaping Using the % Method" section, which was
744 changed into a section of its own to highlight the importance of
745 escaping the URL components correctly.
747 "Examples" section: changed the name of an attribute used in one
748 example from "int" to "four-octet" to avoid potential confusion.
750 Replaced all occurrences of "asterix" with the correctly spelled
753 "Normative References" section: changed UTF-8 reference to point to
754 the UTF-8 Internet Draft; replace [LDAPIANA] Internet Draft reference
755 with a reference to RFC 3383.
757 "Intellectual Property Rights" section: added.
759 Author's Addresses section: New email address for Mark Smith.
761 "Full Copyright Statement" section: updated text to match latest IETF
765 This Internet Draft expires on 25 April 2004.
786 Smith & Howes Intended Category: Standards Track [Page 14]