what's the problem anyway
with 32bit ASN's there should be enough AS namespace to give everyone that
wants to multihome their ipv6/ipv4 PI their own AS number...
should pretty much be the de-facto standard (unless ofcourse you want to
tie your customers to your internet-provider-activities by making it hard
to leave)
maybe we should have made AS numbers 64 bit as well... so there would be
one for every /64 end user
as for the rest of it: get routers with more ram (i don't want to hear any
"my border routers have less than 8GB of ram") arguments, that stuff is
-old-, it's got gray hair and a beard and belongs in a museum, not on the
internet)
The internet will grow, you can't expect it to grow less fast or to
"aggregate" routes just because your technically outdated stuff doesn't
have enough ram to handle the growing route table size. (preferably
offset-based rather than with a sort/lookup mechanism)
if a customer has a /64 and wants to announce that /64 himself, i see no
reason not to give it to them, especially not if hte only reason would be
that some people run still routers that have less ram than my eeepc.
(and some suppliers still think that's "OK" to sell)
On Tue, 26 Oct 2010, Chris Boyd wrote:
On Oct 26, 2010, at 2:45 PM, George Bonser wrote:
But how do they multihome without an ASN?
If they have an ASN, how did they get it without going to an RIR and
paying a fee?
I beleive Jack said that they have redundant connections to his network. I
took that to mean that they did not multihome to different AS.
Such arrangements are not uncommon. Sprint seems to have done very well
selling this sort of near-turnkey service to rural DSL carriers, tiny single
town MSOs and the like.
--Chris
