[mailmaint] Re: WGLC on draft-ietf-mailmaint-imap-uidbatches-18

Alexey Melnikov <alexey.melnikov@isode.com> Thu, 06 November 2025 16:14 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: mailmaint@mail2.ietf.org
Delivered-To: mailmaint@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 5F5BF847B544 for <mailmaint@mail2.ietf.org>; Thu, 6 Nov 2025 08:14:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tC8HHPfoZjvP for <mailmaint@mail2.ietf.org>; Thu, 6 Nov 2025 08:14:30 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [195.21.82.44]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 6881A847B180 for <mailmaint@ietf.org>; Thu, 6 Nov 2025 08:13:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1762445601; d=isode.com; s=june2016; i=@isode.com; bh=U3d5rAt6IuuEMygt5gqqkQ06D+xXcKPOA6L18RblQUg=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=FUb4qX1Yri4SmdZy2YPDKOMi41nDd4XGwE8E92f5KbMmPOR/Sx6J3p/anzSJZajDbDWNn6 eb6CNzfG2mS89ju0Qvqofu+UQVDhV3yLJg6AqkSghbfSLe+bSBjmALFytmr4btxbWUUIaH TZhvtuKsCanGUBib5QzfBzjVQqFERlc=;
Received: from [172.20.12.75] ((unknown) [107.161.12.68]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <aQzJITbQjgAa@waldorf.isode.com>; Thu, 6 Nov 2025 16:13:21 +0000
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <7df538ad-4a00-49a4-b4ce-0e9c746a361a@isode.com>
Date: Thu, 06 Nov 2025 11:13:20 -0500
User-Agent: Mozilla Thunderbird
To: Ken Murchison <murch@fastmail.com>, mailmaint@ietf.org
References: <28053d62-a9f8-4658-86b2-eea67ea4381a@fastmail.com> <078b8dda-a6f3-4012-9a70-ff69ecba0e58@fastmail.com> <bd8caf14d74954c4d1b878c5bb5bedd050024bac@gulbrandsen.priv.no>
From: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <bd8caf14d74954c4d1b878c5bb5bedd050024bac@gulbrandsen.priv.no>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------aLEZqL4qqWlg7W8rwq3Wj1PJ"
Content-Language: en-US
Message-ID-Hash: 2VUCNKWRI6CQTID2C77W2YHOOYKLI46V
X-Message-ID-Hash: 2VUCNKWRI6CQTID2C77W2YHOOYKLI46V
X-MailFrom: alexey.melnikov@isode.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [mailmaint] Re: WGLC on draft-ietf-mailmaint-imap-uidbatches-18
List-Id: Mail Maintenance <mailmaint.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/mailmaint/ox7DJORivuVsYv13btlsTEKfpKA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mailmaint>
List-Help: <mailto:mailmaint-request@ietf.org?subject=help>
List-Owner: <mailto:mailmaint-owner@ietf.org>
List-Post: <mailto:mailmaint@ietf.org>
List-Subscribe: <mailto:mailmaint-join@ietf.org>
List-Unsubscribe: <mailto:mailmaint-leave@ietf.org>

Hi all,

On 23/10/2025 11:24, Arnt Gulbrandsen wrote:
> October 23, 2025 at 1:41 PM, "Ken Murchison" <murch@fastmail.com 
> <mailto:murch@fastmail.com?to=%22Ken%20Murchison%22%20%3Cmurch%40fastmail.com%3E>> 
> wrote:
>
>     Arnt, Alexey,
>
>     Since you both have read the doc and provided feedback previously,
>     are you ok with the current version?
>
>
> Yes.

I am not entirely. I think the document went too far the other way to 
become unnecessarily flexible on server side.

More specifically:

In 3.1.3.1. Batch Size Summary

    *  Servers SHOULD return batches close to the requested size (>= 90%
       and <= 110% when possible)

Why would server ever return more data than asked by the client, if the client is not interested in it? This waste bandwidth and would be easily enough to filter out on the server before sending.

(also in the table above this text)


In 3.1.3.3.1.  Hard Constraints

    If the server supports the [RFC9738] MESSAGELIMIT and UIDBATCHES
    extensions, the server MUST NOT return ranges that contain more than
    the number of messages per batch requested by the client.  This is a
    strict upper bound that cannot be exceeded.  See Section 3.2 for
    details.

So this text was not tied to MESSAGELIMIT extension in the previous 
revision. Why is this restriction tied to MESSAGELIMIT?

Not having batch sizes larger than announced MESSAGELIMIT would make 
sense, but this is not what the above text is saying.


Best Regards,

Alexey