[tcpm] ICMP attacks draft (issue 1): hard errors -> soft errors (in synchronized states)

Fernando Gont <fernando@gont.com.ar> Fri, 23 September 2005 11:20 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EIlbF-0005Zv-Bw; Fri, 23 Sep 2005 07:20:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EIlbA-0005SZ-J0 for tcpm@megatron.ietf.org; Fri, 23 Sep 2005 07:20:13 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08331 for <tcpm@ietf.org>; Fri, 23 Sep 2005 07:20:11 -0400 (EDT)
Received: from server.frh.utn.edu.ar ([170.210.17.146] ident=qmailr) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EIlhX-0003Tt-6X for tcpm@ietf.org; Fri, 23 Sep 2005 07:26:50 -0400
Received: (qmail 22667 invoked from network); 23 Sep 2005 11:19:16 -0000
Received: from unknown (HELO fgont.gont.com.ar) (gont-fernando@200.70.176.40) by server.frh.utn.edu.ar with SMTP; 23 Sep 2005 11:19:16 -0000
Message-Id: <6.2.0.14.0.20050923075214.0428faa8@pop.frh.utn.edu.ar>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14
Date: Fri, 23 Sep 2005 07:58:58 -0300
To: tcpm@ietf.org
From: Fernando Gont <fernando@gont.com.ar>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 2.9 (++)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Subject: [tcpm] ICMP attacks draft (issue 1): hard errors -> soft errors (in synchronized states)
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org

Folks

I will separate the discussion into different issues, so that it is easier 
to get consensus on the different parts of the draft.

Issue 1 is: When a so-called ICMP "hard error" is received for a connection 
in any of the synchronized states (ESTABLISHED and so on), treat the error 
message as a soft error (i.e., do NOT abort the corresponding connection).

This improves TCP's robustness. In the event the error condition does not 
disappear in the near term, the connection will time out, anyway.

Note: ICMP is *unreliable*: you cannot depend on it, anyway.

All BSD-derived and Mentat-derived implementations have been doing this for 
at least fifteen years.

Comments?

Kindest regards,

--
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@acm.org






_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www1.ietf.org/mailman/listinfo/tcpm