Moving IDLE to Draft Standard

[Barry Leiba <[e-mail]>]

I'm getting ready to put IDLE on the path to Draft Standard (it'll have
to wait until the base spec gets there, but it can get on the queue).
I've just sent draft-leiba-imap-2177bis-00.txt to the I-D editor, so
watch for it soon; it's attached here for your reading pleasure.  It's
mostly the same as RFC 2177, with editorial changes generated, mostly,
from conversion of the source to use xml2rfc.  I've also updated the
references, and changed the ABNF to the current syntax.  The minor
substantive changes are

   Clarified that ANY response may come from the server during IDLE,
   and gave examples of the most common responses.

   Clarified that anything other than "DONE" is "BAD".

These are both the result of common questions from implementors.

I need to put together an interoperability report.  To that end, please
tell me (you can reply off-list, and I'll summarize responses on the
list) about client and server implementations of IDLE.  Tell me also,
if you have experience using one client implementation with a different
server implementation.

Barry

--
Barry Leiba, Pervasive Computing Technology  ([e-mail])
http://www.research.ibm.com/people/l/leiba
http://www.research.ibm.com/spam