RE: [tcpm] feedcback on tcp-secure-05: suggested text
"Anantha Ramaiah \(ananth\)" <ananth@cisco.com> Tue, 18 July 2006 19:55 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G2vfP-0005W8-Ol; Tue, 18 Jul 2006 15:55:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G2vfN-0005Vq-RK for tcpm@ietf.org; Tue, 18 Jul 2006 15:55:37 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G2v8k-000292-D4 for tcpm@ietf.org; Tue, 18 Jul 2006 15:21:54 -0400
Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G2v0Z-0003E1-66 for tcpm@ietf.org; Tue, 18 Jul 2006 15:13:29 -0400
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-3.cisco.com with ESMTP; 18 Jul 2006 12:13:27 -0700
X-IronPort-AV: i="4.06,255,1149490800"; d="scan'208"; a="434990782:sNHT28710812"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-4.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k6IJDQGo013147; Tue, 18 Jul 2006 12:13:26 -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 k6IJDQJk024788; Tue, 18 Jul 2006 12:13:26 -0700 (PDT)
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); Tue, 18 Jul 2006 12:13:25 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [tcpm] feedcback on tcp-secure-05: suggested text
Date: Tue, 18 Jul 2006 12:13:24 -0700
Message-ID: <0C53DCFB700D144284A584F54711EC5801DF8A70@xmb-sjc-21c.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [tcpm] feedcback on tcp-secure-05: suggested text
Thread-Index: AcaqmCopm8mtspm1S8ShhoMXTZPpQwAAsg/Q
From: "Anantha Ramaiah (ananth)" <ananth@cisco.com>
To: Ted Faber <faber@ISI.EDU>, tcpm@ietf.org
X-OriginalArrivalTime: 18 Jul 2006 19:13:25.0991 (UTC) FILETIME=[3EAFEF70:01C6AA9E]
DKIM-Signature: a=rsa-sha1; q=dns; l=1677; t=1153250006; x=1154114006; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=ananth@cisco.com; z=From:=22Anantha=20Ramaiah=20\(ananth\)=22=20<ananth@cisco.com> |Subject:RE=3A=20[tcpm]=20feedcback=20on=20tcp-secure-05=3A=20suggested=20text; X=v=3Dcisco.com=3B=20h=3D5Xe8g444+k3iNGnfr28YXh/yDQA=3D; b=kZOAViokTfd5xA8hwNyskD9tcBdFYK5QtXY799RPHEBSFI2jEUStknB1PH56TJx8J/GDyFf5 EVQQHZ2CiAlxvTHyzws1juaN+0kLKerj6QJgRaDDiGvP5+Cs4r1FdMEy;
Authentication-Results: sj-dkim-4.cisco.com; header.From=ananth@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: -2.6 (--)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Cc:
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
Ted,
The text looks good. A small suggestion which I think would draw the
line even better :
(Just taking an example : Pls see the text in quotes inserted the last
paragraph from your proposal below]
In any case, this RFC details only part of a complete strategy to
prevent off-path attackers from disrupting services that use TCP. "This
document focusses on dealing with some TCP segment based attack vectors
and not other protocol packets"
Administrators and implementors should consider the other attack vectors
and determine appropriate mitigations in securing their systems.
Since this document isn't a "cookbook" of all possible attacks on the
TCP layer and the mitigations, saying something of this sort would help
in containing the scope of the document better.
It is just my opinion I also think that there is scope of re-wording the
sentence better.
Thanks,
-Anantha
> -----Original Message-----
> From: Ted Faber [mailto:faber@ISI.EDU]
> Sent: Tuesday, July 18, 2006 11:19 AM
> To: tcpm@ietf.org
> Subject: Re: [tcpm] feedcback on tcp-secure-05: suggested text
>
> I've attached some text that I'd like to propose for the
> Security Considerations secition of this draft in an effort
> to make its scope clear and hopefully address some of Joe's
> concerns about ICMP.
>
> This is just me, a participant, making the suggestion.
>
> Text is attached. Let me know what you think.
>
> --
> Ted Faber
> http://www.isi.edu/~faber PGP:
> http://www.isi.edu/~faber/pubkeys.asc
> Unexpected attachment on this mail? See
> http://www.isi.edu/~faber/FAQ.html#SIG
>
_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www1.ietf.org/mailman/listinfo/tcpm
- RE: [tcpm] feedcback on tcp-secure-05: suggested … Anantha Ramaiah (ananth)