Re: [RPSEC] BGP Security Requirements v08

Robert Loomans <robertl@apnic.net> Tue, 17 July 2007 02:19 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 1IAceV-0001JT-2F; Mon, 16 Jul 2007 22:19:03 -0400
Received: from rpsec by megatron.ietf.org with local (Exim 4.43) id 1IAceU-0001JO-MP for rpsec-confirm+ok@megatron.ietf.org; Mon, 16 Jul 2007 22:19:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IAceU-0001JB-AV for rpsec@ietf.org; Mon, 16 Jul 2007 22:19:02 -0400
Received: from mint.apnic.net ([202.12.29.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IAceP-0002JM-Q7 for rpsec@ietf.org; Mon, 16 Jul 2007 22:19:02 -0400
Received: from [202.12.29.135] (dhcp135.apnic.net [202.12.29.135]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mint.apnic.net (Postfix) with ESMTP id 70C18D5F2D for <rpsec@ietf.org>; Tue, 17 Jul 2007 12:18:56 +1000 (EST)
Message-ID: <469C270F.6030102@apnic.net>
Date: Tue, 17 Jul 2007 12:18:55 +1000
From: Robert Loomans <robertl@apnic.net>
Organization: APNIC - http://www.apnic.net/
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.0.9) Gecko/20061207 Thunderbird/1.5.0.9 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: rpsec@ietf.org
Subject: Re: [RPSEC] BGP Security Requirements v08
References: <200707140126.l6E1QwYZ061559@harbor.brookfield.occnc.com>
In-Reply-To: <200707140126.l6E1QwYZ061559@harbor.brookfield.occnc.com>
X-Enigmail-Version: 0.95.2
OpenPGP: id=C6B3AE7E; url=http://robert.loomans.org/0xC6B3AE7E.asc
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
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

Curtis Villamizar wrote:
> In message <p06240528c2baa0b1241a@[128.89.89.71]>
> Stephen Kent writes:
>
>>> This is a pretty traditional and standard argument in routing protocol
>>> circles whenever extensions to a routing protocol are proposed--do we
>>> make it so older routers can at least forward the new information, or do
>>> we make it so it won't work in the presence of older routers? IMHO, it
>>> generally comes down to--is the information useful to routers on the
>>> other side of the nonsupporting router?
>>  
>> I agree that it is generally useful to have a router forward data 
>> that it can't use itself, but that a later router might be able to 
>> use.  However, I am not comfortable with a suggestion that if a 
>> solution cannot always guarantee this capability, that it is an 
>> unacceptable solution.
> 
> I think most of the WG is comfortable with this and is insisting on
> it.  How many times do we need to go in circles on this?  Once every
> IETF meeting?

Curtis, Stephen, please correct me if I'm mis-characterising your
opinions...

Curtis, you seem to be saying that passing on the information via
non-supporting routers is better than nothing, and so should definitely
be done.

Stephen, you appear to be saying that it might be found to be pointless
or, in fact, worse than useless (ie, actively harmful), and don't want
to be committed to doing so this early in the game.

Is that correct?

Rob

-- 
Robert Loomans                                 Email:  robertl@apnic.net
Senior Programmer/Analyst, APNIC               Phone:    +61 7 3858 3100
http://www.apnic.net                             Fax:    +61 7 3858 3199


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