Re: [Extra] imap4rev2: RFC5182 SEARCHRES

Michael Slusarz <michael.slusarz@open-xchange.com> Wed, 21 November 2018 18:16 UTC

Return-Path: <michael.slusarz@open-xchange.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 D8450130F2B for <extra@ietfa.amsl.com>; Wed, 21 Nov 2018 10:16:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=open-xchange.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 0rbKr6GKR5Vg for <extra@ietfa.amsl.com>; Wed, 21 Nov 2018 10:16:40 -0800 (PST)
Received: from mx4.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8C59130E7E for <extra@ietf.org>; Wed, 21 Nov 2018 10:16:39 -0800 (PST)
Received: from open-xchange.com (imap.open-xchange.com [10.20.30.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx4.open-xchange.com (Postfix) with ESMTPS id 8D8D46A26B for <extra@ietf.org>; Wed, 21 Nov 2018 19:16:37 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1542824197; bh=fXoBOFSiqQUoSEDPvLodmSiHXgTc19GW2VjLTGh/K9M=; h=Date:From:To:In-Reply-To:References:Subject:From; b=8hvx/Zwm4fBrkge02JbEaQiSa/RDyvC1lr5Wt+ORfzT41KqS1SWz55nIy/PsdbTm6 7a5l2j/0aRJCGPvzgCYD/XnHYgAP2kPDDx5D3LbAE4PNTdKjn+SuREBq8tCNOkkmNe uoSVytU14+OtKapaFOLk+JtNHzmI87FJw4WuZyDf3aGdqgf/242vZX+AcHhsKP/MFA 2JDlfgF+nh+j9IstW3CJSBBEQ/POZJ3wrztLDhdFFF1eKlmFIaSvQixR3vzifc9czM /f+JLEMF6cU3JPneeokIl8tC5xn+P13xyiyFvBNzN6ih2Pot0xRiWrQCzPKVGf+LtY /N9TDKgIXOGsA==
Received: from appsuite-gw1.open-xchange.com (appsuite-gw1.open-xchange.com [10.20.28.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by open-xchange.com (Postfix) with ESMTPSA id 8586E3C06FD for <extra@ietf.org>; Wed, 21 Nov 2018 19:16:37 +0100 (CET)
Date: Wed, 21 Nov 2018 11:16:37 -0700 (MST)
From: Michael Slusarz <michael.slusarz@open-xchange.com>
To: extra@ietf.org
Message-ID: <1309404114.9749.1542824197488@appsuite.open-xchange.com>
In-Reply-To: <F2CD4692-B570-4B55-A5FF-48E9CE28822E@oracle.com>
References: <b8a1d46f-5766-4804-bbb9-25699345ca6e@sloti7d1t02> <F2CD4692-B570-4B55-A5FF-48E9CE28822E@oracle.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_9748_793789840.1542824197478"
X-Priority: 3
Importance: Medium
X-Mailer: Open-Xchange Mailer v7.10.0-Rev20
X-Originating-Client: open-xchange-appsuite
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/dyCJfDo2RgGeQaYK5Rks8tx95Js>
Subject: Re: [Extra] imap4rev2: RFC5182 SEARCHRES
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: Wed, 21 Nov 2018 18:16:45 -0000

[FYI: I'll be replying to all of Bron's imap4rev2 messages with the "official" Dovecot response.  Don't worry - the feedback is from people much smarter than me - I'm mainly in charge of being the messenger!]

SEARCHRES is already implemented by Dovecot (has been for awhile).  No objection to including in imap4rev2.

Only question - similar to Chris' - is what the usage is on the client side?  SEARCHRES doesn't seem useful for non-pipelining clients, which is the way the vast majority of IMAP libraries are implemented, at least the ones I have looked at.  e.g. code that programatically calls a search() function, then uses the response from search() and does a fetch() function or whatever.

FWIW, I included a SEARCHRES example in PREVIEW draft in hopes of demonstrating how this extension can be practically useful.  See https://tools.ietf.org/html/draft-ietf-extra-imap-fetch-preview-00#page-8

michael


> On November 20, 2018 at 2:12 PM Chris Newman <chris.newman@oracle.com>; wrote:
> 
> 
>     We've implemented this extension and it's not difficult to implement on the server side so I'm in favor of including this. I'd be interested in a client implementer's perspective.
> 
>     - Chris
> 
>     On 8 Nov 2018, at 3:27, Bron Gondwana wrote:
> 
>         > >         This is one of the open issues from imap4rev2 - which extensions should be part of the mandatory baseline.
> > 
> >         In favour - it's useful to compose actions.
> > 
> >         Against - it's not widely implemented or used.
> > 
> >         Arguments for and against in response to this please.
> > 
> >         Cheers,
> > 
> >         Bron.
> > 
> >         -- 
> >           Bron Gondwana, CEO, FastMail Pty Ltd
> >           brong@fastmailteam.com
> > 
> > 
> > 
> >     > 
>         > > 
> >     > 
>         > > 
> >         _______________________________________________
> >         Extra mailing list
> >         Extra@ietf.org
> >         https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_extra&d=DwICAg&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=K_BObr5Kfkr3rxt1oBPF9KFiEU3xl9LcD2OOJG3TXfI&m=6krI1FgmWhZv2LqblI2h4VuwuAN9JX254RcYg-ZMIGE&s=tOzMc_3golA1EPLg7hmfq0_-klVUFWcd4k9fF17iwwU&e=
> > 
> >     >     _______________________________________________
>     Extra mailing list
>     Extra@ietf.org
>     https://www.ietf.org/mailman/listinfo/extra
>