Re: [Extra] Working Group Last Call - draft-ietf-extra-imap-fetch-preview-08

Bron Gondwana <brong@fastmailteam.com> Fri, 24 July 2020 04:22 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 3B3AC3A0AFF for <extra@ietfa.amsl.com>; Thu, 23 Jul 2020 21:22:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level:
X-Spam-Status: No, score=-2.119 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_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=EX5jfBGC; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ffmnPif5
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 pDv57iAXdVMt for <extra@ietfa.amsl.com>; Thu, 23 Jul 2020 21:21:58 -0700 (PDT)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 316EC3A0B03 for <extra@ietf.org>; Thu, 23 Jul 2020 21:21:58 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 8327EA1E for <extra@ietf.org>; Fri, 24 Jul 2020 00:21:56 -0400 (EDT)
Received: from imap7 ([10.202.2.57]) by compute1.internal (MEProxy); Fri, 24 Jul 2020 00:21:56 -0400
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:subject:content-type; s=fm3; bh=Yg9Jg0K AITnOWpPhLzeaefIq+H+bZklKZBHCIDWzkOg=; b=EX5jfBGCKqc3zlqft5UR+th bI4zwT23CExPYbsjnXfPEHyLdUm34kEasHIR1LlAroEoe7OxDgm7WXYeqqbesbpv Sg+Hvjjaa5LWaUudXskVFp3DwNFzDTulzqO9yszPVy5xDiFW3JZTFpzCdVE5t/V5 RfZVmav8ymALFDbERUMyXngn04JXWVMoPMTG7P1Aa0HI/JO/HSJz4wDc5VDexFK7 wXjvGlbsBLzZxjWsG2wBHoGhOJVrKEmMY0rDRcI+zQlM/04APTeytKSYiXutmW7J UCegC3bX+zL5zQmcuzGuZpOugsSZ3ZNDrBK7XLE63cV7DMijG1qud8yH6k60MkA= =
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=fm3; bh=Yg9Jg0 KAITnOWpPhLzeaefIq+H+bZklKZBHCIDWzkOg=; b=ffmnPif5sBS7OXbM9cRhZU bycTuiYc4D4CIY55Xdf7aWaM8DMrS/j554UMhC4L5xSOwCka+D5+Zs8ARTW8gtYL VSTFdIeZI3OR80W4PpY5H67yhvNwqY9PEfdGBML8iQ2NTAcIaR5A4O9NLuNgPMbX ftS8/PlRQAAvD4GF48cVAna7IKNyOK8U18xp0oSD4Mho/MSf4iHVvkDYsmG/RrOP RgxzoqwSiX/Jis4dEwb2bEULk62pfmhKl3PW82TrKJZmTqP2dQ4QiAwwp1jbcV65 Kj5UcD0zg08x4rUWw6PjzsNhlXEQXHFgBQmM3DBOF3FmLhND2L8khsG50X/M6BaA ==
X-ME-Sender: <xms:42EaX9PpN1atNSsSfmTMcovGpCBLP-5aQUPxzyyF6nkW7uo1FSTsSg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrhedvgdejlecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesrgdtre erreerjeenucfhrhhomhepfdeurhhonhcuifhonhgufigrnhgrfdcuoegsrhhonhhgsehf rghsthhmrghilhhtvggrmhdrtghomheqnecuggftrfgrthhtvghrnhepffdvkeefgeelie eutedttdffheevvefffeekuddvtddtkeeigfejuddvhfdvudelnecuffhomhgrihhnpehi vghtfhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpegsrhhonhhgsehfrghsthhmrghilhhtvggrmhdrtghomh
X-ME-Proxy: <xmx:42EaX_88XMLr2wVY6iE146obtPDiRxAL9Qx5gXYkZ2D4yKvjplwdYw> <xmx:42EaX8Rqh_QBleXs7-SHq0X1pWyJZelhdhy32puH49cSBVH88EEYUg> <xmx:42EaX5v5J3GZqlIkzzOqy3mb8cf2R1jWnZU_m46UYR99FAIwAsDP_w> <xmx:5GEaXw_DGFgnUd3tl0XcLR-o454PPbhxQq-sR-gG_K8wd3t_IWrEGw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id DCF351803EE; Fri, 24 Jul 2020 00:21:55 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-92-g11c785d-fm-20200721.004-g11c785d5
Mime-Version: 1.0
Message-Id: <4d502b60-f4a3-4c33-8301-b6c552437359@dogfood.fastmail.com>
In-Reply-To: <381786159.2271.1594783773523@appsuite.open-xchange.com>
References: <c4da8962-ec81-4ee5-b2e1-258d5b247770@dogfood.fastmail.com> <E7CA280C-D1B9-4BE7-8109-E070CF742623@sirainen.com> <1948688035.19548.1594092129291@appsuite.open-xchange.com> <388F9721-0CB5-4146-AC23-503C4481A090@sirainen.com> <c531ac34-00fd-455e-a0a0-5d3f3b51a038@dogfood.fastmail.com> <381786159.2271.1594783773523@appsuite.open-xchange.com>
Date: Fri, 24 Jul 2020 14:21:35 +1000
From: Bron Gondwana <brong@fastmailteam.com>
To: extra@ietf.org
Content-Type: multipart/alternative; boundary="4f21dc92b23a44ed9a81ac38df5a90f6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/qHaxnEx4ZH2b_8tncb3rbWLg8rA>
Subject: Re: [Extra] Working Group Last Call - draft-ietf-extra-imap-fetch-preview-08
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: Fri, 24 Jul 2020 04:22:00 -0000

