[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: draft-savola-multi6-asn-pi-01.txt

On 25-feb-04, at 9:43, Pekka Savola wrote:

The trouble with large corporations is that they typically have many
offices. Now either all of those connect to the net individually, and
then having a single AS and a single block of address space is of
little use,

Well, it could be of a lot of use.

It could be, but I'm not convinced it is most of the time.

But as noted before by Craig
Huegen (at least), if using a single netblock, these corporations
would have traffic engineering requirements.

Everyone who multihomes and doesn't have huge piles of money to burn has traffic engineering requirements. I agree this is problematic, and we need to revisit this at some point.

If more specific routes
aren't allowed for traffic engineering purposes, or advertising just a
regional subset of address space, this is not enough for a solution.

Guess what, it is allowed, but most people filter these routes out.

An alternative mechanism, which I have stated earlier, is to
"divide-and-conquer" even the larger enterprises: every branch which
connects to ISPs has different addresses.  This will be pure hell for
network admins if they have offices in e.g. 100 or 200 countries, but
such is life, I guess... :)

One man's "pure hell" is another man's job security. :-)

Why should BigCorp Inc. be allowed to announce 200 /40s for 200 offices, when a collection of 200 small corportations isn't allowed to do the same thing collectively?

It's very simple: either you announce your entire block everywhere and carry traffic from location A that needs to be in location B over your own network, or be like anyone else and get PA space (which you can then use for multiaddress multihoming).

or those offices are connected through a private network
that also carries internet traffic, in which case they are their own
ISP and they should qualify for an AS and address space like regular
ISPs.


IMHO, the RIR allocation policies do not allow an /32 for this
specific case of "Enterprise network having its customers within the
enterprise".

Yes, the current "200 customers in 2 years" requirement is problematic (although I'm sure a fortune 500 company can meet it, just give your employees /48s or some such) but so far nobody has been able to come up with something better.