Subject: Re: [ldapext] VLV: Cc/Ci special cases

From: "Jim Sermersheim" <[email-masked]>
Date: Fri, 01 Nov 2002 18:27:06 -0700

I agree. 

>>> "Kurt D. Zeilenga" <[email-masked]> 09/25/02 10:32PM >>>
>   The following special cases exist when the client is specifying the
>   offset and content count: 
>   - an offset of one and a content count of non-one (Ci = 1, Cc != 1)
>     indicates that the target is the first entry in the list.
>   - equivalent values (Ci = Cc) indicate that the target is the last
>     entry in the list.
>   - a content count of zero, and a non-zero offset (Cc = 0, Ci != 0)
>     means the client has no idea what the content count is, the server
>     MUST use its own content count estimate in place of the client's.

>From this,
	(Ci = 0, Cc = 0) indicates the target is the last entry

but what does (Ci = 0, Cc != 0) indicate?

It may be appropriate to eliminate Ci = 0 as valid.  That is,
change byoffset to:
    byoffset            [0] SEQUENCE {
        offset          INTEGER (1 .. maxInt),
        contentCount    INTEGER (0 .. maxInt) },

Kurt

_______________________________________________
Ldapext mailing list
[email-masked] 
https://www1.ietf.org/mailman/listinfo/ldapext

_______________________________________________
Ldapext mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/ldapext