RE: PI space under IPv6

 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

When thinking about requirements, we need to keep in mind that some
end-user organizations really want multiple blocks to announce to the
global network to avoid having a "thick" internetworking mesh between
all
locations.

Most large, global companies want regionalization of their networks;
announcing a single prefix from all locations requires them to build a
beefy infrastructure to deliver traffic, rather than localizing it
(effectively paying twice for traffic delivery -- once to the ISP to
bring traffic to them, and a second time to another provider that needs
to carry it to their final destination).  It also brings along
performance problems unless their set of providers is completely
consistent globally (which is difficult to do given regional performance
implications) -- I've seen traffic cross the ocean twice trying to reach
a destination 40 miles away because some providers have strange BGP
policies.

For a few years now, I've been asserting that there are two major
requirements for large global enterprises:  one is easy "provider
portability" (if renumbering were a "single-command" process for
*everything* including ACL's, all distributed policy in the network,
etc., then I don't care if I have to renumber), the other is the ability
to do regionalized access (don't expect a single prefix per end-user,
even if sized correctly).

/cah

On , [email protected] <> wrote:

> Hi,
> 
>> These allocation procedures do match what I say about all of it: Give
>> address space to organizations that need it. It does FAR from
>> conserve routing table slots though, which indeed is not something
>> the RIR's are involved with, but they should of course try a little
>> IMHO. 
> 
> Indeed.
> 
> To conserve routing table slots, just give a *single* big
> block of IPv6
> addresses to organisations that want and need them. My
> routing table doesn't
> care if an organisation has a /48 or a /27, it's just one
> slot. And I think
> there are plenty IPv6 addresses for this. Giving multiple
> blocks to one
> organisation is the worst that can happen. It saves addresses (of
> which we have plenty), and it wastes routing slots (which we need to
> preserve). 
> 
> - Sander
> 
> _______________________________________________
> global-v6 mailing list
> [email protected]
> http://mailman.apnic.net/mailman/listinfo/global-v6

- -- 
Craig A. Huegen, IT Solutions Architect
IT - Intelligent Network Solutions
Cisco Systems, Inc.
Phone: +1 408 526 8104
email: [email protected]     CCIE #2100

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1

iQA/AwUBRa95vKAMxC7CAM/LEQLzQACg136BBCQYMx1GJDgOyLVT22wttIsAnihu
qcwwGAjTSZpryN5AZBARcii9
=VluG
-----END PGP SIGNATURE-----

_______________________________________________
global-v6 mailing list
[email protected]
http://mailman.apnic.net/mailman/listinfo/global-v6