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

["George, Wesley" <[e-mail]>]

-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On Behalf Of Russ White
Sent: Friday, September 09, 2011 12:43 PM
To: Jakob Heitz
Cc: [e-mail]
Subject: Re: [sidr] BGPSec scaling (was RE: beacons and bgpsec)

You could make it cheaper by moving
specific things off the router and onto auxiliary boxes, but the point
of inline authentication is _not_ to move anything onto boxes outside
the router (or even onto line cards within the router) --this is the
reason all overlay proposals were rejected up front.

WEG] I think that this looks at the separation between forwarding and compute resources a bit too narrowly. As Shane pointed out in an earlier thread, there are some implementations where the forwarding hardware and the routing/general compute hardware are far too closely linked together in the way that they grow and scale. Perhaps the solution is to stop trying to cram new magic into RP slots and start pushing the external processing model where the compute resources are physically, but not logically separate (eg a blade center with a fabric interface, not a standalone route server) so that computing (routing) and forwarding can scale independently. It still ends up with a model where you're throwing more CPU resources at the problem instead of fixing the underlying internet routing scale problem, but perhaps that kicks the can far enough down the road to be acceptable because it puts things back on a commodity PC hardware growth and cost curve.

Wes

This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.