[Extra] Opsdir last call review of draft-ietf-extra-imap-replace-02

Scott Bradner <sob@sobco.com> Sun, 21 October 2018 00:12 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Scott Bradner <sob@sobco.com>
To: ops-dir@ietf.org
Cc: extra@ietf.org, draft-ietf-extra-imap-replace.all@ietf.org, ietf@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <154008077269.13778.3909814853433103491@ietfa.amsl.com>
Date: Sat, 20 Oct 2018 17:12:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/pvXNMyMaAh0GsG2EXgcVE03bbiw>
Subject: [Extra] Opsdir last call review of draft-ietf-extra-imap-replace-02

Reviewer: Scott Bradner
Review result: Has Nits

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

[Extra] Opsdir last call review of draft-ietf-ext… Scott Bradner
Re: [Extra] Opsdir last call review of draft-ietf… Stuart Brandt