Re: [imapext] Alissa Cooper's No Objection on draft-ietf-imapapnd-appendlimit-extension-08: (with COMMENT)
S Moonesamy <sm+ietf@elandsys.com> Tue, 05 January 2016 23:51 UTC
Return-Path: <sm@elandsys.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 11A281ACE23; Tue, 5 Jan 2016 15:51:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level:
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01, 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 erJwboIjBmWz; Tue, 5 Jan 2016 15:51:15 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 44DD81ACD3F; Tue, 5 Jan 2016 15:51:15 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.227.85.115]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id u05Notq5011223 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 5 Jan 2016 15:51:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1452037870; x=1452124270; bh=0Adoozebtqnf7YwX5SEaeP5qVhyutDfPbz2/Q3LKdNo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=4HLnwNWCt92riEw4lD/yTrteTHznPXflJxiXzOuPCQBs421fSGxwoBTWVhCzNhoju FDcZ7JHnR3V2/K0K4egk/WPeiqjjIphMjQB0n9Lxngl4dWQE8RN9JZFpIWK2ojR33H RdcBCTXoCHdRQAOmTEEwcAYjnuRIJG4XQER74atI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1452037870; x=1452124270; i=@elandsys.com; bh=0Adoozebtqnf7YwX5SEaeP5qVhyutDfPbz2/Q3LKdNo=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=bVcPlymEDTflKOdQ8nq/30+9XNGu5Abm/Y7JdFU5kRgRLPxc4xZ6k2t+6J+Mie95M O0UNKNKbwUgdwECX8o65fTiJx+8kcWirElCW7MlAO/P9mFUOo6FLHadCQ89HI5y+/9 d9IS4LPz5NjzmCWwnA4+6iYPe4V/8VC+Pq1v4v/I=
Message-Id: <6.2.5.6.2.20160105153055.0f34f228@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 05 Jan 2016 15:50:46 -0800
To: imapext@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <20160105191025.31613.33420.idtracker@ietfa.amsl.com>
References: <20160105191025.31613.33420.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/imapext/I0Z5o_loFvtM8UUUJf0RZYXl3rQ>
Cc: draft-ietf-imapapnd-appendlimit-extension@ietf.org, Alissa Cooper <alissa@cooperw.in>, mapapnd-chairs@ietf.org, iesg@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: Tue, 05 Jan 2016 23:51:16 -0000
Hello, At 11:10 05-01-2016, Alissa Cooper wrote: >= 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. I'll suggest writing the first sentence as follows: In this case the client can get an APPENDLIMIT value by either issuing a STATUS or a LIST command. I avoided including a normative recommendation to keep it simple. There is the following in Section 6: "because the client knows the limit and should not even be trying to send such commands, a server might consider even a single attempt to be abusive, and terminate the IMAP connection straight away." I'll suggest some text: By looking at the upload size advertised by the IMAP server a client can avoid trying to APPEND mail more than the advertised limit." Regards, S. Moonesamy (as document shepherd)
- [imapext] Alissa Cooper's No Objection on draft-i… Alissa Cooper
- Re: [imapext] Alissa Cooper's No Objection on dra… S Moonesamy
- Re: [imapext] Alissa Cooper's No Objection on dra… S Moonesamy
- Re: [imapext] Alissa Cooper's No Objection on dra… Jayantheesh S B