IETF Logo Mail Archive

RE: [tcpm] tcpsecure: how strong to recommend?

"Anantha Ramaiah (ananth)" <ananth@cisco.com> Sun, 30 September 2007 06:45 UTC

Return-path: <tcpm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IbsYX-00032C-Ai; Sun, 30 Sep 2007 02:45:33 -0400
Received: from tcpm by megatron.ietf.org with local (Exim 4.43) id 1IbsYW-0002o8-01 for tcpm-confirm+ok@megatron.ietf.org; Sun, 30 Sep 2007 02:45:32 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IbsYQ-0001vZ-Ot for tcpm@ietf.org; Sun, 30 Sep 2007 02:45:26 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IbsYQ-0001LS-F5 for tcpm@ietf.org; Sun, 30 Sep 2007 02:45:26 -0400
X-IronPort-AV: E=Sophos;i="4.21,213,1188802800"; d="scan'208";a="227725838"
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 29 Sep 2007 23:45:25 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l8U6jPuJ032169; Sat, 29 Sep 2007 23:45:25 -0700
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l8U6jP1l010377; Sun, 30 Sep 2007 06:45:25 GMT
Received: from xmb-sjc-21c.amer.cisco.com ([171.70.151.176]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Sat, 29 Sep 2007 23:45:25 -0700
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Subject: RE: [tcpm] tcpsecure: how strong to recommend?
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Sat, 29 Sep 2007 23:45:24 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC580409FD54@xmb-sjc-21c.amer.cisco.com>
In-Reply-To: <46FF3FFA.4080207@isi.edu>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [tcpm] tcpsecure: how strong to recommend?
Thread-Index: AcgDKfBc9XS9XmQmRLuz33b4HNhLjQAAFg4Q
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: Joe Touch <touch@ISI.EDU>
X-OriginalArrivalTime: 30 Sep 2007 06:45:25.0525 (UTC) FILETIME=[7B308C50:01C8032D]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1127; t=1191134725; x=1191998725; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ananth@cisco.com; z=From:=20=22Anantha=20Ramaiah=20(ananth)=22=20<ananth@cisco.com> |Subject:=20RE=3A=20[tcpm]=20tcpsecure=3A=20how=20strong=20to=20recommend ? |Sender:=20; bh=JahDW6EA0ub8MTDqp1vPcZNyDioECr0U0CIBHZaVOWw=; b=cGgmMesezHenSpG07rL7w1kByWRYeGeIlDlkWmM9zsy+vPK74oG9hoiFtxQiIaLq5X9ykkhi GP+wqvL/akaiSECMtxgZC0lG6fGMBAeCLtb0gNBq0Zyy2YajZLZwqmh9;
Authentication-Results: sj-dkim-3; header.From=ananth@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: tcpm@ietf.org, mallman@icir.org
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>
Errors-To: tcpm-bounces@ietf.org

 
> > I will have to dis-agree to this since my viewpoint is 
> different. TCP 
> > secure adds robustness to the processing of certain TCP segments, 
> > which in turn helps to counter *some* spoofing attacks. 
> Calling it as 
> > an authentication scheme seems too far-fetched.
> 
> You are making an assertion about whether you believe the 
> packet is spoofed or not based on its content matching what 
> you expect from the true endpoint.
> 
> That is called authentication. Weak, but still authentication.

I am uncomfortable calling TCP secure as an authentication scheme. I
would love to hear what others have to say on this.

> 
> > WHEREAS
> > 
> > TCP MD5, IPsec etc., are meant to be wholesome 
> authentication schemes.
> > Also this requires additional complexity in both software 
> and hardware.
> 
> In EITHER hardware or software. Neither one requires 
> hardware. The level of additional complexity is commensurate 
> with the level of protection they afford.

Agreed. Actually, I wanted to say "it may require hardware assist" 

-Anantha


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

v2.23.0 | Report a Bug | By Email