On 7/16/10 6:02 AM, Valdis.Kletnieks@vt.edu wrote:
On Thu, 15 Jul 2010 20:57:15 PDT, Henry Linneweh said:
Can we get a consensus definition on these definition's and what hardware vender's make edge routers and what hardware vender's make core routers.
I got a router, it's got 5-6 10GE interfaces talking to other routers on my network backbone, and a bunch of 10GE links to end-user-facing aggregation switches. Since it's only forwarding inside my network, it's a core router by your definition.
I now turn up an identical hardware 10GE link - connected to Level3. I just became an edge router by your definition since I'm talking to another network. (I know, I probably don't want to do that - but I *could*, maybe even without a full BGP feed if the routing situation allows. The point is the definition is busticated).
There's also virtualization due to the ubiquitous deployment of VRF's moderate to size extra-large routers are entirely likely to be serving in multiple roles.
Adding to the confusion is the fact that the edge routers of some large providers need more capacity than the core routers of smaller organizations....
Maybe we need to ditch the terms edge and core, and instead talk about:
1/4" plastic tubing - http://www.waterfiltermart.com/images/products/preview/plastic_tubing_and_nu... garden hose - http://upload.wikimedia.org/wikipedia/commons/thumb/c/cd/Garden_hose.jpg/800... fire hose - http://www.firetrainingcenter.com/images/FireHoseStreams.jpg NYC Delaware Aqueduct - http://www.allpropertymanagement.com/blog/2010/02/09/worlds-awesome-tunnels/
Everybody good with that? ;)
(Man.. it *leaks* 15 million gallons a day. That's capacity. :)