IETF Logo Mail Archive

Re: [Extra] [Last-Call] Artart last call review of draft-ietf-extra-imap-uidonly-06

Alexey Melnikov <alexey.melnikov@isode.com> Sat, 16 March 2024 23:58 UTC

Return-Path: <alexey.melnikov@isode.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 BB625C14CEFA; Sat, 16 Mar 2024 16:58:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8LGSL87OC_AF; Sat, 16 Mar 2024 16:58:22 -0700 (PDT)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 9A17FC14F721; Sat, 16 Mar 2024 16:58:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1710633500; d=isode.com; s=june2016; i=@isode.com; bh=AwWOBIT7ET/gXahmMmIBc078Wx8aHzdRumsYkgqhSss=; 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=PlEKfIM1efHqAiZBb0lRTyCiCOU58bPzjs0Y0kKpkLS1sF+taNZV2krpHCcc5z8fArQmCg 9loh2XU0h16NejXRQOFYZ+P4gUxDoAO55jxXxC9eOZ3yTT0GUc1YO2gCA+6WYXGgbbJeWM 4yHmLTheM3GwdseR8UtNSl3kdLWfiuw=;
Received: from [172.21.0.3] ((unknown) [172.21.0.3]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <ZfYyGwAOicfG@statler.isode.com>; Sat, 16 Mar 2024 23:58:20 +0000
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <aea85edb-c213-40d4-a3f9-45b2a0a43ac4@animal.isode.com>
X-Mailer: Isode Harrier Web Server
In-Reply-To: <171035954191.19370.12807276314372318250@ietfa.amsl.com>
References: <171035954191.19370.12807276314372318250@ietfa.amsl.com>
Date: Sat, 16 Mar 2024 23:58:07 +0000
cc: draft-ietf-extra-imap-uidonly.all@ietf.org, extra@ietf.org, last-call@ietf.org, art@ietf.org
from: Alexey Melnikov <alexey.melnikov@isode.com>
to: Barry Leiba <barryleiba@computer.org>
MIME-Version: 1.0
content-type: text/plain; charset="UTF-8"; delsp="yes"; format="flowed"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/fn_rWDS5k01GoHiwpUDY4h7CwTo>
Subject: Re: [Extra] [Last-Call] Artart last call review of draft-ietf-extra-imap-uidonly-06
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.39
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: Sat, 16 Mar 2024 23:58:26 -0000

Hi Barry,

On Wed, 13 Mar 2024 19:52:21 +0000 (GMT Standard Time), Barry Leiba via  
Datatracker wrote:
>Reviewer: Barry Leiba
>Review result: Ready with Issues
>
>— Section 3 —
>
>  Once the UIDONLY extension is enabled (see Section 3.1), the client
>  MUST NOT use message sequence numbers (including the special marker
>  "*") in any arguments to IMAP commands, and the server MUST return
>  tagged BAD response if the client uses message sequence numbers.  The
>  server SHOULD include the UIDREQUIRED response code in such BAD
>  responses (see below).
>
>I see nothing below that says why this is SHOULD rather than MUST, and I  
>can’t
>imagine any justification for not including it.  Why is this SHOULD?

Historically server inclusion of many IMAP response codes was a quality of  
implementation issue.
In this case the client is clearly doing something wrong - it can't  
accidentally enable UIDONLY and then not use UIDs anyway. I suppose  
UIDREQUIRED can just be required, as it will help client implementers and  
server operators.

Best Regards,
Alexey

v2.23.0 | Report a Bug | By Email