GTSM-bis status and TCP RST resistance
Pekka Savola <pekkas@netcore.fi> Sat, 21 January 2006 13:05 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F0IR0-000433-7N; Sat, 21 Jan 2006 08:05:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F0IQy-00040H-9y for rtgwg@megatron.ietf.org; Sat, 21 Jan 2006 08:05:36 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29046 for <rtgwg@ietf.org>; Sat, 21 Jan 2006 08:04:07 -0500 (EST)
Received: from netcore.fi ([193.94.160.1]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F0IZt-0008Hl-O1 for rtgwg@ietf.org; Sat, 21 Jan 2006 08:14:51 -0500
Received: from netcore.fi (localhost [127.0.0.1]) by netcore.fi (8.12.8/8.12.8) with ESMTP id k0LD5PHa021994 for <rtgwg@ietf.org>; Sat, 21 Jan 2006 15:05:25 +0200
Received: from localhost (pekkas@localhost) by netcore.fi (8.12.8/8.12.8/Submit) with ESMTP id k0LD5OvO021991 for <rtgwg@ietf.org>; Sat, 21 Jan 2006 15:05:24 +0200
Date: Sat, 21 Jan 2006 15:05:24 +0200
From: Pekka Savola <pekkas@netcore.fi>
To: rtgwg@ietf.org
Message-ID: <Pine.LNX.4.64.0601211459270.21826@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Virus-Scanned: ClamAV 0.87.1/1246/Thu Jan 19 23:44:42 2006 on otso.netcore.fi
X-Virus-Status: Clean
X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.1.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on otso.netcore.fi
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Subject: GTSM-bis status and TCP RST resistance
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
Sender: rtgwg-bounces@ietf.org
Errors-To: rtgwg-bounces@ietf.org
Hi, It has been awfully quiet on the GTSMbis front lately (draft-ietf-rtgwg-rfc3682bis-05.txt). I think this is important work and we should be pushing it for Standards Track on high priority. One particular area where the doc may need more text is dealing with TCP RSTs. Do we assume that GTSM-enabled peers also send TCP RST's (related to GTSM-enabled sessions) with TTL=255? Note that if the system doesn't use TTL=255 for default (current IANA default TTL is 64), the host kernel will need a modification. Do we verify that on receipt? If not, how do we make GTSM resistant to TCP RST attacks? -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings _______________________________________________ Rtgwg mailing list Rtgwg@ietf.org https://www1.ietf.org/mailman/listinfo/rtgwg
- GTSM-bis status and TCP RST resistance Pekka Savola
- Re: GTSM-bis status and TCP RST resistance Alex Zinin