The model scales well, imho. Regionalize your network into
pieces. Apply each of the pieces into 1 or more proximities to a
Apply set filter lists onto peering sessions for appropriate
Let me expound.
I run Internet-Net.net. I have a POP in every city w/ over 10,000
I aggregate M number of POPs to N number of Hubs.
(use acronym NXP to mean network exchange point.....)
I am connected to P number of NXPs.
I go through each of my N Hubs, and identify if he is
or is not in Pn's region. If he is, I add NXPn's peers to the
allow list. If he's not, I don't.
Won't this work? Is it "too confusing"?
Let's say I have 1 HUB in Arizona. I decide that they are in the
region of MAE-W, PACBELL, and the NXP in Phoenix. So, I accept
routes from everyone at any of those NXPs, and I give my routes
for this HUB only, to everyone at the NXP. I don't tell them
about my route to customers homed to San Mateo, because I don't
want to carry their traffic there, only stuff that's topolgically
'close' to them, as I feel that benefit to my customers is worth
the peering relationship.
Unless you were precient when you allocated your CIDR blocks, this means
that you will not be able to aggregate your networks.