lcupCookieScheme in draft-ietf-ldup-lcup-02.txt

The lcupCookieScheme attribute type:
  ( OID-TBD NAME 'lcupCookieScheme' EQUALITY objectIdentifierMatch
    SYNTAX 1.3.6.1.4.1.1466.115.121.1.38 NO-USER-MODIFICATION
    USAGE directoryOperation ) 

has a syntax (OID) doesn't match the description in the I-D (OID + DN).
I believe it USAGE likely should be dsaOperation as cookie support
for an entry may differ between copies of the entries (in different
replicas).

Also, I guess I do get why this attribute needs a) be accessible from
entries with the DIT and b) why there needs to a DN component.

Given that there that the server maintain any state on behalf of the
client, why would it matter which supported cookie scheme was used?

And it seems kind of pointless to provide a limited discovery
mechanism (complete subtree only) as to which portions of the
DIT the server might support LCUP upon. Seems it would be far
easier (and quite harmless) just for the client to initiate LCUP
and for the server to return an appropriate error if it cannot
process the request.

Kurt