draft-ietf-ldapbis-filter-06.txt   draft-ietf-ldapbis-filter-07.txt 
Network Working Group M. Smith, Editor Network Working Group M. Smith, Editor
Request for Comments: DRAFT Pearl Crescent, LLC Request for Comments: DRAFT Pearl Crescent, LLC
Obsoletes: RFC 2254 T. Howes Obsoletes: RFC 2254 T. Howes
Expires: 13 August 2004 Opsware, Inc. Expires: 13 January 2005 Opsware, Inc.
13 February 2004 13 July 2004
LDAP: String Representation of Search Filters LDAP: String Representation of Search Filters
<draft-ietf-ldapbis-filter-06.txt> <draft-ietf-ldapbis-filter-07.txt>
1. Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions This document is intended to be published as a Standard Track RFC,
of Section 10 of RFC2026. replacing RFC 2254. 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>.
By submitting this Internet-Draft, I accept the provisions of Section
4 of RFC 3667. By submitting this Internet-Draft, I certify that any
applicable patent or other IPR claims of which I am aware have been
disclosed, and any of which I become aware will be disclosed, in
accordance with RFC 3668.
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
Drafts. Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than 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
Discussion of this document should take place on the LDAP (v3)
Revision (ldapbis) Working Group mailing list <ietf-
ldapbis@openldap.org>.
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Please see the Full Copyright section near the end of this document
for more information.
2. Abstract Abstract
LDAP search filters are transmitted in the LDAP protocol using a LDAP search filters are transmitted in the LDAP protocol using a
binary representation that is appropriate for use on the network. binary representation that is appropriate for use on the network.
This document defines a human-readable string representation of LDAP This document defines a human-readable string representation of LDAP
search filters that is appropriate for use in LDAP URLs and in other search filters that is appropriate for use in LDAP URLs and in other
applications. applications.
3. Table of Contents Table of Contents
1. Status of this Memo............................................1 Status of this Memo............................................1
2. Abstract.......................................................1 Abstract.......................................................1
3. Table of Contents..............................................2 Table of Contents..............................................2
4. Introduction...................................................2 1. Introduction...................................................2
5. LDAP Search Filter Definition..................................2 2. LDAP Search Filter Definition..................................3
6. String Search Filter Definition................................4 3. String Search Filter Definition................................4
7. Examples.......................................................5 4. Examples.......................................................6
8. Security Considerations........................................7 5. Security Considerations........................................7
9. Normative References...........................................7 6. IANA Considerations............................................7
10. Informative References.........................................8 7. Normative References...........................................7
11. Intellectual Property Rights...................................8 8. Informative References.........................................8
12. Acknowledgments................................................8 9. Acknowledgments................................................8
13. Authors' Addresses.............................................9 10. Authors' Addresses.............................................8
14. Full Copyright Statement.......................................9 11. Appendix A: Changes Since RFC 2254.............................9
15. Appendix A: Changes Since RFC 2254.............................10 11.1. Technical Changes...........................................9
15.1. Technical Changes...........................................10 11.2. Editorial Changes...........................................10
15.2. Editorial Changes...........................................10 12. Appendix B: Changes Since Previous Document Revision...........11
16. Appendix B: Changes Since Previous Document Revision...........11 12.1. Technical Changes...........................................11
16.1. Technical Changes...........................................12 12.2. Editorial Changes...........................................11
16.2. Editorial Changes...........................................12 13. Intellectual Property Rights...................................12
14. Full Copyright.................................................12
4. Introduction 1. Introduction
The Lightweight Directory Access Protocol (LDAP) [Protocol] defines a The Lightweight Directory Access Protocol (LDAP) [Protocol] defines a
network representation of a search filter transmitted to an LDAP network representation of a search filter transmitted to an LDAP
server. Some applications may find it useful to have a common way of server. Some applications may find it useful to have a common way of
representing these search filters in a human-readable form; LDAP URLs representing these search filters in a human-readable form; LDAP URLs
are an example of one such application. This document defines a are an example of one such application. This document defines a
human-readable string format for representing the full range of human-readable string format for representing the full range of
possible LDAP version 3 search filters, including extended match possible LDAP version 3 search filters, including extended match
filters. filters.
This document is an integral part of the LDAP Technical This document is an integral part of the LDAP Technical
Specification [Roadmap]. Specification [Roadmap].
This document replaces RFC 2254. Changes to RFC 2254 are summarized This document replaces RFC 2254. Changes to RFC 2254 are summarized
in Appendix A. in Appendix A.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14 [RFC2119]. document are to be interpreted as described in BCP 14 [RFC2119].
5. LDAP Search Filter Definition 2. LDAP Search Filter Definition
An LDAPv3 search filter is defined in Section 4.5.1 of [Protocol] as An LDAPv3 search filter is defined in Section 4.5.1 of [Protocol] as
follows: follows:
Filter ::= CHOICE { Filter ::= CHOICE {
and [0] SET SIZE (1..MAX) OF filter Filter, and [0] SET SIZE (1..MAX) OF filter Filter,
or [1] SET SIZE (1..MAX) OF filter Filter, or [1] SET SIZE (1..MAX) OF filter Filter,
not [2] Filter, not [2] Filter,
equalityMatch [3] AttributeValueAssertion, equalityMatch [3] AttributeValueAssertion,
substrings [4] SubstringFilter, substrings [4] SubstringFilter,
skipping to change at page 3, line 46 skipping to change at page 3, line 51
-- Constrained to <attributedescription> -- Constrained to <attributedescription>
-- [Models] -- [Models]
AttributeValue ::= OCTET STRING AttributeValue ::= OCTET STRING
MatchingRuleId ::= LDAPString MatchingRuleId ::= LDAPString
AssertionValue ::= OCTET STRING AssertionValue ::= OCTET STRING
LDAPString ::= OCTET STRING -- UTF-8 encoded, LDAPString ::= OCTET STRING -- UTF-8 encoded,
-- [ISO10646] characters -- [Unicode] characters
The AttributeDescription is a string representation of the attribute The AttributeDescription is a string representation of the attribute
description and is defined in [Protocol]. The AttributeValue and description and is defined in [Protocol]. The AttributeValue and
AssertionValue OCTET STRING have the form defined in [Syntaxes]. The AssertionValue OCTET STRING have the form defined in [Syntaxes]. The
Filter is encoded for transmission over a network using the Basic Filter is encoded for transmission over a network using the Basic
Encoding Rules defined in [X.690], with simplifications described in Encoding Rules (BER) defined in [X.690], with simplifications
[Protocol]. described in [Protocol].
6. String Search Filter Definition 3. String Search Filter Definition
The string representation of an LDAP search filter is a string of The string representation of an LDAP search filter is a string of
UTF-8[RFC3629] encoded ISO 10646-1 characters that is defined by the UTF-8 [RFC3629] encoded Unicode characters [Unicode] that is defined
following grammar, following the ABNF notation defined in [RFC2234]. by the following grammar, following the ABNF notation defined in
The productions used that are not defined here are defined in section [RFC2234]. The productions used that are not defined here are
1.4 (Common ABNF Productions) of [Models] unless otherwise noted. defined in section 1.4 (Common ABNF Productions) of [Models] unless
The filter format uses a prefix notation. otherwise noted. The filter format uses a prefix notation.
filter = LPAREN filtercomp RPAREN filter = LPAREN filtercomp RPAREN
filtercomp = and / or / not / item filtercomp = and / or / not / item
and = AMPERSAND filterlist and = AMPERSAND filterlist
or = VERTBAR filterlist or = VERTBAR filterlist
not = EXCLAMATION filter not = EXCLAMATION filter
filterlist = 1*filter filterlist = 1*filter
item = simple / present / substring / extensible item = simple / present / substring / extensible
simple = attr filtertype assertionvalue simple = attr filtertype assertionvalue
filtertype = equal / approx / greater / less filtertype = equal / approx / greaterorequal / lessorequal
equal = EQUALS equal = EQUALS
approx = TILDE EQUALS approx = TILDE EQUALS
greater = RANGLE EQUALS greaterorequal = RANGLE EQUALS
less = LANGLE EQUALS lessorequal = LANGLE EQUALS
extensible = attr [dnattrs] [matchingrule] COLON EQUALS assertionvalue extensible = attr [dnattrs]
/ [dnattrs] matchingrule COLON EQUALS assertionvalue [matchingrule] COLON EQUALS assertionvalue
/ [dnattrs]
matchingrule COLON EQUALS assertionvalue
/ COLON EQUALS assertionvalue / COLON EQUALS assertionvalue
present = attr EQUALS ASTERISK present = attr EQUALS ASTERISK
substring = attr EQUALS [initial] any [final] substring = attr EQUALS [initial] any [final]
initial = assertionvalue initial = assertionvalue
any = ASTERISK *(assertionvalue ASTERISK) any = ASTERISK *(assertionvalue ASTERISK)
final = assertionvalue final = assertionvalue
attr = attributedescription attr = attributedescription
; The attributedescription rule is defined in ; The attributedescription rule is defined in
; Section 2.5 of [Models]. ; Section 2.5 of [Models].
dnattrs = COLON "dn" dnattrs = COLON "dn"
matchingrule = COLON oid matchingrule = COLON oid
assertionvalue = valueencoding assertionvalue = valueencoding
; The <valueencoding> rule is used to encode an ; The <valueencoding> rule is used to encode an <AssertionValue>
; <AssertionValue> from Section 4.1.6 of [Protocol]. ; from Section 4.1.6 of [Protocol].
valueencoding = 0*(normal / escaped) valueencoding = 0*(normal / escaped)
normal = UTF1SUBSET / UTFMB normal = UTF1SUBSET / UTFMB
escaped = ESC HEX HEX escaped = ESC HEX HEX
UTF1SUBSET = %x01-27 / %x2B-5B / %x5D-7F UTF1SUBSET = %x01-27 / %x2B-5B / %x5D-7F
; UTF1SUBSET excludes 0x00 (NUL), LPAREN, ; UTF1SUBSET excludes 0x00 (NUL), LPAREN,
; RPAREN, ASTERISK, and ESC. ; RPAREN, ASTERISK, and ESC.
EXCLAMATION = %x21 ; exclamation mark ("!") EXCLAMATION = %x21 ; exclamation mark ("!")
AMPERSAND = %x26 ; ampersand (or AND symbol) ("&") AMPERSAND = %x26 ; ampersand (or AND symbol) ("&")
ASTERISK = %x2A ; asterisk ("*") ASTERISK = %x2A ; asterisk ("*")
COLON = %x3A ; colon (":") COLON = %x3A ; colon (":")
skipping to change at page 5, line 41 skipping to change at page 5, line 48
a value with the character "*" anywhere in it would be represented as a value with the character "*" anywhere in it would be represented as
"(cn=*\2a*)". "(cn=*\2a*)".
As indicated by the valueencoding rule, implementations MUST escape As indicated by the valueencoding rule, implementations MUST escape
all octets greater than 0x7F that are not part of a valid UTF-8 all octets greater than 0x7F that are not part of a valid UTF-8
encoding sequence when they generate a string representation of a encoding sequence when they generate a string representation of a
search filter. Implementations SHOULD accept as input strings that search filter. Implementations SHOULD accept as input strings that
are not valid UTF-8 strings. This is necessary because RFC 2254 did are not valid UTF-8 strings. This is necessary because RFC 2254 did
not clearly define the term "string representation" (and in not clearly define the term "string representation" (and in
particular did not mention that the string representation of an LDAP particular did not mention that the string representation of an LDAP
search filter is a string of UTF-8 encoded ISO 10646-1 characters). search filter is a string of UTF-8 encoded Unicode characters).
7. Examples 4. Examples
This section gives a few examples of search filters written using This section gives a few examples of search filters written using
this notation. this notation.
(cn=Babs Jensen) (cn=Babs Jensen)
(!(cn=Tim Howes)) (!(cn=Tim Howes))
(&(objectClass=Person)(|(sn=Jensen)(cn=Babs J*))) (&(objectClass=Person)(|(sn=Jensen)(cn=Babs J*)))
(o=univ*of*mich*) (o=univ*of*mich*)
(seeAlso=) (seeAlso=)
skipping to change at page 7, line 16 skipping to change at page 7, line 24
The fourth example shows a filter searching for the four-byte value The fourth example shows a filter searching for the four-byte value
0x00000004, illustrating the use of the escaping mechanism to 0x00000004, illustrating the use of the escaping mechanism to
represent arbitrary data, including NUL characters. represent arbitrary data, including NUL characters.
The fifth example illustrates the use of the escaping mechanism to The fifth example illustrates the use of the escaping mechanism to
represent various non-ASCII UTF-8 characters. represent various non-ASCII UTF-8 characters.
The sixth and final example demonstrates assertion of a BER encoded The sixth and final example demonstrates assertion of a BER encoded
value. value.
8. Security Considerations 5. Security Considerations
This memo describes a string representation of LDAP search filters. This memo describes a string representation of LDAP search filters.
While the representation itself has no known security implications, While the representation itself has no known security implications,
LDAP search filters do. They are interpreted by LDAP servers to LDAP search filters do. They are interpreted by LDAP servers to
select entries from which data is retrieved. LDAP servers should select entries from which data is retrieved. LDAP servers should
take care to protect the data they maintain from unauthorized access. take care to protect the data they maintain from unauthorized access.
Please refer to the Security Considerations sections of [Protocol] Please refer to the Security Considerations sections of [Protocol]
and [AuthMeth] for more information. and [AuthMeth] for more information.
9. Normative References 6. IANA Considerations
[AuthMeth] Harrison, R. (editor), "LDAP: Authentication Methods and This document has no actions for IANA.
Connection Level Security Mechanisms", draft-ietf-ldapbis-
authmeth-xx.txt, a work in progress.
[ISO10646] Universal Multiple-Octet Coded Character Set (UCS) - 7. Normative References
Architecture and Basic Multilingual Plane, ISO/IEC 10646-1,
1993. [AuthMeth] Harrison, R. (editor), "LDAP: Authentication Methods and
Connection Level Security Mechanisms",
draft-ietf-ldapbis-authmeth-xx.txt, a work in progress.
[Models] Zeilenga, K. (editor), "LDAP: Directory Information Models", [Models] Zeilenga, K. (editor), "LDAP: Directory Information Models",
draft-ietf-ldapbis-models-xx.txt, a work in progress. draft-ietf-ldapbis-models-xx.txt, a work in progress.
[Protocol] draft-ietf-ldapbis-protocol-xx.txt, a work in progress. [Protocol] draft-ietf-ldapbis-protocol-xx.txt, a work in progress.
[RFC2119] S. Bradner, "Key words for use in RFCs to Indicate [RFC2119] S. Bradner, "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14 (also RFC 2119), March 1997. Requirement Levels", BCP 14 (also RFC 2119), March 1997.
[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.
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646", [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646",
RFC 3629, November 2003. RFC 3629, November 2003.
[Roadmap] Zeilenga, K. (editor), "LDAP: Technical Specification Road [Roadmap] Zeilenga, K. (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.
[Syntaxes] Dally, K. (editor), "LDAP: Syntaxes", draft-ietf-ldapbis- [Syntaxes] Dally, K. (editor), "LDAP: Syntaxes",
syntaxes-xx.txt, a work in progress. draft-ietf-ldapbis-syntaxes-xx.txt, a work in progress.
[Unicode] The Unicode Consortium, "The Unicode Standard, Version
3.2.0" is defined by "The Unicode Standard, Version 3.0"
(Reading, MA, Addison-Wesley, 2000. ISBN 0-201-61633-5), as
amended by the "Unicode Standard Annex #27: Unicode 3.1"
(http://www.unicode.org/reports/tr27/) and by the "Unicode
Standard Annex #28: Unicode 3.2."
[X.690] Specification of ASN.1 encoding rules: Basic, Canonical, and [X.690] Specification of ASN.1 encoding rules: Basic, Canonical, and
Distinguished Encoding Rules, ITU-T Recommendation X.690, Distinguished Encoding Rules, ITU-T Recommendation X.690,
1994. 1994.
10. Informative References 8. Informative References
None. None.
11. Intellectual Property Rights 9. Acknowledgments
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. Acknowledgments
This document replaces RFC 2254 by Tim Howes. Changes included in This document replaces RFC 2254 by Tim Howes. Changes included in
this revised specification are based upon discussions among the this revised specification are based upon discussions among the
authors, discussions within the LDAP (v3) Revision Working Group authors, discussions within the LDAP (v3) Revision Working Group
(ldapbis), and discussions within other IETF Working Groups. The (ldapbis), and discussions within other IETF Working Groups. The
contributions of individuals in these working groups is gratefully contributions of individuals in these working groups is gratefully
acknowledged. acknowledged.
13. Authors' Addresses 10. Authors' Addresses
Mark Smith, Editor Mark Smith, Editor
Pearl Crescent, LLC Pearl Crescent, LLC
447 Marlpool Dr. 447 Marlpool Dr.
Saline, MI 48176 Saline, MI 48176
USA USA
+1 734 944-2856 +1 734 944-2856
mcs@pearlcrescent.com mcs@pearlcrescent.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
14. Full Copyright Statement 11. Appendix A: Changes Since RFC 2254
Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS 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.
15. Appendix A: Changes Since RFC 2254 11.1. Technical Changes
15.1. Technical Changes Replaced [ISO 10646] reference with [Unicode].
The following technical changes were made to the contents of the The following technical changes were made to the contents of the
"String Search Filter Definition" section: "String Search Filter Definition" section:
Added statement that the string representation is a string of UTF-8 Added statement that the string representation is a string of UTF-8
encoded ISO 10646-1 characters. encoded Unicode characters.
Revised all of the ABNF to use common productions from [Models]. Revised all of the ABNF to use common productions from [Models].
Replaced the "value" rule with a new "assertionvalue" rule within the Replaced the "value" rule with a new "assertionvalue" rule within the
"simple", "extensible", and "substring" ("initial", "any", and "simple", "extensible", and "substring" ("initial", "any", and
"final") rules. This matches a change made in [Syntaxes]. "final") rules. This matches a change made in [Syntaxes].
Revised the "attr", "matchingrule", and "assertionvalue" ABNF to more Revised the "attr", "matchingrule", and "assertionvalue" ABNF to more
precisely reference productions from the [Models] and [Protocol] precisely reference productions from the [Models] and [Protocol]
documents. documents.
"String Search Filter Definition" section: replaced "greater" and
"less" with "greaterorequal" and "lessorequal" to avoid confusion.
Introduced the "valueencoding" and associated "normal" and "escaped" Introduced the "valueencoding" and associated "normal" and "escaped"
rules to reduce the dependence on descriptive text. The "normal" rules to reduce the dependence on descriptive text. The "normal"
production restricts filter strings to valid UTF-8 sequences. production restricts filter strings to valid UTF-8 sequences.
Added a third option to the "extensible" production to allow creation Added a third option to the "extensible" production to allow creation
of a MatchingRuleAssertion that only has a matchValue. of a MatchingRuleAssertion that only has a matchValue.
Added a statement about expected behavior in light of RFC 2254's lack Added a statement about expected behavior in light of RFC 2254's lack
of a clear definition of "string representation." of a clear definition of "string representation."
15.2. Editorial Changes 11.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.
Header and "Authors' Addresses" sections: added Mark Smith as the Header and "Authors' Addresses" sections: added Mark Smith as the
document editor and updated affiliation and contact information. document editor and updated affiliation and contact information.
"Table of Contents" and "Intellectual Property Rights" sections: "Table of Contents", "IANA Considerations", and "Intellectual
added. Property Rights" sections: added.
Copyright: updated per latest IETF guidelines. Copyright: updated per latest IETF guidelines.
"Abstract" section: separated from introductory material. "Abstract" section: separated from introductory material.
"Introduction" section: new section; separated from the Abstract. "Introduction" section: new section; separated from the Abstract.
Updated second paragraph to indicate that RFC 2254 is replaced by Updated second paragraph to indicate that RFC 2254 is replaced by
this document (instead of RFC 1960). Added reference to the [Roadmap] this document (instead of RFC 1960). Added reference to the [Roadmap]
document. document.
skipping to change at page 11, line 31 skipping to change at page 10, line 48
(cn:=Betty Rubble), (:1.2.3:=Wilma Flintstone), and (cn:=Betty Rubble), (:1.2.3:=Wilma Flintstone), and
(1.3.6.1.4.1.1466.0=\04\02\48\69). Replaced one occurrence of "a (1.3.6.1.4.1.1466.0=\04\02\48\69). Replaced one occurrence of "a
value" with "an assertion value". Corrected the description of this value" with "an assertion value". Corrected the description of this
example: (sn:dn:2.4.6.8.10:=Barney Rubble). example: (sn:dn:2.4.6.8.10:=Barney Rubble).
"Security Considerations" section: added references to [Protocol] and "Security Considerations" section: added references to [Protocol] and
[AuthMeth]. [AuthMeth].
"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 entries for [ISO10646], [RFC2119], [AuthMeth], document. Added entries for [Unicode], [RFC2119], [AuthMeth],
[Models], and [Roadmap] and updated the UTF-8 reference. Replaced [Models], and [Roadmap] and updated the UTF-8 reference. Replaced
RFC 822 reference with a reference to RFC 2234. RFC 822 reference with a reference to RFC 2234.
"Informative References" section: added for clarity. "Informative References" section: added for clarity.
"Acknowledgments" section: added. "Acknowledgments" section: added.
"Appendix A: Changes Since RFC 2254" section: added. "Appendix A: Changes Since RFC 2254" section: added.
"Appendix B: Changes Since Previous Document Revision" section: "Appendix B: Changes Since Previous Document Revision" section:
added. added.
16. Appendix B: Changes Since Previous Document Revision 12. Appendix B: Changes Since Previous Document Revision
This appendix lists all changes relative to the previously published This appendix lists all changes relative to the previously published
revision, draft-ietf-ldapbis-filter-05.txt. Note that when revision, draft-ietf-ldapbis-filter-06.txt. Note that when
appropriate these changes are also included in Appendix A, but are appropriate these changes are also included in Appendix A, but are
also included here for the benefit of the people who have already also included here for the benefit of the people who have already
reviewed draft-ietf-ldapbis-filter-05.txt. This section will be reviewed draft-ietf-ldapbis-filter-06.txt. This section will be
removed before this document is published as an RFC. removed before this document is published as an RFC.
16.1. Technical Changes 12.1. Technical Changes
None. Replaced [ISO 10646] reference with [Unicode].
16.2. Editorial Changes "String Search Filter Definition" section: replaced "greater" and
"less" with "greaterorequal" and "lessorequal" to avoid confusion.
Also, broke some long lines into two lines to avoid exceeding the 72
column limit.
"LDAP Search Filter Definition" section: changed the LDAPv3 search 12.2. Editorial Changes
filter ABNF so it matches that used in the latest revision of
[Protocol] and removed the following redundant descriptive text:
"where the LDAPString above is limited to the UTF-8 encoding [UTF-8]
of the ISO 10646 character set [ISO10646]."
"String Search Filter Definition" section: Corrected section "Status of this Memo", "Intellectual Property Rights", and "Full
reference to [Models] and replaced this sentence: "Implementations Copyright" sections: updated to use boilerplate from RFC 3667 and RFC
SHOULD accept as input a string that includes invalid UTF-8 octet 3668.
sequences." with the following: "Implementations SHOULD accept as
input strings that are not valid UTF-8 strings."
"Examples" section: Corrected the description of this example: "Status of this Memo", "Abstract" and "Table of Contents" sections:
(sn:dn:2.4.6.8.10:=Barney Rubble). removed section numbers.
"Normative References" section: changed UTF-8 reference to point to "LDAP Search Filter Definition" section: added (BER) to the last
RFC 3629, replaced [ASN.1] with [X.690] for consistency, and indented sentence.
the reference descriptions to enhance readability.
Authors' Addresses section: New contact information for Mark Smith. "IANA Considerations" section: added.
Updated the copyright year to 2004. 13. Intellectual Property Rights
This Internet Draft expires on 13 August 2004. 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.
14. 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 13 January 2005.
 End of changes. 

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