It belonged to some Canadian ISP, I believe it was a cable company.
Regarding the aggregation/deaggregation mess. This is due to the fact
that ARIN is rather strict with IP assignements and how we route
internally.
Because ARIN wants us to use 80% of our ip blocks, before we can request
new assignments from them we have to dole out addresses in /22's to each
city we have, in order to use them up appropriately. Its been a bit of a
nightmare trying to meet ARIN's policies and also try to meet the
Internet Communities policies. Believe me, I would much rather advertise
a /16 prefix out to the Internet, rather then a /22. We have not been
able to accommodate this unfortunately.
It belonged to some Canadian ISP, I believe it was a cable company.
Regarding the aggregation/deaggregation mess. This is due to the fact
that ARIN is rather strict with IP assignements and how we route
internally. Because ARIN wants us to use 80% of our ip blocks, before we can request
new assignments from them we have to dole out addresses in /22's to each
city we have, in order to use them up appropriately. Its been a bit of a
nightmare trying to meet ARIN's policies and also try to meet the
Internet Communities policies. Believe me, I would much rather advertise
a /16 prefix out to the Internet, rather then a /22. We have not been
able to accommodate this unfortunately.
Err... Why do you say you need to advertise a /22 for each city rather
than the /16 for your entire network? What's inside your network and
how you distribute your addresses there is not of concern for anyone
outside of your network. Why don't you advertise the /16 via BGP and
then let the IGP handle the /22 distribution to each city?
Regarding the aggregation/deaggregation mess. This is due to the fact
that ARIN is rather strict with IP assignements and how we route
internally.
Because ARIN wants us to use 80% of our ip blocks, before we can request
new assignments from them we have to dole out addresses in /22's to each
city we have, in order to use them up appropriately. Its been a bit of a
Are you saying you have POPs in dozens of cities and do not have your own
network connecting them, but instead buy transit from verio, cogent, and
at&t in each city and announce /22 subnets to them from each of these POPs
using the same (15270) origin ASN with ASN loop detection disabled?
So, why would GRE not be a reasonable (temporary)
solution here? If the islands are going to remain
disconnected long term, why not get additional AS
numbers?
I find blaming > 250 extra routes WITH EXACTLY THE
SAME PATH INFO on ARIN pretty unconvincing...
Perhaps the networks are disconnected? Perhaps there is insufficient bandwidth between the cities to carry inter-city traffic?
So, why would GRE not be a reasonable (temporary) solution here? If the islands are going to remain disconnected long term, why not get additional AS numbers?
I don't believe the fact of having multiple ASNs solves this issue, I believe ARIN looks at allocated space per OrgID.
I find blaming 250 extra routes WITH EXACTLY THE SAME PATH INFO on ARIN pretty unconvincing...
Personally, I (or my routers) don't have a problem -- at least at the moment. You could always filter.
It is non-trivial to get additional ASNs, even if you are multi-homed in multiple sites.
Doesn't mean it can't be done.
But AS exhaustion is far more critical than IP exhaustion. (Or even RIB/FIB/proc exhaustion through additional prefixes, IMHO.) So if they want to be .. uh, well, a good 'Netizen and use one AS with static routes or defaults or something to route between them, that's better than a slew of ASes with the same prefix info we have today.