IETF Logo Mail Archive

Re: [imapext] IMAP4 non-synchronizing literals - draft-ietf-imapapnd-rfc2088bis-01

Alexey Melnikov <alexey.melnikov@isode.com> Fri, 05 February 2016 10:59 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 514821A1B79 for <imapext@ietfa.amsl.com>; Fri, 5 Feb 2016 02:59:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
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 NSYXmL2Av-Ko for <imapext@ietfa.amsl.com>; Fri, 5 Feb 2016 02:59:00 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id C10271A1B76 for <imapext@ietf.org>; Fri, 5 Feb 2016 02:59:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1454669940; d=isode.com; s=selector; i=@isode.com; bh=yhrabD3T8phM8M4xn20cJa6W0aFq/N6tXvSfQSd8qj8=; 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=Tt3M/q2ey3j02EyAG7mGU/+JA3R1vA0qUYg4Wt+Y9EkxTQ+aI73j/4LUmYHA737Wi6pN/z MxmyxpbiCINAmdv8mXGTPFLTqIGemHl58AkJlODbl9t83bZ1+Mr2BkD6Su9vXeNBO2rJMS N7w8NPTvh921eK2o3Ln9JrroXIawouo=;
Received: from [192.168.0.5] (cpc5-nmal20-2-0-cust24.19-2.cable.virginm.net [92.234.84.25]) by statler.isode.com (submission channel) via TCP with ESMTPSA id <VrSAcQBBx2Hx@statler.isode.com>; Fri, 5 Feb 2016 10:58:59 +0000
To: Jayantheesh S B <j.sb@sea.samsung.com>, "imapext@ietf.org" <imapext@ietf.org>
References: <6.2.5.6.2.20151204031930.103a4fd0@elandnews.com> <CACU8CfTVYYWjwPUQNLuAuh-sb-VRRQ7Vxw1BpPK6hjMY7wAzzg@mail.gmail.com> <5666FA20.3060308@isode.com> <56672B8D.5010609@teamaol.com> <32632fae99ba42028794d611b8e31b41@SEAMBX01.sea.samsung.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <56B4806F.6080603@isode.com>
Date: Fri, 05 Feb 2016 10:58:55 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
In-Reply-To: <32632fae99ba42028794d611b8e31b41@SEAMBX01.sea.samsung.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/mrQfjBXWlpQgWrCVGzcdCi_hXcs>
Cc: "S Moonesamy (sm+ietf@elandsys.com)" <sm+ietf@elandsys.com>
Subject: Re: [imapext] IMAP4 non-synchronizing literals - draft-ietf-imapapnd-rfc2088bis-01
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2016 10:59:02 -0000

Hi Jay,

On 28/01/2016 21:02, Jayantheesh S B wrote:
> Hi Alexey,
> 
> I agree with not to restrict this with only APPEND command.

Ok, I will update the draft to apply the limit to all commands.

> All,
> 
>  
> 
> Kindly share your review comments for this
> draft-ietf-imapapnd-rfc2088bis-01.
> 
>  
> 
> Regards,
> 
> Jay
> 
> *From:*imapext [mailto:imapext-bounces@ietf.org] *On Behalf Of *Stu Brandt
> *Sent:* Tuesday, December 08, 2015 2:12 PM
> *To:* imapext@ietf.org
> *Subject:* Re: [imapext] IMAP4 non-synchronizing literals -
> draft-ietf-imapapnd-rfc2088bis-01
> 
>  
> 
> Alexey -
> 
> I agree with Jamie...restricting to just APPEND (and MULTIAPPEND, and
> CATENATE) seems unnecessary.   Thinking of potential new extensions
> (e.g. REPLACE), there could likely be additional cases where the
> motivation for LITERAL- applies.
> 
> - Stu
> 
> On 12/8/15 10:41 AM, Alexey Melnikov wrote:
> 
>     On 04/12/2015 18:35, Jamie Nicolson wrote:
> 
>     Apologies if this was discussed before, but why limit the LITERAL-
>     size restriction to APPEND? Why not just make it apply to all
>     commands: any literal > 4KB must be sent as a synchronizing literal.
>     This might be easier for clients and servers to implement, so that
>     the code for processing literals doesn't need to know which command
>     it belongs to. The impact on other commands would be very limited,
>     since they will almost never need to send a literal that large.
> 
>     I personally don't mind if it applies to all commands. Other thoughts?
> 
>      
> 
>     On Fri, Dec 4, 2015 at 3:25 AM, S Moonesamy <sm+ietf@elandsys.com
>     <mailto:sm+ietf@elandsys.com>> wrote:
> 
>     Hello,
> 
>     The second draft on our charter about "IMAP4 non-synchronizing
>     literals" [1].  Could the working group please review
>     draft-ietf-imapapnd-rfc2088bis-01 and send comments to the mailing list?
> 
>     Regards,
>     S. Moonesamy (as imapapdb WG Chair)
> 
>     1. https://tools.ietf.org/html/draft-ietf-imapapnd-rfc2088bis-01
> 
>     _______________________________________________
>     imapext mailing list
>     imapext@ietf.org <mailto:imapext@ietf.org>
>     https://www.ietf.org/mailman/listinfo/imapext
> 
>      
> 
> 
> 
> 
>     _______________________________________________
> 
>     imapext mailing list
> 
>     imapext@ietf.org <mailto:imapext@ietf.org>
> 
>     https://www.ietf.org/mailman/listinfo/imapext
> 
> 
> 
> 
> 
>     _______________________________________________
> 
>     imapext mailing list
> 
>     imapext@ietf.org <mailto:imapext@ietf.org>
> 
>     https://www.ietf.org/mailman/listinfo/imapext
> 
>  
> 
> 
> 
> _______________________________________________
> imapext mailing list
> imapext@ietf.org
> https://www.ietf.org/mailman/listinfo/imapext
>

v2.23.0 | Report a Bug | By Email