Re: Kathleen Moriarty's No Objection on draft-ietf-imapapnd-appendlimit-extension-08: (with COMMENT)
Alexey Melnikov <[email protected]> Sun, 10 Jan 2016 13:00:07 +0000
| Newsgroups | gmane.ietf.imapext |
|---|---|
| Message-ID | <[email protected]> |
Hi Barry, On 9 Jan 2016, at 22:27, Barry Leiba <[email protected]> wrote: >> We are fine with the proposed text. We will update the draft with this >> text and release a new version (10). > > Great; thanks. I'd like to hear from a couple of others to make sure > it's OK with a few more people. Alexey, SM, can the two of you weigh > in? Changes in -09 and -10 look good to me. > > Barry > >> -----Original Message----- >> From: imapext [mailto:[email protected]] On Behalf Of Barry Leiba >> Sent: Thursday, January 07, 2016 7:31 PM >> To: [email protected]; [email protected] >> Cc: [email protected]; The IESG; SM >> Subject: Re: [imapext] Kathleen Moriarty's No Objection on draft-ietf-imapapnd-appendlimit-extension-08: (with COMMENT) >> >> Authors and working group: >> In light of this discussion, I suggest that we replace the content of the Security Considerations section with this: >> >> NEW >> This extension provides additional information that cooperative >> clients can use as an optimization, and does not introduce new >> security concerns. This extension does not address abusive clients >> that intend to consume server resources, and servers will still have >> to take action to disconnect and/or restrict access to clients that >> exhibit abusive behavior. >> END >> >> Please comment, and if there are no objections, please make the change in another revision. Thanks. >> >> Barry >> >>> On Thu, Jan 7, 2016 at 9:32 AM, Kathleen Moriarty <[email protected]> wrote: >>> I was just suggesting that you could cut out the scenario, leave the >>> last sentence and say it's because of a possible attack on resources, >>> 'resources' being a short way of describing the scenario laid out. If >>> some other attack comes out that is mitigated in a similar way that >>> uses 'resources' in another way, you are covered. It also gets rid of >>> the extra text that I don't see as necessary. But leave it if you >>> think it's fine. >> >> _______________________________________________ >> imapext mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/imapext >> > > _______________________________________________ > imapext mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/imapext _______________________________________________ imapext mailing list [email protected] https://www.ietf.org/mailman/listinfo/imapext