Skip to main content

Last Call Review of draft-ietf-extra-imap-partial-02

Request Review of draft-ietf-extra-imap-partial
Requested revision No specific revision (document currently at 04)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2022-11-19
Requested 2022-11-05
Authors Alexey Melnikov , ArunPrakash Achuthan , Vikram Nagulakonda , Luis Alves
I-D last updated 2022-11-21
Completed reviews Opsdir Last Call review of -04 by Yingzhen Qu
Genart Last Call review of -02 by Roni Even (diff)
Opsdir Last Call review of -02 by Yingzhen Qu (diff)
Assignment Reviewer Yingzhen Qu
State Completed Snapshot
Review review-ietf-extra-imap-partial-02-opsdir-lc-qu-2022-11-21
Posted at
Reviewed revision 02 (document currently at 04)
Result Has Nits
Completed 2022-11-21
I have reviewed this document 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.

Document: draft-ietf-extra-imap-partial-02
Reviewer: Yingzhen Qu
Review Date: 2022-11-20

This document extends PARTIAL SEARCH return option defined in RFC 5267.
The document is ready, but the following nits should be considered
before publication.

General: this documents still has a normative reference to RFC 3501, which
was obsoleted by RFC 9051. RFC 3501 is referenced multiple times in the

Nits (line numbers are from idnits):

90   This document defines an extension to the Internet Message Access
91   Protocol [RFC3501] for performing incremental searches and fetches.

major: RFC 9051 should be referenced here instead of RFC 3501.

101   This document extends PARTIAL SEARCH return option originally

nits: should it be "PARTIAL SEARCH" (used 4 times) or "PARTIAL search"
(used 2 times)? 

245	          +------------------------------+---------------------+
246	          |    SAVE PARTIAL COUNT [m]    |  all found messages |
247	          +------------------------------+---------------------+

249	                                 Table 1

251	   where '[m]' means optional "MIN" and/or "MAX"

Question: If the SAVE + PARTIAL result options are combined with COUNT,
MIN and MAX, what the result would be? The text above the table didn't
cover this case.