Re: [sidr] BGPSec scaling (was RE: beacons and bgpsec)

"Sriram, Kotikalapudi" <kotikalapudi.sriram@nist.gov> Fri, 09 September 2011 14:58 UTC

Return-Path: <kotikalapudi.sriram@nist.gov>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AD5121F86C7 for <sidr@ietfa.amsl.com>; Fri, 9 Sep 2011 07:58:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.508
X-Spam-Level:
X-Spam-Status: No, score=-5.508 tagged_above=-999 required=5 tests=[AWL=1.091, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SO1FPEBUANYO for <sidr@ietfa.amsl.com>; Fri, 9 Sep 2011 07:58:15 -0700 (PDT)
Received: from wsget2.nist.gov (wsget2.nist.gov [129.6.13.151]) by ietfa.amsl.com (Postfix) with ESMTP id 0B9B921F8681 for <sidr@ietf.org>; Fri, 9 Sep 2011 07:58:06 -0700 (PDT)
Received: from WSXGHUB2.xchange.nist.gov (129.6.18.19) by wsget2.nist.gov (129.6.13.151) with Microsoft SMTP Server (TLS) id 14.1.323.0; Fri, 9 Sep 2011 11:00:44 -0400
Received: from MBCLUSTER.xchange.nist.gov ([fe80::d479:3188:aec0:cb66]) by WSXGHUB2.xchange.nist.gov ([129.6.18.19]) with mapi; Fri, 9 Sep 2011 10:59:27 -0400
From: "Sriram, Kotikalapudi" <kotikalapudi.sriram@nist.gov>
To: "George, Wesley" <wesley.george@twcable.com>, sidr wg list <sidr@ietf.org>
Date: Fri, 09 Sep 2011 10:59:27 -0400
Thread-Topic: [sidr] BGPSec scaling (was RE: beacons and bgpsec)
Thread-Index: AcxXlRYzx19OWW9WR+qLPmTOJN+B3gAtymVABVV7wuAAKuVRUAArCkoc
Message-ID: <D7A0423E5E193F40BE6E94126930C49308D2CF54D1@MBCLUSTER.xchange.nist.gov>
References: <A37CADA4-F16D-4C01-8D9C-D01001C4EFE4@tcb.net> <21C19DA8-7BF3-4832-8C13-C9A45FE026FB@algebras.org> <87D9E106-2A37-4E1E-8C69-7084C199A3FE@tcb.net> <331AEFBD-6AE5-469E-A11E-E672DC61DCDC@pobox.com> <B92913D1-AB82-4D9F-B8A9-F8F4F99713D6@tcb.net> <p06240803ca685bff5443@[128.89.89.43]> <D6D12861-412E-4A65-B626-B627449981B8@tcb.net> <34E4F50CAFA10349A41E0756550084FB0C2ED5A4@PRVPEXVS04.corp.twcable.com> <D7A0423E5E193F40BE6E94126930C49308D36D8383@MBCLUSTER.xchange.nist.gov>, <34E4F50CAFA10349A41E0756550084FB0E0D6263@PRVPEXVS04.corp.twcable.com>
In-Reply-To: <34E4F50CAFA10349A41E0756550084FB0E0D6263@PRVPEXVS04.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Subject: Re: [sidr] BGPSec scaling (was RE: beacons and bgpsec)
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Sep 2011 14:58:16 -0000

>If the timing is wrong, it ends up being gating to deployment of BGPSec. 
>If the timing is right, it probably requires a lot of redesign work 
>and additional investment, neither of which are particularly optimal. 
>I'd prefer that we document up-front that there is a real concern here and that 
>IETF needs to get moving on the scale problem, 
>
>Wes George

The devil is always in the details. But I am thinking (hope not too simplistically)
that once you have a solution agreed upon and deployed for scaling the FIB, then
all it does is slow down (hopefully quite significantly) the growth of the
FIB and RIB sizes. It makes no changes to the eBGP protocol as such.
(Only adds the additional step of mapping look up at the ingress routers.)
It would appear that "BGPSEC protocol specification" by itself has no dependency 
on the FIB scalability solution (except that the potential impediments for 
BGPSEC deployment may be substantially alleviated -- benefiting from possibly
significant reductions in RIB size, # updates/beacons, and route-processor workload).
FIB scalability solution would ultimately reduce the cost of deployment
of BGPSEC, but the specifications of the two solutions/protocols need not be
intertwined. Having said that, I am all for full scale co-operation between the
two efforts -- much as you have suggested.  

Sriram