Re: [RPSEC] BGP Security Requirements v08

Curtis Villamizar <curtis@occnc.com> Tue, 17 July 2007 14:27 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 1IAo0y-00058r-3z; Tue, 17 Jul 2007 10:27:00 -0400
Received: from rpsec by megatron.ietf.org with local (Exim 4.43) id 1IAo0q-00053m-C7 for rpsec-confirm+ok@megatron.ietf.org; Tue, 17 Jul 2007 10:26:52 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAo0o-00052u-FX for rpsec@ietf.org; Tue, 17 Jul 2007 10:26:51 -0400
Received: from 69.37.59.172.adsl.snet.net ([69.37.59.172] helo=harbor.brookfield.occnc.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IAo0n-0001IC-5v for rpsec@ietf.org; Tue, 17 Jul 2007 10:26:50 -0400
Received: from harbor.brookfield.occnc.com (harbor.brookfield.occnc.com [69.37.59.172]) by harbor.brookfield.occnc.com (8.13.6/8.13.6) with ESMTP id l6HEQJiK090507; Tue, 17 Jul 2007 10:26:19 -0400 (EDT) (envelope-from curtis@harbor.brookfield.occnc.com)
Message-Id: <200707171426.l6HEQJiK090507@harbor.brookfield.occnc.com>
To: Stephen Kent <kent@bbn.com>
From: Curtis Villamizar <curtis@occnc.com>
Subject: Re: [RPSEC] BGP Security Requirements v08
In-reply-to: Your message of "Mon, 16 Jul 2007 14:28:54 EDT." <p06240507c2c167b442a1@[128.89.89.71]>
Date: Tue, 17 Jul 2007 10:26:19 -0400
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: rpsec@ietf.org, Russ White <riw@cisco.com>
X-BeenThere: rpsec@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: curtis@occnc.com
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

In message <p06240507c2c167b442a1@[128.89.89.71]>
Stephen Kent writes:
>  
> I think the question is why, if the path info received by an "island 
> AS" has a number of unverified hops, is this path info useful, in a 
> security sense, to the AS that receives? How does the requirement to 
> send such info promote adoption of the protocol?
>  
> Steve


Because it is likely to be more reliable than information with no
authentication at all.

The major ISPs are fairly reliable at getting their internal routing
right so if the non-authenticating routers in the middle are entirely
in a set of ISPs that are known to generally not have breakins into
their own infrastructure.  For the purposes of commercial traffic
among other ISPs that want to distinguish their services as having
somewhat more reliable routing due to the use of authentication, there
is a great deal of value.

It may be optimistic to think that this value would be enough to give
any routing authentication sufficient value to gain critical mass in
the commercial world.  If there is no value for islands of deployment
except to authenticate within the island this is a non-starter from
day one in the commercial world.  If so it may be a non-starter at
router vendors without a very large influx of money from elsewhere,
such as government funding specifically for something that is not
being implemented because it will never get commercially deployed.  If
you are sure that the money is out there waiting for this spec to
publish, then fine.  Otherwise you may be wasting your time and ours
if the requirement to add value to disconnected islands is ignored.

That's just an opinion and I don't know how widely held it is today.
This might be a good question to ask at the WG meeting.

Curtis


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