Re: [imapext] Alissa Cooper's No Objection on draft-ietf-imapapnd-appendlimit-extension-08: (with COMMENT)

Jayantheesh S B <j.sb@sea.samsung.com> Thu, 07 January 2016 17:23 UTC

Return-Path: <j.sb@sea.samsung.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 D044F1A9104; Thu, 7 Jan 2016 09:23:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.4
X-Spam-Level:
X-Spam-Status: No, score=0.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_EXTNSN=2.3, RCVD_IN_DNSWL_NONE=-0.0001] 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 uxgBKd-nKU-Z; Thu, 7 Jan 2016 09:23:05 -0800 (PST)
Received: from wguard01.sdsamerica.net (wguard01.sdsamerica.net [206.67.236.191]) by ietfa.amsl.com (Postfix) with ESMTP id 714F41A90E0; Thu, 7 Jan 2016 09:23:05 -0800 (PST)
From: Jayantheesh S B <j.sb@sea.samsung.com>
To: S Moonesamy <sm+ietf@elandsys.com>, Alissa Cooper <alissa@cooperw.in>, The IESG <iesg@ietf.org>
Thread-Topic: [imapext] Alissa Cooper's No Objection on draft-ietf-imapapnd-appendlimit-extension-08: (with COMMENT)
Thread-Index: AQHRR/RlWF+Av3cVr0WWi4uFPEm6WJ7vQ4yAgAEMadA=
Date: Thu, 07 Jan 2016 17:23:03 +0000
Message-ID: <13d76c6a27ff4d05a48d1cf39e978d27@SEAMBX01.sea.samsung.com>
References: <20160105191025.31613.33420.idtracker@ietfa.amsl.com> <6.2.5.6.2.20160106121402.0d584cd0@elandnews.com>
In-Reply-To: <6.2.5.6.2.20160106121402.0d584cd0@elandnews.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Received-SPF: none
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/-BWyjRCoWU93sq4lWzLsq7_gncs>
Cc: "draft-ietf-imapapnd-appendlimit-extension@ietf.org" <draft-ietf-imapapnd-appendlimit-extension@ietf.org>, "imapext@ietf.org" <imapext@ietf.org>, "imapapnd-chairs@ietf.org" <imapapnd-chairs@ietf.org>
Subject: Re: [imapext] Alissa Cooper's No Objection on draft-ietf-imapapnd-appendlimit-extension-08: (with COMMENT)
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: Thu, 07 Jan 2016 17:23:07 -0000

Dear All,

Updated the document with the below text proposed by SM.

NEW
    In this case the client can get an APPENDLIMIT value by either issuing
    a STATUS or a LIST command.

    By looking at the upload size advertised by the IMAP server a client
    can avoid trying to APPEND mail more than the advertised limit.
END

Regards,
Jay
-----Original Message-----
From: imapext [mailto:imapext-bounces@ietf.org] On Behalf Of S Moonesamy
Sent: Wednesday, January 06, 2016 3:21 PM
To: Alissa Cooper; The IESG
Cc: draft-ietf-imapapnd-appendlimit-extension@ietf.org; imapext@ietf.org; imapapnd-chairs@ietf.org
Subject: Re: [imapext] Alissa Cooper's No Objection on draft-ietf-imapapnd-appendlimit-extension-08: (with COMMENT)

Hi Alissa,
At 11:10 05-01-2016, Alissa Cooper wrote:
>The document, along with other ballot positions, can be found here:
>https://datatracker.ietf.org/doc/draft-ietf-imapapnd-appendlimit-extens
>ion/
>
>
>
>----------------------------------------------------------------------
>COMMENT:
>----------------------------------------------------------------------
>
>It's unusual to see author names without first initials in the document 
>header. Not sure if that was intentional but seems like it should be 
>fixed (assuming the authors have both first names and surnames).

It is a mistake.  It will be fixed in the next revision of the draft.

>= Section 2 =
>
>"In this case the client SHOULD get an APPENDLIMIT value by issuing a
>    STATUS or LIST command.
>
>    An IMAP client SHOULD be able to parse both formats.  By looking at
>    the upload size advertised by the IMAP server, a client MUST NOT try
>    to APPEND mail more than the advertised limit."
>
>The first and last normative requirements here seem too strict 
>considering that this extension basically allows an optimization. That 
>is, if a client decides not to find out the append limit for a 
>particular mailbox using STATUS or LIST, that doesn't seem to create 
>any particular problem. Likewise, it seems better for a client to avoid 
>sending an attachment larger than a known limit, but doing so doesn't 
>seem so problematic as to warrant a MUST NOT.

NEW
    In this case the client can get an APPENDLIMIT value by either issuing
    a STATUS or a LIST command.

    By looking at the upload size advertised by the IMAP server a client
    can avoid trying to APPEND mail more than the advertised limit.
END

Regards,
S. Moonesamy (as document shepherd) 

_______________________________________________
imapext mailing list
imapext@ietf.org
https://www.ietf.org/mailman/listinfo/imapext