Re: [RPSEC] Feedback on draft-behringer-bgp-session-req-01

Stephen Kent <kent@bbn.com> Fri, 22 June 2007 16:07 UTC

Return-path: <rpsec-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I1lfH-0004cr-Tj; Fri, 22 Jun 2007 12:07:15 -0400
Received: from rpsec by megatron.ietf.org with local (Exim 4.43) id 1I1lfG-0004cZ-00 for rpsec-confirm+ok@megatron.ietf.org; Fri, 22 Jun 2007 12:07:14 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I1lfF-0004cO-Mm for rpsec@ietf.org; Fri, 22 Jun 2007 12:07:13 -0400
Received: from mx11.bbn.com ([128.33.0.80]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I1lfE-0003AV-GV for rpsec@ietf.org; Fri, 22 Jun 2007 12:07:13 -0400
Received: from dhcp89-089-071.bbn.com ([128.89.89.71]) by mx11.bbn.com with esmtp (Exim 4.60) (envelope-from <kent@bbn.com>) id 1I1lfD-0000tY-69; Fri, 22 Jun 2007 12:07:12 -0400
Mime-Version: 1.0
Message-Id: <p0624050ac2a19691e536@[128.89.89.71]>
In-Reply-To: <467BDADD.3000406@isi.edu>
References: <467AE0B5.2080104@isi.edu> <C35ADD020AEBD04383C1F7F644227FDF03E688C4@xmb-sjc-227.amer.cisco.com> <467BDADD.3000406@isi.edu>
Date: Fri, 22 Jun 2007 11:10:40 -0400
To: Joe Touch <touch@ISI.EDU>
From: Stephen Kent <kent@bbn.com>
Subject: Re: [RPSEC] Feedback on draft-behringer-bgp-session-req-01
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Cc: "Barry Greene \(bgreene\)" <bgreene@cisco.com>, rpsec@ietf.org
X-BeenThere: rpsec@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Protocol Security Requirements <rpsec.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rpsec>, <mailto:rpsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/rpsec>
List-Post: <mailto:rpsec@ietf.org>
List-Help: <mailto:rpsec-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rpsec>, <mailto:rpsec-request@ietf.org?subject=subscribe>
Errors-To: rpsec-bounces@ietf.org

At 7:21 AM -0700 6/22/07, Joe Touch wrote:
>Content-Type: multipart/signed; micalg=pgp-sha1;
>	protocol="application/pgp-signature";
>	boundary="------------enigB1D3AB5BCF55D129E9BDB950"
>
>Hi, Barry,
>
>Barry Greene (bgreene) wrote:
>>  I guess we have differing views on the definition of "security." If I
>>  can classify based on a policy which provides me more resistance from
>>  attacks, then that is a "security tool." Hence, GTSM is a security tool.
>
>GTSM could be classified as a security tool, but it is not IP layer
>security. It is a mechanism an endpoint can use to increase its
>resistance to attack, as you note, but it doesn't particularly protect
>any single protocol layer or header.
>
>Joe


GTSM also has a very limited (although important) scope, since it is 
generally applicable only in contexts where one can predict the 
appropriate TTL value for legitimate traffic (and where active 
attacks on the path the traffic is traversing are not assumed to be 
viable).

Steve


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