[Extra] Martin Duke's No Objection on draft-ietf-extra-imap4rev2-25: (with COMMENT)

Martin Duke via Datatracker <noreply@ietf.org> Sat, 23 January 2021 04:57 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: extra@ietf.org
Delivered-To: extra@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E02E53A0C53; Fri, 22 Jan 2021 20:57:23 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Martin Duke via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org, extra@ietf.org, brong@fastmailteam.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.24.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Martin Duke <martin.h.duke@gmail.com>
Message-ID: <161137784334.20615.12096399788075509949@ietfa.amsl.com>
Date: Fri, 22 Jan 2021 20:57:23 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/DgfyWjscZragheI2AEWEFiajXls>
Subject: [Extra] Martin Duke's No Objection on draft-ietf-extra-imap4rev2-25: (with COMMENT)
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 23 Jan 2021 04:57:24 -0000

Martin Duke has entered the following ballot position for
draft-ietf-extra-imap4rev2-25: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)

Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.

The document, along with other ballot positions, can be found here:


Various non-blocking questions/comments: what would happen if the UID approached 2^32 due to a lifetime of spam
or something? The server can increment the validity value, but doesn’t that
make earlier email unreferenceable except via sequence number?

2.3.2 In the $Phishing definition, do you mean the user agent SHOULD (in caps)
display an additional warning message?

4.1.1 the last statement, “ the "*" value for a sequence number is not
permitted.”, is oddly placed, enough that it almost reads like a typo where you
meant UID. A clearer statement might be “The ‘*’ value is permitted for UIDs
but not sequence numbers.”