Last Call Comment: LDAP & X.500 Component Matching Rules toProposed Standard

[Harald Tveit Alvestrand <harald@alvestrand.no>]

Last Call comment on this document:

The document fails to describe how a client can determine whether or not an 
LDAP server implements the componentFilterMatch matching rule.

Since the extension is complex, and presently unsupported, it will likely 
be critical for interoperability (and proper error messages) that a client 
know how to check whether this extension is present or not in a server.
(It's possible, albeit expensive, for a client to have fallback in some 
situations by pulling large sets of objects to the client and doing the 
required matching client-side. Unless he knows whether or not it is 
supported, this becomes more complex.)

It is not clear to this reader whether this should be indicated via 
"supportedControl", "supportedExtension", "supportedLDAPVersion" or some 
other mechanism.

            Harald Alvestrand, speaking as IETF participant


--On onsdag, mai 07, 2003 15:09:29 -0400 The IESG <iesg-secretary@ietf.org> 
wrote:

> The IESG has received a request to consider LDAP & X.500 Component
> Matching Rules <draft-legg-ldapext-component-matching-10.txt> as a
> Proposed Standard.  This has been reviewed in the IETF but is not the
> product of an IETF Working Group.
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action.  Please send any comments to the
> iesg@ietf.org or ietf@ietf.org mailing lists by 2003-6-7.
>
> Files can be obtained via
> http://www.ietf.org/internet-drafts/draft-legg-ldapext-component-matching
> -10.txt