Re: [MORG] draft-ietf-morg-multimailbox-search-05 - WGLC

[Barry Leiba <[e-mail]>]

Hi, Timo.

>>    S: * ESEARCH (TAG "tag1" MAILBOX "folder1" UIDVALIDITY 1) UID ALL
>>    4001,4003,4005,4007,4009
>>    S: * ESEARCH (TAG "tag2" MAILBOX "folder1" UIDVALIDITY 6789023554)
>>    UID ALL 195001:195004,169788
>
> UIDVALIDITY changes rather suddenly in this example, so I think that's
> just unnecessary confusion. Also the second one's UID set isn't sorted
> as it should be.

The UIDVALIDITY change does seem odd.  Given the UID ranges, it seems
intentional, but a little weird.  Alexey, did you have a particular
reason for including an example like that, without textual
explanation?

The sequence set does not need to be sorted; why do you say "as it
should be"?  According to RFC 3501, sorting it is a "MAY":

sequence-set    = (seq-number / seq-range) *("," sequence-set)
                    ; set of seq-number values, regardless of order.
                    ; Servers MAY coalesce overlaps and/or execute the
                    ; sequence in any order.
                    ; Example: a message sequence number set of
                    ; 2,4:7,9,12:* for a mailbox with 15 messages is
                    ; equivalent to 2,4,5,6,7,9,12,13,14,15
                    ; Example: a message sequence number set of *:4,5:7
                    ; for a mailbox with 10 messages is equivalent to
                    ; 10,9,8,7,6,5,4,5,6,7 and MAY be reordered and
                    ; overlap coalesced to be 4,5,6,7,8,9,10.

I actually think it's good to have an example where they're not
sorted, to make sure it's understood that clients MUST deal with that.

Barry