IETF Logo Mail Archive

Re: [Extra] [EXT] Re: I-D Action: draft-ietf-extra-imap4rev2-15.txt

Alexey Melnikov <alexey.melnikov@isode.com> Thu, 03 September 2020 08:53 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 102053A0C92 for <extra@ietfa.amsl.com>; Thu, 3 Sep 2020 01:53:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.047
X-Spam-Level:
X-Spam-Status: No, score=-3.047 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, NICE_REPLY_A=-0.948, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F7MxR0Suyp3q for <extra@ietfa.amsl.com>; Thu, 3 Sep 2020 01:53:45 -0700 (PDT)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id F3D4D3A0C86 for <extra@ietf.org>; Thu, 3 Sep 2020 01:53:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1599123223; d=isode.com; s=june2016; i=@isode.com; bh=DPCwCva7R7JxZFCKt0Fe9JU3FXMYxzVl0vnS4txT09g=; 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=K4LQzr+xf1HBBexMaH6IV6Ni5YfBu3B5roymvxZFao61qSzzkbCHGelxX9bD8tartP8j6E AQN8p2K/WFupb5Q6GLVzNexwS68xpagEcyOn45f1z1LkK/mM4JhCC5+/e676ddts/SqkVZ e1gdGvDvYl3tDMJIv/ZHucW5Dwex4nc=;
Received: from [172.27.248.45] (connect.isode.net [172.20.0.72]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <X1CvFgBUoDUC@statler.isode.com>; Thu, 3 Sep 2020 09:53:43 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: Stephan Bosch <stephan.bosch@open-xchange.com>, extra@ietf.org
References: <159238763595.1803.574245566610096074@ietfa.amsl.com> <b4390473-241f-6860-2ebb-fdf4dad06ec8@isode.com> <a7304716-b160-4731-e145-934cb127d28e@open-xchange.com> <b908d009-5ee4-9caa-63ea-23788a270188@open-xchange.com> <de1f23c9-5516-91d7-039e-9354ce73ffea@isode.com> <66611b2f-e1aa-1609-f296-4b4f5db92bbb@open-xchange.com>
Message-ID: <d8d81519-815c-a48d-fc19-e2a8a3c78010@isode.com>
Date: Thu, 03 Sep 2020 09:53:20 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
In-Reply-To: <66611b2f-e1aa-1609-f296-4b4f5db92bbb@open-xchange.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/uh5HTTTDyaPeiDsa-SlqegaA3AU>
Subject: Re: [Extra] [EXT] Re: I-D Action: draft-ietf-extra-imap4rev2-15.txt
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, 03 Sep 2020 08:53:46 -0000

On 02/09/2020 21:06, Stephan Bosch wrote:

> Hi Alexey,
>
> On 29/07/2020 17:55, Alexey Melnikov wrote:
>>>>    It is an error for the server to return both a \HasChildren and a
>>>>    \HasNoChildren attribute in the same LIST response.
>>>> -> Any recommendation for what clients should do if this does 
>>>> happen? Provisionally treat it as \HasChildren?
>
> No word on this? Do we want to avoid recommending error mitigation 
> strategies in the document?

I am still thinking about this. General answer is "sometimes" :-). Cases 
about malformed email messages are the most difficult to decide.

In this particular case I think if both are present, the client needs to 
pretend that neither is set and behave accordingly.


Best Regards,

Alexey

v2.23.0 | Report a Bug | By Email