Skip to main content

Last Call Review of draft-ietf-extra-specialuse-important-03
review-ietf-extra-specialuse-important-03-opsdir-lc-clarke-2018-05-21-00

Request Review of draft-ietf-extra-specialuse-important
Requested revision No specific revision (document currently at 04)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2018-05-14
Requested 2018-04-30
Authors Barry Leiba
Draft last updated 2018-05-21
Completed reviews Genart Last Call review of -03 by Brian E. Carpenter (diff)
Secdir Last Call review of -03 by Stefan Santesson (diff)
Opsdir Last Call review of -03 by Joe Clarke (diff)
Assignment Reviewer Joe Clarke
State Completed
Review review-ietf-extra-specialuse-important-03-opsdir-lc-clarke-2018-05-21
Reviewed revision 03 (document currently at 04)
Result Ready
Completed 2018-05-21
review-ietf-extra-specialuse-important-03-opsdir-lc-clarke-2018-05-21-00
I have been asked to review  draft-ietf-extra-specialuse-important on behalf of
the ops directorate.  I apologize for the tardiness of the review.

This document describes a new IMAP message keyword, $Important and a new
\Important attribute to designate a mailbox to hold such "important" messages. 
The rules of what is "important" are external to this document.  This document
also defines a registry with which to hold IMAP attributes (and includes
\Important in this registry).

On the whole, this document is ready.  My only ops-related comment relates to
interoperability with services like Google's GMail that offer an "Important"
mailbox today.  How will this standardization interoperate with existing
implementations?  And is it worth explaining that in some text herein?

In terms of nits, I found just one readability item.

Section 2:

s/While the keyword also can/While the keyword can also/