[Extra] Proposed update to draft-ietf-extra-imap-replace-02

Stuart Brandt <stujenerin@aol.com> Thu, 25 October 2018 01:31 UTC

Return-Path: <stujenerin@aol.com>
X-Original-To: extra@ietfa.amsl.com
Delivered-To: extra@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31AA5130DCD for <extra@ietfa.amsl.com>; Wed, 24 Oct 2018 18:31:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=aol.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mjZnz3x6hCCa for <extra@ietfa.amsl.com>; Wed, 24 Oct 2018 18:31:09 -0700 (PDT)
Received: from sonic312-22.consmr.mail.bf2.yahoo.com (sonic312-22.consmr.mail.bf2.yahoo.com [74.6.128.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 097D11292AD for <extra@ietf.org>; Wed, 24 Oct 2018 18:31:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aol.com; s=a2048; t=1540431067; bh=zC8nFf8HvG6FGMW4RzP26KXG39s9BNOw8u8BXvRlx5A=; h=Date:From:To:Subject:From:Subject; b=uIKw/ZQwOzuxxAXXnbrM4E27sTpmj5VUcseFsrLVsa7ZHRCPlH5tQnPu/jD2toO5unvXMncFP6noxK3nScZEPIVttigPhWNoU+nVqmQozkZgDMc+ZlXsRxdOSEwPhSRav5o1R1V6JlToZclEkHLMQQdDIOfa3U6Ms6zbK9JhoVvSUG9lxhIV0BmzpNJol/x7yLD6eQuW/cDm0/sJNnljPLTjSLvP2WVMolDvMxGbCiwbsjLf44sErK/C4glNljPl3z2t3r9HV6JR0oAAF7h5CHcYkJ42vYHr05fs519blWVdMyFnHL5Rn5KcOc4PO6vxvCVVBN5agyFHovUcZqJs7Q==
X-YMail-OSG: cgOujw0VM1npJIJU8JvrtPRH8Kbz4oHzB7Z6ul2bSKslk2rKsn.094eBp5UMOZx f_nzG8qZwaxnkPAHqLmdgFTEHjjjEHU.Q5JLdsalqJN1iClu2tgj8dcO5gtZaywlCOuvlMVJf8yC s89T_2YbVQb8LkNxagduMW6ytUwKxJiit29MKQEBMN3YV9CcLbG4WA2IStAdAi7XkuWMYjHR8HzH 5Il0ExgpNh7_QlzdznTqVrq5Cupeda61w.enneU93YGyHyxy1WdA3VDrDtmoxw2B12HKwvdaiSPA WBgt9QhdAyTS0S6GSnY1miUzkma0rHj81Va8flb.SJk2OLPBACplNCqOwXoQfQtWZmu8B_w.D6D3 D_bc5Q8HLTooh0vWjfEc_Om1vELabN_otayRZOhk34KRgCFzxDPlobDcq_tsfTj64G1gXhO4kJLc 4Px2H2bnx05709x0a6hlUWd7.ZK8Cy_5fJK_yEuESctjARp.e_KbpC.ZWjlCTikogWzfq2m4kcyB BTBCXrfAPVgls0TTIBuawvRhof5jfM2bjF6eXD1bmQRvi2P0iipAdIQTVgAQG_BgwRXG32HPeDa0 1LgZfBfZmjn9euux2K4F4WFLm_fhEJI_zzuVCmhJAicnzZgijnDrJqJN0Wwzh6s9Ys5kdGjJiV7w Gy4UATin5m5isuN9Np3MCZhnJR_iM8h99LkvO7IGRrthWxkrocQ4mK2tA6ne4BGF3WK6EUMJ9A1s 7_jmdc0N2vXygKzr2ACcSDwBA6TOBSa8RgGveP5O0BpeZWL4xNMgzx2EHTN1ANCpTwrxiZE4KqPw _GBVovzq9Ct6vGmfGCvbn_gfvu1K99U9B6cQdlADvG6B8hEoM13oQskYgcbiWZKyDywIZT0RQK75 .fdCDnjzhn0Xnw1Gr6TmuxW5qq_fkYSZLBeyFcJaBuEnWy59xtatvg_j3iaaS2IFlfdZZV3m_fKv vYGcVIgvVmVazxS3CMcl_1kNv6vxJ717f3Stqd3EHIdPbhET9jmoOzTAlUDoTZM2t1AY1tdwlsS7 O2MpogfdHGCektPnp
Received: from sonic.gate.mail.ne1.yahoo.com by sonic312.consmr.mail.bf2.yahoo.com with HTTP; Thu, 25 Oct 2018 01:31:07 +0000
Received: from pool-70-106-226-126.clppva.fios.verizon.net (EHLO [192.168.1.13]) ([70.106.226.126]) by smtp429.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 8a4b0630d4dd80b61f586f2859098398 for <extra@ietf.org>; Thu, 25 Oct 2018 01:31:04 +0000 (UTC)
Message-ID: <5BD11CB4.5080909@aol.com>
Date: Wed, 24 Oct 2018 21:30:28 -0400
From: Stuart Brandt <stujenerin@aol.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: extra@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/v21vU4nCoYd_b8a57PpjAqgLZVE>
Subject: [Extra] Proposed update to draft-ietf-extra-imap-replace-02
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Email mailstore and eXtensions To Revise or Amend <extra.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/extra>, <mailto:extra-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/extra/>
List-Post: <mailto:extra@ietf.org>
List-Help: <mailto:extra-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/extra>, <mailto:extra-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2018 01:31:11 -0000

Based on yesterday's last call feedback, there seems to be 2 areas where 
wording of the draft lacked clarity for reviewers. The following are 
proposed changes that I will make once the submission tool reopens. 
Feedback is welcomed.

A) Lack of clarity on state diagram impacts relative to UID REPLACE

Current...
    Unlike the APPEND command which is valid in the authenticated state,
    the REPLACE and UID REPLACE commands MUST only be valid in the
    selected state.  This difference from APPEND is necessary since
    REPLACE operates on message sequence numbers.

Proposed...
    Unlike the APPEND command, which is valid in the authenticated state,
    the REPLACE and UID REPLACE commands MUST only be valid in the
    selected state.  This difference from APPEND is necessary since
    REPLACE operates on message sequence numbers.  Additionally, the
    REPLACE extension intentionally follows the convention for UID
    commands found in [RFC3501] section 6.4.8 in that the UID variant of
    the command does not support use from the authenticated state.

B) Lack of clarity in final paragraph of the section 2