I'm ready to go with this on Monday :)

On Wed, Jul 15, 2020, at 13:29, Michael Slusarz wrote:
> It seems I was a day late to submit, as submissions are paused before the meeting...
>  
> I've finished the -09 draft.  If interested, I could post a copy.  Otherwise, I will just submit at end of the month when submission tool is reopened.
>  
> Changes in -09:
>  * PREVIEW without LAZY MUST NOT return NIL (kept it simple)
>  * Rewrote the LAZY modifier section a bit to break apart the semantics of LAZY from "Client Implementation Advice".  The latter is a combo of some of the text previously in the section with list recommendations.  Slightly tweaked Example 2 to request two previews in a single FETCH request in background.
> Decided to make no mention of NO response in this document.  After discussion here, it seems like that is expected to be an extremely rare case - and that case is already adequately handled by FETCH command definition in base IMAP spec.
>  
> michael
>  
>> On 07/07/2020 5:00 AM Bron Gondwana <brong@fastmailteam.com> wrote:
>>  
>>  
>> On Tue, Jul 7, 2020, at 18:54, Timo Sirainen wrote:
>>> On 7. Jul 2020, at 6.22, Michael Slusarz <michael.slusarz=40open-xchange.com@dmarc.ietf.org> wrote:
>>>>  
>>>>> On 07/02/2020 3:20 AM Timo Sirainen <timo@sirainen.com> wrote:
>>>>>  
>>>>>  
>>>>> On 2. Jul 2020, at 4.56, Bron Gondwana < brong@fastmailteam.com> wrote:
>>>>>  
>>>>>> As discussed in the interim meeting, this document was brought back to the working group to be reverted to an earlier and simpler version.
>>>>>>  
>>>>>> This email announces a 2 week working group last call for any further comments on this version before I re-submit to IESG for publication.  Please reply with any comments by Thursday, July 16th 2020.  Let's get this one off our plates before IETF108.
>>>>>  
>>>>>    It is possible that preview text is not available now, but might be
>>>>>    available later -- perhaps the server's preview-generating resources
>>>>>    are overloaded, there is a server-imposed timeout during preview
>>>>>    generation, or there is some transient issue with fetching the
>>>>>    message body.  In such cases, the server will return NIL as the
>>>>>    preview response, and the client can try to retrieve the preview
>>>>>    later.
>>>>> This sounds like it's possible for server to return NIL even when the LAZY modifier isn't specified. Is this really wanted? I'd think client developers would prefer that only LAZY can return NILs. Either way, it's not clearly enough specified what is intended.
>>>> I was originally going to agree with Timo ... but then I remember we added this part as a direct response to a potential DoS situation - what happens if preview requests are (subjectively) taking too much time.
>>>  
>>> I don't really see why this would be an issue. IMAP protocol doesn't have this kind of a special "DoS-prevention feature" anywhere else. Especially now that the preview is always text, I don't think it can be excessively slow to generate it. At least in Dovecot's implementation it's basically as expensive as fetching BODYSTRUCTURE, and we don't have DoS prevention against fetching those. Maybe in theory if server wanted to analyze attachments in some way .. but is it really worth the added complexity for a problem that probably will remain theoretical?
>>>  
>>> FETCH is also good in that it returns the results after each mail. So the server is allowed to start throttling the responses to the client without actually failing it.
>>  
>> You're right.  Here we are overcomplexing it again!
>>  
>> Server MUST NOT return NIL to a non-lazy preview is fine by me.
>>  
>> Server SHOULD NOT return NIL is fine by me as well, along with clients SHOULD NOT cache a NIL response.  Either way our server is always going to have one because it gets calculated on APPEND.
>>  
>> Bron.
>>  
>>  
>> --
>>   Bron Gondwana, CEO, Fastmail Pty Ltd
>>   brong@fastmailteam.com
>>  
>>  
>> _______________________________________________
>> Extra mailing list 
>> Extra@ietf.org 
>> https://www.ietf.org/mailman/listinfo/extra 
> _______________________________________________
> Extra mailing list
> Extra@ietf.org
> https://www.ietf.org/mailman/listinfo/extra
> 

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