Re: [ldapext] draft-zeilenga-ldap-noop comments

["Kurt D. Zeilenga" <Kurt@OpenLDAP.org>]

At 09:49 AM 12/29/2003, Hallvard B Furuseth wrote:
>What does an operation with the no-op control return if the control
>is not appropriate for the operation?  Is behavior undefined, or
>maybe it returns unavailableCriticalExtension?

That behavior is defined (for all controls) by Section 4.1.12 of
RFC 2251.

>draft-zeilenga-ldap-noop-03.txt says:
>
>> 1.  Overview
>
>>   It is often desirable to be able to determine if a directory [X.500]
>
>I suggest s/X.500/RFC3377/.  The X.500 reference is confusing, since
>the rest of the draft only applies to LDAP directories and not X.500
>directories.

I'll replace this citation with one to [RFC2251] after the next
word, "operation", in the sentence.


>>  This No-Op control is not intended to be to a "effective access"
>>  mechanism [RFC2820, U12].
>
>s/a/an/.
>
>> 2.  No-Op Control
>
>>   A result code of noOperation
>>   (TBD) indicates that the server discovered no reason why the operation
>>   would fail if submitted without the No-Op control.
>
>I don't know what TBD means?

IANA assigned.  I'll replace that with IANA-ASSIGNED-CODE.


>-- 
>Hallvard
>
>_______________________________________________
>Ldapext mailing list
>Ldapext@ietf.org
>https://www1.ietf.org/mailman/listinfo/ldapext


_______________________________________________
Ldapext mailing list
Ldapext@ietf.org
https://www1.ietf.org/mailman/listinfo/ldapext