Current...
    In its simplest form, the REPLACE command is a single-command
    encapsulation of APPEND, STORE +flags \DELETED and UID EXPUNGE for a
    message, except that it avoids any of the quota implications or
    intermediate states associated with the 3 command sequence.  In
    handling a REPLACE command, a server MUST NOT generate a response
    code for the STORE +flags \DELETED portion of the sequence.
    Additionally, servers supporting the REPLACE command MUST NOT infer
    any inheritance of content, flags, or annotations from the message
    being replaced.  Finally, the replaced and replacing messages SHOULD
    NOT be present in the mailbox at the same time.

Proposed...
    In its simplest form, the REPLACE command is a single-command
    encapsulation of APPEND, STORE +flags \DELETED and UID EXPUNGE for a
    message, except that it avoids any of the quota implications or
    intermediate states associated with the 3 command sequence.  Server
    developers are encouraged to implement REPLACE as an atomic operation
    to simplify error handling, minimize operational concerns, and reduce
    potential security problems.  For systems where this is not possible,
    communication with the requesting client must ensure no confusion of
    message store state.  A server MUST NOT generate a response code for
    the STORE +flags \DELETED portion of the sequence.  Additionally,
    servers supporting the REPLACE command MUST NOT infer any inheritance
    of content, flags, or annotations from the message being replaced.