Hi Robin,
|If this was a maths class, I would be sure that this Friday's test
|would include questions on abstraction action boundary and
|abstraction naming boundary!
;-) Indeed. Those are Noel-ism's as you've found out, and they're
absolutely necessary to talk about aggregation
Hi Tony,
If this was a maths class, I would be sure that this Friday's test
would include questions on abstraction action boundary and
abstraction naming boundary!
Perhaps you could give a more concrete example of how you envisage
routers behaving in a geographic address aggregation setting
: Abstraction action boundary geo-aggregation router
behavior
To: 'Robin Whittle' [EMAIL PROTECTED], 'Routing Research Group'
rrg@psg.com
Date: Tuesday, July 22, 2008, 4:53 AM
Hi Robin,
|If this was a maths class, I would be sure that this
Friday's test
|would include questions on abstraction
renumbering and without any burden to those outside of the
continent.
If routing optimality becomes an issue, having an abstraction action
boundary that is even one or more hops removed from the abstraction naming
boundary can further improve the situation.
The issue with this approach is again one
as
most specifcs draw the traffic around your network, and you incur the phone
calls from Canada, who will kindly ask you to cease and desist, eh? ;-)
We discovered this when we tried to do proxy aggregation the first time: the
abstraction action boundary MUST be carefully and thoughtfully
be delivered in Montreal rather than New York. But
|this isn't the kind of coordination where the entire internet
|needs to
|be upgraded before something useful can happen.
True, but it still requires all of the providers at the abstraction action
boundary to coordinate to ensure that traffic
discovered this when we tried to do proxy aggregation the first
time: the
abstraction action boundary MUST be carefully and thoughtfully
engineered to
avoid unintended consequences. This requires cooperation.
Right. A pan-Canadian network that also peers in some US cities may be
somewhat
in question at those locations, inviting the
traffic...
We discovered this when we tried to do proxy aggregation the first
time: the
abstraction action boundary MUST be carefully and thoughtfully
engineered to
avoid unintended consequences. This requires cooperation.
Right. A pan-Canadian
