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

Jari Arkko <jari.arkko@piuha.net> Thu, 18 February 2010 19:03 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C8F3128C0E2 for <tcpm@core3.amsl.com>; Thu, 18 Feb 2010 11:03:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.416
X-Spam-Level:
X-Spam-Status: No, score=-2.416 tagged_above=-999 required=5 tests=[AWL=0.183, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HaAoVKVX4lqj for <tcpm@core3.amsl.com>; Thu, 18 Feb 2010 11:03:11 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 8A6113A8039 for <tcpm@ietf.org>; Thu, 18 Feb 2010 11:03:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 9EBC42D287 for <tcpm@ietf.org>; Thu, 18 Feb 2010 21:04:54 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LvqjKvOlxUXQ for <tcpm@ietf.org>; Thu, 18 Feb 2010 21:04:54 +0200 (EET)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 333442D257 for <tcpm@ietf.org>; Thu, 18 Feb 2010 21:04:54 +0200 (EET)
Message-ID: <4B7D8F55.90406@piuha.net>
Date: Thu, 18 Feb 2010 21:04:53 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: tcpm@ietf.org
References: <20100218175622.61BB028C2E3@core3.amsl.com> <2002D196-D83C-4B44-870C-8E9A94D2D640@nokia.com> <4B7D8B9F.1010608@piuha.net>
In-Reply-To: <4B7D8B9F.1010608@piuha.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: [tcpm] TCPM and draft-ietf-tcpm-icmp-attacks
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Feb 2010 19:03:12 -0000

Hi,

This document was recently in IESG review. My opinion is that the 
document should be approved as an RFC. Thanks for writing it.

However, I would like to note the following text from the document:

 The consensus of the TCPM WG (TCP Maintenance and
 Minor Extensions Working Group) was to document this widespread
 implementation of nonstandard TCP behavior but to not change the TCP
 standard.

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". 
For at least some of the techniques described in this draft, they are 
generally accepted and widely implemented on key implementations. I ask 
what the reason is for divorcing IETF standards from established best 
practices and actual running code? TCP RFCs are not sacred documents, 
they should reflect what we want our implementations to do. But maybe 
there are important use cases for the actual standard TCP behavior in 
this space, just that I don't know about them. Please educate me about 
the background for this decision.

Jari