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

S Moonesamy <[email protected]> Tue, 05 Jan 2016 15:50:46 -0800
Newsgroups gmane.ietf.imapext
Message-ID <[email protected]>
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 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/imapext