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

Bron Gondwana <brong@fastmailteam.com> Sun, 24 January 2021 03:14 UTC

Return-Path: <brong@fastmailteam.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 57BA73A1114; Sat, 23 Jan 2021 19:14:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.118
X-Spam-Level:
X-Spam-Status: No, score=-2.118 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fastmailteam.com header.b=EP068hNR; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ES0jPjad
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 J7Nah2qDnkQP; Sat, 23 Jan 2021 19:14:52 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 253953A1113; Sat, 23 Jan 2021 19:14:51 -0800 (PST)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 6A6F25C0120; Sat, 23 Jan 2021 22:14:50 -0500 (EST)
Received: from imap7 ([10.202.2.57]) by compute2.internal (MEProxy); Sat, 23 Jan 2021 22:14:50 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= fastmailteam.com; h=mime-version:message-id:in-reply-to :references:date:from:to:cc:subject:content-type; s=fm1; bh=PhxZ orp8z7eneNic4cWTgFKFg4lsEdDTyeFfGqq1oNI=; b=EP068hNR8r4A1vFKKAxZ Vo4TLZG6ZVgLG8iIf1ULU4uX20FTD6jwYD0MZuaqhNR7x52eE58jajdcmYvlfP3j nnWgDipGCwEUH4dd9vYz31/ScWokTEYMQe/qcNIJ/wO9sIRd4ZLGBTfpkfFTMii7 s5TScNWfN9mYRPWY0w+1NmZSvSJRXUrZG2+1xY89I4+kN9sj/SptwrtF+Y7BdvgZ 463Je4Tudhfz7xVOhSkMlWfPcD5A1vwL6Su55pvIi7+IkPe+2MPitoMbB89g371O TSR52ti5DfepE/YVU6OubFbmzYMF5tAyRbf6brxBlX29mAPF60j84X+jJ6Ct6nhA Gw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=PhxZor p8z7eneNic4cWTgFKFg4lsEdDTyeFfGqq1oNI=; b=ES0jPjaduLJR1reIiiCPOV W3TkXDQsi+CUfaZ30WEsHZ2Ynb+1DiK/nZUvN94W5+GqF8m94naVdqSWt1PaxUsx TEYXD+odd70uInj5F8te8Yqg/POsaw9CT8CVxMOfFA4GPkqweY9hlOJQw7MGf195 hSDvdVcJmLObql6qVMa1at6r0KD3BrjFD3cDwEq/V5kqnPBejTOspjNSBYUrAinn aj0u6nBy02mCAJ39GXYmwDhYJAqzcueKyo+OT4hfFAE2bUVV5OrOWIhi+MP/okFc eQHSchq1w2leW5o4nfHE3ZZTMopNkrl8tHJIEKcZz54VS/AIr96OxmnW1g4v5iJw ==
X-ME-Sender: <xms:KuYMYL3_SPEMp49384EihyEvUsp0HA1viwnmKmmQ4rF2q-k1t8pkRA> <xme:KuYMYKHNCkKbLlnIj8G5pHQ_lSrWLy70ueTs-oPcER3wFyi-G40OwJqa3cTRxzDit ubBvLM75_U>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudelgdehiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsegrtderreerreejnecuhfhrohhmpedfuehrohhn ucfiohhnugifrghnrgdfuceosghrohhnghesfhgrshhtmhgrihhlthgvrghmrdgtohhmqe enucggtffrrghtthgvrhhnpeetvdejvdffudetleefteetgfegkefffffgkeeugfeijeei hfejteffvedtvddttdenucffohhmrghinhepihgrnhgrrdhorhhgnecuvehluhhsthgvrh fuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepsghrohhnghesfhgrshhtmhgr ihhlthgvrghmrdgtohhm
X-ME-Proxy: <xmx:KuYMYL6LJPkaJ3Aq4PPMbM3lFnBpNOSP5Da0JGH3Vw3-Cir5fJZmdw> <xmx:KuYMYA2gJ8b7R49yf6LpHg9fReXUMWeRLrWbnRGvJp1qzoesoMqikQ> <xmx:KuYMYOGX6gZj1P3-R_nFvdOXvmJEAv1qQO9Gegi07y71DK2AmTDkYg> <xmx:KuYMYDRg4gdi4qbPFloVC987YhO-ZeaGeg2PNiXGkdVqHSXopP4wYQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id F0D9B36005C; Sat, 23 Jan 2021 22:14:49 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.5.0-alpha0-78-g36b56e88ef-fm-20210120.001-g36b56e88
Mime-Version: 1.0
Message-Id: <f950de71-5e6a-4b19-ad2e-40b7394c27f7@dogfood.fastmail.com>
In-Reply-To: <161137784334.20615.12096399788075509949@ietfa.amsl.com>
References: <161137784334.20615.12096399788075509949@ietfa.amsl.com>
Date: Sun, 24 Jan 2021 14:14:28 +1100
From: Bron Gondwana <brong@fastmailteam.com>
To: Martin Duke <martin.h.duke@gmail.com>, The IESG <iesg@ietf.org>
Cc: draft-ietf-extra-imap4rev2@ietf.org, extra-chairs@ietf.org, extra@ietf.org
Content-Type: multipart/alternative; boundary="2a23ac5a6cb74bbc91c6078df482e500"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/awjar_gNmWp9N8JTY3BwgCQ4HW0>
Subject: Re: [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
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: Sun, 24 Jan 2021 03:14:54 -0000

On Sat, Jan 23, 2021, at 15:57, Martin Duke via Datatracker wrote:

(I know the answers to these!)

> 2.3.1.1 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?

Sequence number is even less persistent - but when you increment the UIDVALIDITY you can renumber the UIDs for everything, so you'd just start at 1 and reid all the existing records.  So they'll be referenceable by their new UIDs next time the mailbox is selected.

And (plug) if the server implements RFC8474 (object ids) then a client can even tell that it's the same email and not need to fetch the content again, even after a UIDVALIDITY change.

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

This definition is copied from the IANA registry for keywords:

https://www.iana.org/assignments/imap-jmap-keywords/phishing/phishing-template

I'm not sure there's any point in changing the text to be different from the IANA registration just to make it capital SHOULD.  It's unlikely to change anybody's behaviour on reading this document.

> 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.”

No, that would be an incorrect statement.  The phrase "UID set" is a definitional term which means:

* a sequence set;
* that references UIDs, not message numbers; and
* that consists only of numbers, not the magic '*' character (which can change value as new messages arrive)

You can have a "sequence set" which references UIDs and does contain '*', but then it's not a "UID set" any more by definition.

Cheers,

Bron.

--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  brong@fastmailteam.com