Last Call Review of draft-ietf-extra-imap-replace-02
review-ietf-extra-imap-replace-02-opsdir-lc-bradner-2018-10-20-00
| Request | Review of | draft-ietf-extra-imap-replace |
|---|---|---|
| Requested revision | No specific revision (document currently at 03) | |
| Type | Last Call Review | |
| Team | Ops Directorate (opsdir) | |
| Deadline | 2018-10-16 | |
| Requested | 2018-10-02 | |
| Authors | Stuart Brandt | |
| I-D last updated | 2018-10-20 | |
| Completed reviews |
Genart Last Call review of -01
by Robert Sparks
(diff)
Secdir Last Call review of -01 by Catherine Meadows (diff) Opsdir Last Call review of -02 by Scott O. Bradner (diff) |
|
| Assignment | Reviewer | Scott O. Bradner |
| State | Completed | |
| Request | Last Call review on draft-ietf-extra-imap-replace by Ops Directorate Assigned | |
| Reviewed revision | 02 (document currently at 03) | |
| Result | Has nits | |
| Completed | 2018-10-20 |
review-ietf-extra-imap-replace-02-opsdir-lc-bradner-2018-10-20-00
This is an OPS-DIR review of IMAP REPLACE Extension (draft-ietf-extra-imap-replace-02) imo - this proposal causes negative ops issues - i.e. it fixes potentially bad ops situations where the state of a message repository is not determinable due to the failure of one of a chain of commands. so it reduces potential ops issues that said, it seems to me that section 3.4 could more clearly state that no changes are to be made to the repository unless all changes are made - i.e., 'all or nothing' - the information is there but it is a bit convoluted and the use of a clear simple statement would help