draft-ietf-ldapbis-filter-08.txt   draft-ietf-ldapbis-filter-09.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: 24 April 2005 Opsware, Inc. Expires: 16 May 2005 Opsware, Inc.
24 October 2004 16 November 2004
LDAP: String Representation of Search Filters LDAP: String Representation of Search Filters
<draft-ietf-ldapbis-filter-08.txt> <draft-ietf-ldapbis-filter-09.txt>
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 have been or will be disclosed, and any of which he or she become
aware will be disclosed, in accordance with RFC 3668. aware will be disclosed, in accordance with RFC 3668.
This document is intended to be published as a Standards Track RFC, This document is intended to be published as a Standards Track RFC,
replacing RFC 2254. Distribution of this memo is unlimited. replacing RFC 2254. Distribution of this memo is unlimited.
skipping to change at page 2, line 10 skipping to change at page 2, line 10
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 Please see the Full Copyright section near the end of this document
for more information. for more information.
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 [LDAPURL] and
applications. in other applications.
Table of Contents Table of Contents
Status of this Memo............................................1 Status of this Memo............................................1
Abstract.......................................................2 Abstract.......................................................2
Table of Contents..............................................2 Table of Contents..............................................2
1. Introduction...................................................2 1. Introduction...................................................2
2. LDAP Search Filter Definition..................................3 2. LDAP Search Filter Definition..................................3
3. String Search Filter Definition................................4 3. String Search Filter Definition................................4
4. Examples.......................................................6 4. Examples.......................................................6
5. Security Considerations........................................7 5. Security Considerations........................................7
6. IANA Considerations............................................7 6. IANA Considerations............................................7
7. Normative References...........................................7 7. Normative References...........................................7
8. Informative References.........................................8 8. Informative References.........................................8
9. Acknowledgments................................................8 9. Acknowledgments................................................8
10. Authors' Addresses.............................................8 10. Authors' Addresses.............................................9
11. Appendix A: Changes Since RFC 2254.............................9 11. Appendix A: Changes Since RFC 2254.............................9
11.1. Technical Changes...........................................9 11.1. Technical Changes...........................................9
11.2. Editorial Changes...........................................10 11.2. Editorial Changes...........................................10
12. Appendix B: Changes Since Previous Document Revision...........11 12. Appendix B: Changes Since Previous Document Revision...........11
12.1. Editorial Changes...........................................11 12.1. Technical Changes...........................................11
13. Intellectual Property Rights...................................11 12.2. Editorial Changes...........................................12
14. Full Copyright.................................................12 Intellectual Property Rights...................................12
Full Copyright.................................................13
1. Introduction 1. Introduction
The Lightweight Directory Access Protocol (LDAP) [Protocol] defines a The Lightweight Directory Access Protocol (LDAP) [Roadmap] 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 Specification This document is a integral part of the LDAP technical specification
[Roadmap]. [Roadmap] which obsoletes the previously defined LDAP technical
specification, RFC 3377, in its entirety.
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].
2. LDAP Search Filter Definition 2. LDAP Search Filter Definition
An LDAPv3 search filter is defined in Section 4.5.1 of [Protocol] as An LDAP 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,
greaterOrEqual [5] AttributeValueAssertion, greaterOrEqual [5] AttributeValueAssertion,
lessOrEqual [6] AttributeValueAssertion, lessOrEqual [6] AttributeValueAssertion,
skipping to change at page 3, line 49 skipping to change at page 4, line 4
matchingRule [1] MatchingRuleId OPTIONAL, matchingRule [1] MatchingRuleId OPTIONAL,
type [2] AttributeDescription OPTIONAL, type [2] AttributeDescription OPTIONAL,
matchValue [3] AssertionValue, matchValue [3] AssertionValue,
dnAttributes [4] BOOLEAN DEFAULT FALSE } dnAttributes [4] BOOLEAN DEFAULT FALSE }
AttributeDescription ::= LDAPString AttributeDescription ::= LDAPString
-- 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,
-- [Unicode] characters -- [Unicode] characters
The AttributeDescription is a string representation of the attribute The AttributeDescription, as defined in [Protocol], is a string
description and is defined in [Protocol]. The AttributeValue and representation of the attribute description that is discussed in
AssertionValue OCTET STRING have the form defined in [Syntaxes]. The [Models]. The AttributeValue and AssertionValue OCTET STRING have
Filter is encoded for transmission over a network using the Basic the form defined in [Syntaxes]. The Filter is encoded for
Encoding Rules (BER) defined in [X.690], with simplifications transmission over a network using the Basic Encoding Rules (BER)
described in [Protocol]. defined in [X.690], with simplifications described in [Protocol].
3. 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 Unicode characters [Unicode] that is defined UTF-8 [RFC3629] encoded Unicode characters [Unicode] that is defined
by the following grammar, following the ABNF notation defined in by the following grammar, following the ABNF notation defined in
[RFC2234]. The productions used that are not defined here are [RFC2234]. The productions used that are not defined here are
defined in section 1.4 (Common ABNF Productions) of [Models] unless defined in section 1.4 (Common ABNF Productions) of [Models] unless
otherwise noted. The filter format uses a prefix notation. otherwise noted. The filter format uses a prefix notation.
skipping to change at page 4, line 36 skipping to change at page 4, line 40
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 / greaterorequal / lessorequal filtertype = equal / approx / greaterorequal / lessorequal
equal = EQUALS equal = EQUALS
approx = TILDE EQUALS approx = TILDE EQUALS
greaterorequal = RANGLE EQUALS greaterorequal = RANGLE EQUALS
lessorequal = LANGLE EQUALS lessorequal = LANGLE EQUALS
extensible = attr [dnattrs] extensible = ( attr [dnattrs]
[matchingrule] COLON EQUALS assertionvalue [matchingrule] COLON EQUALS assertionvalue )
/ [dnattrs] / ( [dnattrs]
matchingrule COLON EQUALS assertionvalue matchingrule 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 <AssertionValue> ; The <valueencoding> rule is used to encode an <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,
skipping to change at page 5, line 38 skipping to change at page 5, line 42
representing the value of the encoded octet. representing the value of the encoded octet.
This simple escaping mechanism eliminates filter-parsing ambiguities This simple escaping mechanism eliminates filter-parsing ambiguities
and allows any filter that can be represented in LDAP to be and allows any filter that can be represented in LDAP to be
represented as a NUL-terminated string. Other octets that are part of represented as a NUL-terminated string. Other octets that are part of
the <normal> set may be escaped using this mechanism, for example, the <normal> set may be escaped using this mechanism, for example,
non-printing ASCII characters. non-printing ASCII characters.
For AssertionValues that contain UTF-8 character data, each octet of For AssertionValues that contain UTF-8 character data, each octet of
the character to be escaped is replaced by a backslash and two hex the character to be escaped is replaced by a backslash and two hex
digits, which form a single octet in the code of the character. digits, which form a single octet in the code of the character. For
example, the filter checking whether the "cn" attribute contained a
For example, the filter checking whether the "cn" attribute contained 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 Unicode characters). search filter is a string of UTF-8 encoded Unicode characters).
4. Examples 4. Examples
skipping to change at page 6, line 19 skipping to change at page 6, line 21
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=)
The following examples illustrate the use of extensible matching. The following examples illustrate the use of extensible matching.
(cn:1.2.3.4.5:=Fred Flintstone) (cn:caseExactMatch:=Fred Flintstone)
(cn:=Betty Rubble) (cn:=Betty Rubble)
(sn:dn:2.4.6.8.10:=Barney Rubble) (sn:dn:2.4.6.8.10:=Barney Rubble)
(o:dn:=Ace Industry) (o:dn:=Ace Industry)
(:1.2.3:=Wilma Flintstone) (:1.2.3:=Wilma Flintstone)
(:dn:2.4.6.8.10:=Dino) (:DN:2.4.6.8.10:=Dino)
The first example shows use of the matching rule "1.2.3.4.5". The first example shows use of the matching rule "caseExactMatch."
The second example demonstrates use of a MatchingRuleAssertion form The second example demonstrates use of a MatchingRuleAssertion form
without a matchingRule. without a matchingRule.
The third example illustrates the use of the ":oid" notation to The third example illustrates the use of the ":oid" notation to
indicate that matching rule "2.4.6.8.10" should be used when making indicate that matching rule identified by the OID "2.4.6.8.10" should
comparisons, and that the attributes of an entry's distinguished name be used when making comparisons, and that the attributes of an
should be considered part of the entry when evaluating the match entry's distinguished name should be considered part of the entry
(indicated by the use of ":dn"). when evaluating the match (indicated by the use of ":dn").
The fourth example denotes an equality match, except that DN The fourth example denotes an equality match, except that DN
components should be considered part of the entry when doing the components should be considered part of the entry when doing the
match. match.
The fifth example is a filter that should be applied to any attribute The fifth example is a filter that should be applied to any attribute
supporting the matching rule given (since the attr has been omitted). supporting the matching rule given (since the <attr> has been
omitted).
The sixth and final example is also a filter that should be applied The sixth and final example is also a filter that should be applied
to any attribute supporting the matching rule given. Attributes to any attribute supporting the matching rule given. Attributes
supporting the matching rule contained in the DN should also be supporting the matching rule contained in the DN should also be
considered. considered.
The following examples illustrate the use of the escaping mechanism. The following examples illustrate the use of the escaping mechanism.
(o=Parens R Us \28for all your parenthetical needs\29) (o=Parens R Us \28for all your parenthetical needs\29)
(cn=*\2A*) (cn=*\2A*)
skipping to change at page 7, line 16 skipping to change at page 7, line 20
(bin=\00\00\00\04) (bin=\00\00\00\04)
(sn=Lu\c4\8di\c4\87) (sn=Lu\c4\8di\c4\87)
(1.3.6.1.4.1.1466.0=\04\02\48\69) (1.3.6.1.4.1.1466.0=\04\02\48\69)
The first example shows the use of the escaping mechanism to The first example shows the use of the escaping mechanism to
represent parenthesis characters. The second shows how to represent a represent parenthesis characters. The second shows how to represent a
"*" in an assertion value, preventing it from being interpreted as a "*" in an assertion value, preventing it from being interpreted as a
substring indicator. The third illustrates the escaping of the substring indicator. The third illustrates the escaping of the
backslash character. backslash character.
The fourth example shows a filter searching for the four-byte value The fourth example shows a filter searching for the four octet value
0x00000004, illustrating the use of the escaping mechanism to 00 00 00 04 (hex), 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. Specifically, there are
5 characters in the <assertionvalue> portion of this example: LATIN
CAPITAL LETTER L (U+004C), LATIN SMALL LETTER U (U+0075), LATIN SMALL
LETTER C WITH CARON (U+010D), LATIN SMALL LETTER I (U+0069), and
LATIN SMALL LETTER C WITH ACUTE (U+0107).
The sixth and final example demonstrates assertion of a BER encoded The sixth and final example demonstrates assertion of a BER encoded
value. value.
5. 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
skipping to change at page 8, line 27 skipping to change at page 8, line 33
[Syntaxes] Dally, K. (editor), "LDAP: Syntaxes", [Syntaxes] Dally, K. (editor), "LDAP: Syntaxes",
draft-ietf-ldapbis-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 [Unicode] The Unicode Consortium, "The Unicode Standard, Version
3.2.0" is defined by "The Unicode Standard, Version 3.0" 3.2.0" is defined by "The Unicode Standard, Version 3.0"
(Reading, MA, Addison-Wesley, 2000. ISBN 0-201-61633-5), as (Reading, MA, Addison-Wesley, 2000. ISBN 0-201-61633-5), as
amended by the "Unicode Standard Annex #27: Unicode 3.1" amended by the "Unicode Standard Annex #27: Unicode 3.1"
(http://www.unicode.org/reports/tr27/) and by the "Unicode (http://www.unicode.org/reports/tr27/) and by the "Unicode
Standard Annex #28: Unicode 3.2." Standard Annex #28: Unicode 3.2."
8. Informative References
[LDAPURL] Smith, M. (editor), "LDAP: Uniform Resource Locator",
draft-ietf-ldapbis-url-xx.txt, a work in progress.
[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.
8. Informative References
None.
9. Acknowledgments 9. Acknowledgments
This document replaces RFC 2254 by Tim Howes. Changes included in This document replaces RFC 2254 by Tim Howes. RFC 2254 was a product
this revised specification are based upon discussions among the of the IETF ASID Working Group.
authors, discussions within the LDAP (v3) Revision Working Group
(ldapbis), and discussions within other IETF Working Groups. The Changes included in this revised specification are based upon
contributions of individuals in these working groups is gratefully discussions among the authors, discussions within the LDAP (v3)
acknowledged. Revision Working Group (ldapbis), and discussions within other IETF
Working Groups. The contributions of individuals in these working
groups is gratefully acknowledged.
10. 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
skipping to change at page 9, line 32 skipping to change at page 9, line 41
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 Unicode 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].
Added "(" and ")" around the components of the <extensible>
subproductions for clarity.
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 "String Search Filter Definition" section: replaced "greater" and
"less" with "greaterorequal" and "lessorequal" to avoid confusion. "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
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."
11.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.
skipping to change at page 10, line 27 skipping to change at page 10, line 34
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.
"LDAP Search Filter Definition" section: made corrections to the "LDAP Search Filter Definition" section: made corrections to the LDAP
LDAPv3 search filter ABNF so it matches that used in [Protocol]. search filter ABNF so it matches that used in [Protocol].
Clarified the definition of 'value' (now 'assertionvalue') to take Clarified the definition of 'value' (now 'assertionvalue') to take
into account the fact that it is not precisely an AttributeAssertion into account the fact that it is not precisely an AttributeAssertion
from [Protocol] section 4.1.6 (special handling is required for some from [Protocol] section 4.1.6 (special handling is required for some
characters). Added a note that each octet of a character to be characters). Added a note that each octet of a character to be
escaped is replaced by a backslash and two hex digits, which escaped is replaced by a backslash and two hex digits, which
represent a single octet. represent a single octet.
"Examples" section: added four additional examples: (seeAlso=), "Examples" section: added four additional examples: (seeAlso=),
(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). Replaced the numeric OID
in the first extensible match example with "caseExactMatch" to
demonstrate use of the descriptive form. Used "DN" (uppercase) in
the last extensible match example to remind the reader to treat the
<dnattrs> production as case insensitive. Reworded the description
of the fourth escaping mechanism example to avoid making assumptions
about byte order. Added text to the fifth escaping mechanism example
to spell out what the non-ASCII characters are in Unicode terms.
"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 [Unicode], [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: (new section) moved [X.690] to this
section. Added a reference to [LDAPURL].
"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.
Surrounded the names of all ABNF productions with "<" and ">" where
they are used in descriptive text.
Replaced all occurrences of "LDAPv3" with "LDAP."
12. 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-07.txt. Note that when revision, draft-ietf-ldapbis-filter-08.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-07.txt. This section will be reviewed draft-ietf-ldapbis-filter-08.txt. This section will be
removed before this document is published as an RFC. removed before this document is published as an RFC.
12.1. Editorial Changes 12.1. Technical Changes
"Status of this Memo" section: replaced RFC 3668 (IPR) boilerplate Removed the third option from the "extensible" production that
paragraph with the version that says "each author" instead of "I." allowed creation of a MatchingRuleAssertion that only had a
matchValue (disallowed By [Protocol]). Added "(" and ")" around the
components of the <extensible> subproductions for clarity.
"Status of this Memo" section: added 2 paragraphs that were 12.2. Editorial Changes
accidently removed from the -07 revision (one begins with "The list
of current Internet-Drafts..." and the other begins with "The list of
Internet-Draft Shadow Directories...."
13. Intellectual Property Rights "Introduction" section: referenced [Roadmap] upon first use of LDAP
and expanded the paragraph that begins "This document is an integral
part of the LDAP technical specification..." to match the text used
in [Protocol].
"LDAP Search Filter Definition" section: reworded the last paragraph
for clarity.
"Examples" section: Replaced the numeric OID in the first extensible
match example with "caseExactMatch" to demonstrate use of the
descriptive form. Used "DN" (uppercase) in the last extensible match
example to remind the reader to treat the <dnattrs> production as
case insensitive. Reworded the description of the fourth escaping
mechanism example to avoid making assumptions about byte order.
Added text to the fifth escaping mechanism example to spell out what
the non-ASCII characters are in Unicode terms.
References: added [LDAPURL] and moved [X.690] to "Informative
References."
"Acknowledgements" section: added the sentence "RFC 2254 was a
product of the IETF ASID Working Group."
Changed these two sections to unnumbered ones: "Intellectual Property
Rights" and "Full Copyright."
Surrounded the names of all ABNF productions with "<" and ">" where
they are used in descriptive text.
Replaced all occurrences of "LDAPv3" with "LDAP."
Intellectual Property Rights
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights 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 might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 12, line 11 skipping to change at page 13, line 14
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
14. Full Copyright Full Copyright
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2004). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
This Internet Draft expires on 24 April 2005. This Internet Draft expires on 16 May 2005.
 End of changes. 

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