Re: [imapext] I-D Action: draft-ietf-qresync-rfc5162bis-07.txt

[Alexey Melnikov <[e-mail]>]

On 07/01/2014 12:44, Eliot Lear wrote:
> Hi Alexey,
Hi Eliot,

> Thanks for making these changes.  I'm sorry.  I need one more change. 
> The proto write-up is pretty clear about updates.  It says the following:
>
> > * If publication of this document changes the status of any existing
> >   RFCs, are those RFCs listed on the title page header, and are the
> >   changes listed in the abstract and discussed (explained, not just
> >   mentioned) in the introduction?
>
> I propose the following textual changes to the abstract to sort all of 
> this:
>
> OLD:
>
>     The Conditional Store facility provides a protected update mechanism
>     for message state information -- for example, the mechanism can be
>     used to guarantee that only one client can change message state at
>     any time -- and a mechanism for requesting only changes to message
>     state.
>
>     This document additionally defines another IMAP extension, Quick
>     Resynchronization, which builds on the Conditional Store extension to
>     provide an IMAP client the ability to fully resynchronize a mailbox
>     as part of the SELECT/EXAMINE command, without the need for
>     additional server-side state or client round-trips.
>
>     This document obsoletes RFC 4551 and RFC 5162.  It updates RFC 4315,
>     RFC 3501 and RFC 2683.
>
> New:
>
>
>     Initially defined in RFC 4551, The Conditional Store facility provides
>     a protected update mechanism for message state information and a
>     mechanism for requesting only changes to message state.  This memo
>     updates that mechanism and obsoletes RFC 4551, based on operational
>     experience.
>
>     This document additionally updates another IMAP extension, Quick
>     Resynchronization, which builds on the Conditional Store extension to
>     provide an IMAP client the ability to fully resynchronize a mailbox
>     as part of the SELECT/EXAMINE command, without the need for
>     additional server-side state or client round-trips.  Hence this memo
>     obsoletes RFC 5162.
>
>     Finally, in when these extensions are used, other mechanisms are
>     updated.  In particular, the line length recommendation in RFC 2863
>     is modified, the UID EXPUNGE command from RFC 4315 is modified, and
>     the behavior of EXPUNGE from RFC 3501 is modified.
I slightly modified the last paragraph, as it was not quite right. But 
otherwise I've used your text. -08 posted.