[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: [ldapext] draft-zeilenga-ldap-dontusecopy: criticality
- To: Michael Ströder <michael@stroeder.com>
- Subject: Re: [ldapext] draft-zeilenga-ldap-dontusecopy: criticality
- From: Pierangelo Masarati <ando@sys-net.it>
- Date: Sat, 01 Nov 2008 15:28:38 +0100
- Cc: Ldapext <ldapext@ietf.org>
- Delivered-to: ldapext@core3.amsl.com
- In-reply-to: <49073795.4040604@sys-net.it>
- References: <487FC74A.5050507@stroeder.com> <91C1D771-178D-4EAC-802D-5DCE430B8AA1@Isode.com> <48805FD6.7000407@stroeder.com> <49073795.4040604@sys-net.it>
- User-agent: Thunderbird 2.0.0.17 (X11/20081001)
Pierangelo Masarati wrote:
The main problem is that it's impossible to find out whether a server
supports a certain control (within a particular naming context)
without sending it. (And even if you send it and
unavailableCriticalExtension you cannot really tell if the client sent
several critical controls.)
What about a "whoFailed?" control, whose criticality MUST be FALSE,
which is supposed to result in returning a control whose value is a set
of OIDs of the extensions (exop, control, whatever) that failed? In
most cases, only the first that failed would be returned, but this would
be left to the implementation.
See <http://www.openldap.org/its?findid=5784> and
<http://www.openldap.org/devel/cvsweb.cgi/~checkout~/doc/drafts/draft-masarati-ldap-whatfailed-xx.txt>
(plan to submit it shortly). It's already in OpenLDAP's HEAD code.
p.
_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www.ietf.org/mailman/listinfo/ldapext