Re: [tcpm] TCPM and draft-ietf-tcpm-icmp-attacks

[Fernando Gont <[e-mail]>]

Joe Touch wrote:

>> This would seem to imply that the TCPM WG has decided to deviate from
>> the old IETF operating principle of "rough consensus and running code".
> 
> The short answer is that there wasn't rough consensus for these changes
> in the WG, as explained in the note in the text.

I believe that the short answer is that *you* have done everything that
was available to stop this document (and others) from moving forward.
Requesting text to be added, then requesting the very same text to be
taken out of the I-D. And at some point, we ended up changing the track,
changing text, and changing whatever was out there just with the hope
that you'd be happy, we'd stop wasting energy, and the document would be
eventually published.

It is interesting to note that one of the issues with with you have
trashed this I-D is that it used vocabulary that could be taken as the
draft "recommending" the described counter-measures. Yet, as the editor
of the last version of the (close to infamous) TCP A-O effort, you have
crafted this text:

"  There are other mechanisms proposed to reduce the impact
   of ICMP attacks by further validating ICMP contents and changing the
   effect of some messages based on TCP state"

Note the use of the term "proposed". (that's specifically what I'm
referring to).

I believe this is the height of irony.

Thanks,
-- 
Fernando Gont
e-mail: [e-mail] || [e-mail]
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1