Re: [Extra] BINARY in imap4rev2 (was Re: I-D Action: draft-ietf-extra-imap4rev2-04.txt)

Alexey Melnikov <alexey.melnikov@isode.com> Tue, 12 March 2019 14:02 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 3AD05130DF6 for <extra@ietfa.amsl.com>; Tue, 12 Mar 2019 07:02:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 9N_t9nlPvF3P for <extra@ietfa.amsl.com>; Tue, 12 Mar 2019 07:01:59 -0700 (PDT)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 6032A130DCB for <extra@ietf.org>; Tue, 12 Mar 2019 07:01:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1552399318; d=isode.com; s=june2016; i=@isode.com; bh=ATGooI9e26RdvPw1tFHH3J79sG64I9V290urt7nFyzE=; 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=pGN7T+XALdjPBHh0VPGPOkcJG5vd6KM9RQmFUMnFlb0dR5+YdG2gdAxzmrvNEnTESzVP4u J4LUEgl2AApW6Tl/R+bC+a6aFqu4vyANxLal0WDLj1DT91wPbe0oKVf5xQZ4vyT/jaU6B6 qVwx0T7mawGiU5nel0TJYGaD0D3/ZIw=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <XIe71QBUXgQK@statler.isode.com>; Tue, 12 Mar 2019 14:01:58 +0000
To: Chris Newman <chris.newman@oracle.com>, extra@ietf.org
References: <155212910291.28686.15855866349973202216@ietfa.amsl.com> <3C6355CD-BA02-41A7-8DDA-16233E41B0EF@oracle.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <935596a7-a41c-0c4f-676a-0927c6dcf0f0@isode.com>
Date: Tue, 12 Mar 2019 14:01:44 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.0
In-Reply-To: <3C6355CD-BA02-41A7-8DDA-16233E41B0EF@oracle.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/-Jtl6Im2XL9J98I9G0NDif37t68>
Subject: Re: [Extra] BINARY in imap4rev2 (was Re: I-D Action: draft-ietf-extra-imap4rev2-04.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: Tue, 12 Mar 2019 14:02:01 -0000

On 11/03/2019 20:37, Chris Newman wrote:
> I do believe the document should make it clear whether a FETCH 
> BINARY[] can be applied to a non-leaf body part and what the result 
> will be if that's done.
>
> Possible choices:
>  * not allowed, will result in a BAD/NO
>  * allowed, but may result in UNKNOWN-CTE for servers that don't 
> support recursive CTE removal on sub-parts of non-leaf types.
>  * Allowed to fetch non-leaf and server has to support decoding base64 
> & QP CTEs of all parts of {multipart/*, message/rfc822, 
> message/global} recursively.
>
> The IMAP BINARY spec was never clear on this point.

I agree that we should make this clear, this is already on my to do list.

I haven't made up my mind about which option is the best, partially 
because message/global has changed processing of email messages a bit.