[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: I-D ACTION:draft-ietf-ldapbis-url-07.txt
I have completed my review of the I-D. While it's my personal
opinion that the revisions made are consistent with WG
consensus, I did find a few minor problems which likely
should be addressed prior to progression. Most significantly,
a few aspects of the I-D need updated to be consistent with
the ABNF definitions of [Protocol] and [Models]. I suggest
the <extype> rule be clarified and examples changed slightly
to demonstrate case-insensitive. I also make a few editorial
suggestions to improve clarity and/or to remove nits. See
attachment for details.
Kurt
At 01:34 PM 10/25/2004, Kurt D. Zeilenga wrote:
>Please review this I-D to ensure the changes made (or not made)
>in this revision are consistent with WG consensus, as reflected
>in the summary of the WG Last Call and follow-up discussions.
>The chairs intend to progress this revision to the AD within
>the next week.
>
>-- Kurt, LDAPBIS co-chair
>
>
>At 01:03 PM 10/25/2004, Internet-Drafts@ietf.org wrote:
>>A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>This draft is a work item of the LDAP (v3) Revision Working Group of the IETF.
>>
>> Title : LDAP: Uniform Resource Locator
>> Author(s) : M. Smith, T. Howes
>> Filename : draft-ietf-ldapbis-url-07.txt
>> Pages : 15
>> Date : 2004-10-25
>>
>>This document describes a format for an LDAP Uniform Resource Locator
>>(URL). An LDAP URL describes an LDAP search operation that is used
>>to retrieve information from an LDAP directory, or, in the context of
>>an LDAPv3 referral or reference, an LDAP URL describes a service
>>where an LDAP operation may be progressed.
>>
>>A URL for this Internet-Draft is:
>>http://www.ietf.org/internet-drafts/draft-ietf-ldapbis-url-07.txt
>>
>>To remove yourself from the I-D Announcement list, send a message to
>>i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.
>>You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
>>to change your subscription settings.
>>
>>
>>Internet-Drafts are also available by anonymous FTP. Login with the username
>>"anonymous" and a password of your e-mail address. After logging in,
>>type "cd internet-drafts" and then
>> "get draft-ietf-ldapbis-url-07.txt".
>>
>>A list of Internet-Drafts directories can be found in
>>http://www.ietf.org/shadow.html
>>or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>
>>
>>Internet-Drafts can also be obtained by e-mail.
>>
>>Send a message to:
>> mailserv@ietf.org.
>>In the body type:
>> "FILE /internet-drafts/draft-ietf-ldapbis-url-07.txt".
>>
>>NOTE: The mail server at ietf.org can return the document in
>> MIME-encoded form by using the "mpack" utility. To use this
>> feature, insert the command "ENCODING mime" before the "FILE"
>> command. To decode the response(s), you will need "munpack" or
>> a MIME-compliant mail reader. Different MIME-compliant mail readers
>> exhibit different behavior, especially when dealing with
>> "multipart" MIME messages (i.e. documents which have been split
>> up into multiple messages), so check your local documentation on
>> how to manipulate these messages.
>>
>>
>>Below is the data which will enable a MIME compliant mail reader
>>implementation to automatically retrieve the ASCII version of the
>>Internet-Draft.
>>Content-Type: text/plain
>>Content-ID: <2004-10-25162124.I-D@ietf.org>
>>
>>ENCODING mime
>>FILE /internet-drafts/draft-ietf-ldapbis-url-07.txt
>>
>><ftp://ftp.ietf.org/internet-drafts/draft-ietf-ldapbis-url-07.txt>
>
>Network Working Group Mark Smith, Editor
>Request for Comments: DRAFT Pearl Crescent, LLC
>Obsoletes: RFC 2255 Tim Howes
>Expires: 24 April 2005 Opsware, Inc.
>
> 24 October 2004
>
>
> LDAP: Uniform Resource Locator
> <draft-ietf-ldapbis-url-07.txt>
>
>
>
>Status of this Memo
>
> By submitting this Internet-Draft, each author represents that any
> applicable patent or other IPR claims of which he or she is aware
> have been or will be disclosed, and any of which he or she become
> aware will be disclosed, in accordance with RFC 3668.
>
> This document is intended to be published as a Standards Track RFC,
> replacing RFC 2255. Distribution of this memo is unlimited.
> Technical discussion of this document will take place on the IETF
> LDAP (v3) Revision (ldapbis) Working Group mailing list
> <ietf-ldapbis@openldap.org>. Please send editorial comments directly
> to the editor <mcs@pearlcrescent.com>.
>
> Internet-Drafts are working documents of the Internet Engineering
> Task Force (IETF), its areas, and its working groups. Note that
> other groups may also distribute working documents as
> Internet-Drafts.
>
> Internet-Drafts are draft documents valid for a maximum of six months
> and may be updated, replaced, or obsoleted by other documents at any
> time. It is inappropriate to use Internet-Drafts as reference
> material or to cite them other than a "work in progress."
>
> The list of current Internet-Drafts can be accessed at
> http://www.ietf.org/1id-abstracts.html
>
> The list of Internet-Draft Shadow Directories can be accessed at
> http://www.ietf.org/shadow.html
>
> Copyright (C) The Internet Society (2004). All Rights Reserved.
> Please see the Full Copyright section near the end of this document
> for more information.
>
>
>
>
>
>
>
>Abstract
>
> This document describes a format for an LDAP Uniform Resource Locator
> (URL). An LDAP URL describes an LDAP search operation that is used
Spell LDAP out of first use.
> to retrieve information from an LDAP directory, or, in the context of
> an LDAPv3 referral or reference, an LDAP URL describes a service
> where an LDAP operation may be progressed.
>
>Table of Contents
>
> Status of this Memo............................................1
> Abstract.......................................................2
> Table of Contents..............................................2
>1. Introduction...................................................2
>2. URL Definition.................................................3
>2.1. Escaping Using the % Method.................................5
>3. Defaults for Fields of the LDAP URL............................5
>4. Examples.......................................................6
>5. Security Considerations........................................8
>6. IANA Considerations............................................9
>7. Normative References...........................................9
>8. Informative References.........................................10
>9. Intellectual Property Rights...................................10
>10. Acknowledgements...............................................10
>11. Authors' Addresses.............................................11
>12. Appendix A: Changes Since RFC 2255.............................11
>12.1. Technical Changes...........................................11
>12.2. Editorial Changes...........................................12
>13. Appendix B: Changes Since Previous Document Revision...........13
>13.1. Editorial Changes...........................................14
>14. Intellectual Property Rights...................................14
>15. Full Copyright.................................................14
Last sections should be unnumbered.
>1. Introduction
>
> LDAP is the Lightweight Directory Access Protocol, defined in
> [Protocol].
s/[Protocol]/[Roadmap]/
> This document specifies the LDAP URL format for version
> 3 of LDAP and clarifies how LDAP URLs are resolved. This document
> also defines an extension mechanism for LDAP URLs, so that future
> documents can extend their functionality, for example, to provide
> access to new LDAPv3 extensions as they are defined.
s/their/the/ (extensions extend the base functionality)
Actually, rewriting the sentence as follows may be appropriate.
This document also defines an extension mechanism for LDAP URLs.
This mechanism may be used to provide access to new LDAP
extensions.
I suggest inserting a paragraph break here.
> Note: not all
^
Remove extra space. I also suggest s/Note:/Note that/.
> of the parameters of the LDAP search operation described in
> [Protocol] can be expressed using the format defined in this
> document.
It maybe appropriate to add the following to this paragraph:
Note also that URLs may be used to represent reference
knowledge, including for non-search operations.
> This document is an integral part of the LDAP Technical Specification
> [Roadmap].
>
> This document replaces RFC 2255. See Appendix A for a list of changes
> relative to RFC 2255.
>
> The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
> document are to be interpreted as described in BCP 14 [RFC2119].
>
>2. URL Definition
>
> An LDAP URL begins with the protocol prefix "ldap" and is defined by
> the following grammar, following the ABNF notation defined in
> [RFC2234].
>
> ldapurl = scheme COLON SLASH SLASH [hostport] [SLASH dn
> [QUESTION [attributes] [QUESTION [scope]
> [QUESTION [filter] [QUESTION extensions]]]]]
> scheme = "ldap"
> 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]>
> ; See the "Escaping Using the % Method"
> ; section below.
> attributes = attrdesc *(COMMA attrdesc)
> attrdesc = <AttributeDescription
> from Section 4.1.4 of [Protocol]>
> / ASTERISK
> ; See the "Escaping Using the % Method"
> ; section below.
This should be:
attributes = selector *(COMMA selector)
selector = <attributeSelector from Section 4.1.4 of [Protocol]>
; See the "Escaping Using the % Method"
; section below.
> scope = "base" / "one" / "sub"
> filter = <filter from Section 4 of [Filters]>
> ; See the "Escaping Using the % Method"
> ; section below.
> extensions = extension *(COMMA extension)
> extension = [EXCLAMATION] extype [EQUALS exvalue]
> extype = oid / oiddescr
This should just be:
extype = <oid from section 1.4 of [Models]>
> 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]>
> oiddescr = <name from section 3.3 of [LDAPIANA]>
With the above change, <oid> and <oiddescr> rules here can
be deleted.
>
> EXCLAMATION = %x21 ; exclamation mark ("!")
> ASTERISK = %x2A ; asterisk ("*")
Can be dropped if the above changes are implemented.
> SLASH = %x2F ; forward slash ("/")
> COLON = %x3A ; colon (":")
> QUESTION = %x3F ; question mark ("?")
>
>
I suggest wrapping all ABNF rule names appearing in the prose
using <>.
> The "ldap" prefix indicates an entry or entries accessible from the
> LDAP 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
> described in [LDAPDN]. It identifies the base object of the LDAP
> search or the target of a non-search operation.
>
> The attributes construct is used to indicate which attributes should
> be returned from the entry or entries. Individual attrdesc names are
> as defined for AttributeDescription in [Protocol].
>
> The scope construct is used to specify the scope of the search to
> perform in the given LDAP server. The allowable scopes are "base"
> for a base object search, "one" for a one-level search, or "sub" for
> a subtree search.
>
> The filter is used to specify the search filter to apply to entries
> within the specified scope during the search. It has the format
> specified in [Filters].
>
> The extensions construct provides the LDAP URL with an extensibility
> mechanism, allowing the capabilities of the URL to be extended in the
> future. Extensions are a simple comma-separated list of type=value
> pairs, where the =value portion MAY be omitted for options not
> requiring it. Each type=value pair is a separate extension. These
> LDAP URL extensions are not necessarily related to any of the LDAPv3
> extension mechanisms. Extensions may be supported or unsupported by
> the client resolving the URL. An extension prefixed with a '!'
> character (ASCII 0x21) is critical. An extension not prefixed with a
> '!' character is non-critical.
>
> If an LDAP URL extension is implemented (that is, if the
> implementation understands it and is able to use it), the
> implementation MUST make use of it. If an extension is not
> implemented and is marked critical, the implementation MUST NOT
> process the URL. If an extension is not implemented and it not
> marked critical, the implementation MUST ignore the extension.
>
> The extension type (extype) MAY be specified using the oid form
s/oid/numeric OID <numericoid> form/ (likewise below)
> (e.g., 1.2.3.4) or the oiddesc form (e.g., myLDAPURLExtension). Use
s/oiddesc/descriptor <descr> form/ (likewise below)
s/./ of the <oid> production [Models]./
> of the oiddesc form SHOULD be restricted to registered object
> identifier descriptive names. See [LDAPIANA] for registration
> details and usage guidelines for descriptive names.
>
> No LDAP URL extensions are defined in this document. Other documents
> or a future version of this document MAY define one or more
> extensions.
>
>2.1. Escaping Using the % Method
>
> A generated LDAP URL MUST consist only of the restricted set of
> characters included in the uric production that is defined in section
> 2 of [RFC2396]. Implementations SHOULD accept other valid UTF-8
> strings [RFC3629] as input. An octet MUST be escaped using the %
> 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
> [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.
>
> Note that before the % method of escaping is applied, the extensions
> component of the LDAP URL may contain one or more null (zero) bytes.
> No other component may.
>
>3. Defaults for Fields of the LDAP URL
>
> Some fields of the LDAP URL are optional, as described above. In the
> absence of any other specification, the following general defaults
> SHOULD be used when a field is absent. Note: other documents MAY
> specify different defaulting rules; for example, section 4.1.10 of
> [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
> referral.
>
> hostport
> The default LDAP port is TCP port 389. If no hostport is given,
> the client must have some apriori knowledge of an appropriate LDAP
> server to contact.
>
> dn
> If no dn is given, the default is the zero-length DN, "".
>
> attributes
> If the attributes part is omitted, all user attributes of the
> entry or entries should be requested (e.g., by setting the
> attributes field AttributeDescriptionList in the LDAP search
> request to a NULL list, or (in LDAPv3) by requesting the special
> attribute name "*").
>
>
>
>
>
> scope
> If scope is omitted, a scope of "base" is assumed.
>
> filter
> If filter is omitted, a filter of "(objectClass=*)" is assumed.
>
> extensions
> If extensions is omitted, no extensions are assumed.
>
>
>4. Examples
>
> The following are some example LDAP URLs using the format defined
> above. The first example is an LDAP URL referring to the University
> of Michigan entry, available from an LDAP server of the client's
> choosing:
>
> ldap:///o=University%20of%20Michigan,c=US
>
> The next example is an LDAP URL referring to the University of
> Michigan entry in a particular ldap server:
>
> ldap://ldap1.example.net/o=University%20of%20Michigan,c=US
>
> Both of these URLs correspond to a base object search of the
> "o=University of Michigan,c=US" entry using a filter of
> "(objectclass=*)", requesting all attributes.
>
> The next example is an LDAP URL referring to only the postalAddress
> attribute of the University of Michigan entry:
>
> ldap://ldap1.example.net/o=University%20of%20Michigan,
> c=US?postalAddress
>
> The corresponding LDAP search operation is the same as in the
> previous example, except that only the postalAddress attribute is
> requested.
>
> The next example is an LDAP URL referring to the set of entries found
> by querying the given LDAP server on port 6666 and doing a subtree
> search of the University of Michigan for any entry with a common name
> of "Babs Jensen", retrieving all attributes:
>
> ldap://ldap1.example.net:6666/o=University%20of%20Michigan,
> c=US??sub?(cn=Babs%20Jensen)
>
> The next example is an LDAP URL referring to all children of the c=GB
> entry:
>
>
>
>
>
> ldap://ldap1.example.com/c=GB?objectClass?one
Please s/ldap:/LDAP:/ and s/one/ONE/ to demonstrate case insensitive.
> The objectClass attribute is requested to be returned along with the
> entries, and the default filter of "(objectclass=*)" is used.
>
> 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 use of the escaping mechanism on the reserved character '?'.
>
> ldap://ldap2.example.com/o=Question%3f,c=US?mail
>
> The next example (which is broken into two lines for readability)
> illustrates the interaction between the LDAP string representation of
> filters quoting mechanism and URL quoting mechanisms.
>
> ldap://ldap3.example.com/o=Babsco,c=US
> ???(four-octet=%5c00%5c00%5c00%5c04)
>
> 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
> would be written as (four-octet=\00\00\00\04). Because the \
> character must be escaped in a URL, the \'s are escaped as %5c in the
> URL encoding.
s/%5c/%5c (or %5C)/
I suggest that you use uppercase hex values in a subsequent
example.
> 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
> defaulting rules specified in section 4 of this document are used:
>
> 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
> server.
>
>The final two examples show use of a hypothetical, experimental bind
>name extension (the value associated with the extension is an LDAP DN).
>
> ldap:///??sub??e-bindname=cn=Manager%2cdc=example%2cdc=com
> ldap:///??sub??!e-bindname=cn=Manager%2cdc=example%2cdc=com
>
> The two URLs are the same, except that the second one marks the
> e-bindname extension as critical. Notice the use of the % encoding
> method to encode the commas within the distinguished name value in
> the e-bindname extension.
>
>
>5. Security Considerations
>
> General URL security considerations discussed in [RFC2396] are
> relevant for LDAP URLs.
>
> The use of security mechanisms when processing LDAP URLs requires
> particular care, since clients may encounter many different servers
> via URLs, and since URLs are likely to be processed automatically,
> without user intervention. A client SHOULD have a user-configurable
> policy about which servers to connect to using which security
> mechanisms, and SHOULD NOT make connections that are inconsistent
> with this policy. If a client chooses to reuse an existing
> connection when resolving one or more LDAP URL, it MUST ensure that
> the connection is compatible with the URL and that no security
> policies are violated.
>
> Sending authentication information, no matter the mechanism, may
> violate a user's privacy requirements. In the absence of specific
> policy permitting authentication information to be sent to a server,
> a client should use an anonymous connection. (Note that clients
> conforming to previous LDAP URL specifications, where all connections
> are anonymous and unprotected, are consistent with this
> specification; they simply have the default security policy.) Simply
> opening a connection to another server may violate some users'
> privacy requirements, so clients should provide the user with a way
> to control URL processing.
>
> Some authentication methods, in particular reusable passwords sent to
> the server, may reveal easily-abused information to the remote server
> or to eavesdroppers in transit, and should not be used in URL
> processing unless explicitly permitted by policy. Confirmation by
> the human user of the use of authentication information is
> appropriate in many circumstances. Use of strong authentication
> methods that do not reveal sensitive information is much preferred.
> If the URL represents a referral for an update operation, strong
> authentication methods SHOULD be used. Please refer to the Security
> Considerations section of [AuthMeth] for more information.
>
> The LDAP URL format allows the specification of an arbitrary LDAP
> search operation to be performed when evaluating the LDAP URL.
> Following an LDAP URL may cause unexpected results, for example, the
> retrieval of large amounts of data, the initiation of a long-lived
> search, etc. The security implications of resolving an LDAP URL are
> the same as those of resolving an LDAP search query.
>
>6. IANA Considerations
>
> This document has no actions for IANA.
>
>7. Normative References
>
>[AuthMeth] Harrison, R. (editor), "LDAP: Authentication Methods",
> draft-ietf-ldapbis-authmeth-xx.txt, a work in progress. a
> work in progress.
>
>[LDAPDN] Zeilenga, K. (editor), "LDAP: String Representation of
> Distinguished Names", draft-ietf-ldapbis-dn-xx.txt, a work
> in progress.
>
>[Filters] Smith, M. and Howes, T., "LDAP: String Representation of
> Search Filters", draft-ietf-ldapbis-filter-xx.txt, a work in
> progress.
>
>[LDAPIANA] Zeilenga, K., "IANA Considerations for LDAP",
> draft-ietf-ldapbis-bcp64-xx.txt, a work in progress.
With above changes, can be informative.
>
>[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-ietf-ldapbis-protocol-xx.txt, a work in progress.
>
>[RFC2234] Crocker, D., Overell, P., "Augmented BNF for Syntax
> Specifications: ABNF", RFC 2234, November 1997.
>
>[RFC2396] Berners-Lee, T., Fielding, R., and Masinter, L., "Uniform
> 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.
>
>[Roadmap] K. Zeilenga (editor), "LDAP: Technical Specification Road
> Map", draft-ietf-ldapbis-roadmap-xx.txt, a work in progress.
>
>[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646",
> RFC 3629, November 2003.
>
>8. Informative References
>
> None.
>
>9. 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.
>
>10. 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.
>
>
>
>
>
>
>
>11. Authors' Addresses
>
> Mark Smith, Editor
> Pearl Crescent, LLC
> 447 Marlpool Dr.
> Saline, MI 48176
> USA
> +1 734 944-2856
> mcs@pearlcrescent.com
>
> Tim Howes
> Opsware, Inc.
> 599 N. Mathilda Ave.
> Sunnyvale, CA 94085
> USA
> +1 408 744-7509
> howes@opsware.com
>
>12. Appendix A: Changes Since RFC 2255
>
>12.1. Technical Changes
>
> The following technical changes were made to the contents of the "URL
> Definition" section:
>
> Revised all of the ABNF to use common productions from [Models].
>
> Added note and references to [RFC2732] to allow literal IPv6
> addresses inside the hostport portion of the URL.
>
> Added missing ASTERISK as an alternative for the attrdesc part of the
> 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.
>
>
>12.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.
>
> "Table of Contents" and "IANA Considerations" sections: added.
>
> "Introduction" section: new section; separated from the Abstract.
> Changed the text indicate that RFC 2255 is replaced by this document
> (instead of RFC 1959). Added text to indicate that LDAP URLs are
> used for references and referrals. Fixed typo (replaced the nonsense
> 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
> LDAP search operation described in [Protocol] can be expressed using
> this format.
>
> "URL Definition" section: removed second copy of ldapurl grammar and
> following two paragraphs (editorial error in RFC 2255). Fixed line
> break within '!' sequence. Replaced "residing in the LDAP server"
> with "accessible from the LDAP server" in the sentence immediately
> following the ABNF. Reworded last paragraph to clarify which
> characters must be URL escaped. Added text to indicate that LDAP
> URLs are used for references and referrals. Added text that refers
> to the ABNF from RFC 2234. Clarified and strengthened the
> requirements with respect to processing of URLs that contain
> implements and not implemented extensions (the approach now closely
> matches that specified in [Protocol] for LDAP controls).
>
> "Defaults for Fields of the LDAP URL" section: added; formed by
> moving text about defaults out of the "URL Definition" section.
>
> "URL Processing" section: clarified that connections MAY be reused
> only if the open connection is compatible with the URL. Added text
> to indicate that use of security services is encouraged and that they
> SHOULD be used when updates are involved. Removed "dn" from
> discussion of authentication methods. Added note that the client MAY
> interrogate the server to determine the most appropriate method.
>
>
>
>
>
>
> "Examples" section: Modified examples to use example.com and
> example.net hostnames. Added missing '?' to the LDAP URL example
> whose filter contains three null bytes. Removed space after one
> comma within a DN. Revised the bindname example to use e-bindname.
> Changed the name of an attribute used in one example from "int" to
> "four-octet" to avoid potential confusion. Added an example that
> 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
> reuse. Added a note about using strong authentication methods for
> updates. Added a reference to [AuthMeth]. Added note that simply
> opening a connection may violate some users' privacy requirements.
>
> "Acknowledgements" section: added statement about this being an
> update to RFC 2255. Added Kurt Zeilenga, Jim Sermersheim, and
> Hallvard Furuseth.
>
> "Normative References" section: renamed from "References" per new RFC
> guidelines. Changed from [1] style to [Protocol] style throughout the
> document. Added references to RFC 2234, RFC 2732, and RFC 3629.
> Updated all RFC 1738 references to point to the appropriate sections
> within RFC 2396. Updated the LDAP references to refer to LDAPBis WG
> documents. Removed the reference to the LDAP Attribute Syntaxes
> document and added references to the [AuthMeth], [LDAPIANA], and
> [Roadmap] documents.
>
> "Informative References" section: added for clarity.
>
> Header and "Authors' Addresses" sections: added "editor" next to Mark
> Smith's name. Updated affiliation and contact information.
>
> Copyright: updated the year.
>
>
>13. Appendix B: Changes Since Previous Document Revision
>
> This appendix lists all changes relative to the previously published
> revision, draft-ietf-ldapbis-url-06.txt. Note that when appropriate
> these changes are also included in Appendix A, but are also included
> here for the benefit of the people who have already reviewed
> draft-ietf-ldapbis-url-06.txt. This section will be removed before
> this document is published as an RFC.
>
>
>
>
>
>
>
>
>
>13.1. Editorial Changes
>
> "Status of this Memo" section: replaced RFC 3668 (IPR) boilerplate
> paragraph with the version that says "each author" instead of "I."
>
> "URL Definition" section: replaced phrases such as "recognized by"
> with "implemented by" when referring to LDAP URL extensions.
>
> "URL Definition" section: added the following two sentences at the
> end of the subsection on "Escaping Using the % Method":
> Note that before the % method of escaping is applied, the
> extensions component of the LDAP URL may contain one or more null
> (zero) bytes. No other component may.
>
>14. Intellectual Property Rights
>
> The IETF takes no position regarding the validity or scope of any
> Intellectual Property Rights 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; nor does it represent that it has
> made any independent effort to identify any such rights. Information
> on the procedures with respect to rights in RFC documents can be
> found in BCP 78 and BCP 79.
>
> Copies of IPR disclosures made to the IETF Secretariat 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 implementers or users of this
> specification can be obtained from the IETF on-line IPR repository at
> http://www.ietf.org/ipr.
>
> The IETF invites any interested party to bring to its attention any
> copyrights, patents or patent applications, or other proprietary
> rights that may cover technology that may be required to implement
> this standard. Please address the information to the IETF at
> ietf-ipr@ietf.org.
>
>15. Full Copyright
>
> Copyright (C) The Internet Society (2004). This document is subject
> to the rights, licenses and restrictions contained in BCP 78, and
> except as set forth therein, the authors retain all their rights.
>
> This document and the information contained herein are provided on an
> "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
> OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
> ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
>
>
>
>
>
> INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
> INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
> WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
>
>This Internet Draft expires on 24 April 2005.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>