Draft:  draft-ietf-imapext-condstore-08.txt
Reviewer: Black_David@emc.com
Review Date:  Thursday 2/9/2006 1:00 AM CST
IETF LC Date: 2/9/2006

Summary: This draft is basically ready for publication as a Proposed
Standard RFC, but has nits that should be fixed before publication.

The formatting of this draft is awful, as it takes ragged
right to a whole new level.  The idnits checker is not happy
about this or the lack of proper page separators, both of which
are already covered in Bert Wijnen's nits Comment in IESG discussion.

The table of contents is missing all of its page numbers.

The first portion of Section 2 is unclear as to whether it
is describing the elsewhere-specified behavior of IMAP vs.
imposing new requirements.  A check of RFC 3501 indicates
that the entire notion of mod-sequence is new to this draft.
The first sentence of the second paragraph is the problem -
is should be rephrased to something like:

   An IMAP server that supports this extension MUST associate
   a positive unsigned 64-bit value called a modification
   sequence (mod-sequence) with every IMAP message.

Beyond this, the draft is well-written with extensive
examples that will be of great use to implementers.