Re: AD review of draft-ietf-imapapnd-rfc2088bis-03

> However, I realized that the server should still be allowed to return
> BYE and disconnect. So my final version is:
>
>    A "LITERAL-" compliant server that encounters a non-synchronizing
>    literal larger than 4096 bytes proceeds as described in
>    Section 4. If responding to an APPEND command, the tagged BAD
>    response MUST contains the TOOBIG response code [RFC4469].
>    If responding with untagged BYE response, it SHOULD include
>    the TOOBIG response code.

I think that's better than how we started, by leaving the actual
advice in one place (Section 4), and referring to it.

I still think Section 4 could be better about explaining why it would
(or wouldn't) be useful to send BAD before flushing the literal and
the rest of the command, rather than after, but no one else has piped
up so we'll go from here.

I'll request last call now.

Barry

_______________________________________________
imapext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/imapext