IETF Logo Mail Archive

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

Jamie Nicolson <nicolson@google.com> Fri, 04 December 2015 18:36 UTC

Return-Path: <nicolson@google.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 7DB2D1B31FA for <imapext@ietfa.amsl.com>; Fri, 4 Dec 2015 10:36:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level:
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 Fkg3Es7eO_R8 for <imapext@ietfa.amsl.com>; Fri, 4 Dec 2015 10:36:03 -0800 (PST)
Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B1331B31F9 for <imapext@ietf.org>; Fri, 4 Dec 2015 10:36:02 -0800 (PST)
Received: by iofh3 with SMTP id h3so125317956iof.3 for <imapext@ietf.org>; Fri, 04 Dec 2015 10:36:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=+CEMMdoxVD3q0veBrHsyjeAVhHf0fnCSC51pg1yRlPQ=; b=lzdZk3iZZcdeTcvS61cqDY5Cs8HDAyxHPXJJxm8OgQ4WNn0OyQlrupR37LKqi2xIy8 bAMey7Xr3TH5GMKDSn5jEgvtGfmb85HOYG87DHX7nWEMKR7N8kNLoX7K0IubyYJr20Os x+BNMp/RxEBKjAC1TcY3FkRL2OTxjD4bBu90g3wTYmPDla0yfREg3i04iIe5GHua9/7u hX8P3XDJU51TvJV5Ki+VnWdY8QhP2OYpF0jWjEnOvoFyUJfG19KWfTLvFqPHh3M23zDd X95C0HP/e0T8t9LgPIzlOY//YJ5gChCEipPd59wbSZewpF6D1rIiu5ZszBNj7Cl9yrzq 4LVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=+CEMMdoxVD3q0veBrHsyjeAVhHf0fnCSC51pg1yRlPQ=; b=SOON9bEsHEGO3PsfJzLG3R3g+NWM6iZ/NV/nUqqzBLoSl85rlUsvIvSGGxRLgSGRNb lW2z5sYqeHgxVH5KYbLKZA57hvo1BWsm2HEHy00OaIQ/rmHkxlvszRduiuNb+RHeZ/0O Ju+iBVs/M4q1RS9RV15fGzYsGy+kr2jHY1Jij9yOhh8f0wE8+4BSt47mvZrgEk3Mij3g z78xQPNS3NM4lUD+6j3mx8BaApicYtKhWUZTaOTnLStOaksjJkQEo9I9RvpEebNVWj4d 4LnAnlBxopW9zLlW9uRYAnGz2qzivMjFfqPugZIPhB/j8qXax323aer//eG2F0wmsE4k 6TWQ==
X-Gm-Message-State: ALoCoQlF+hYs0EW1Sq5594pquWpL3V2LhPJ/MGzWjTXjyBykOnSi4tgSagMW62LzSIYPxHIS44Z0
X-Received: by 10.107.159.199 with SMTP id i190mr14373675ioe.29.1449254162242; Fri, 04 Dec 2015 10:36:02 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.62.14 with HTTP; Fri, 4 Dec 2015 10:35:32 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20151204031930.103a4fd0@elandnews.com>
References: <6.2.5.6.2.20151204031930.103a4fd0@elandnews.com>
From: Jamie Nicolson <nicolson@google.com>
Date: Fri, 04 Dec 2015 10:35:32 -0800
Message-ID: <CACU8CfTVYYWjwPUQNLuAuh-sb-VRRQ7Vxw1BpPK6hjMY7wAzzg@mail.gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary="001a1140fb3e87f68d052616c708"
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/3KSbGom_me42JfXPYVN5QvgTB7E>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, "imapext@ietf.org" <imapext@ietf.org>
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, 04 Dec 2015 18:36:04 -0000

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.

On Fri, Dec 4, 2015 at 3:25 AM, S Moonesamy <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
> https://www.ietf.org/mailman/listinfo/imapext
>

v2.23.0 | Report a Bug | By Email