Skip to main content

Last Call Review of draft-ietf-imapapnd-appendlimit-extension-07

Request Review of draft-ietf-imapapnd-appendlimit-extension
Requested revision No specific revision (document currently at 10)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2016-01-05
Requested 2015-12-22
Authors Jayantheesh , Narendra Singh Bisht
I-D last updated 2016-01-11
Completed reviews Genart Last Call review of -07 by Peter E. Yee (diff)
Secdir Last Call review of -07 by Paul Wouters (diff)
Opsdir Last Call review of -07 by Sarah Banks (diff)
Assignment Reviewer Sarah Banks
State Completed
Request Last Call review on draft-ietf-imapapnd-appendlimit-extension by Ops Directorate Assigned
Reviewed revision 07 (document currently at 10)
Result Has nits
Completed 2016-01-11
I have reviewed draft-ietf-imapapnd-appendlimit-extension-08 as part of the
Operational directorate's ongoing effort to review all IETF documents
being processed by the IESG.  These comments were written with the
intent of improving the operational aspects of the IETF drafts. Comments
that are not addressed in last call may be included in AD reviews during
the IESG review.  Document editors and WG chairs should treat these
comments just like any other last call comments.

The document is ready with a minor nit/comment.

This draft discusses an extension to IMAP, where a server can use APPENDLIMIT
to communicate to the client the maximum mail upload size, via several commands
(status, list, capability). The document cites a particularly useful use case,
of mobile devices and resource contention. I found the document fairly well
written, and I have a single comment:

Section 3.1 - is the should in "should issue a STATUS command"  normative? It
reads as if it could be...

Authors, thanks for making me research "hone in" versus "home in" (ala section
6). :)

Kind regards,