Merit Network
Can't find what you're looking for? Search the Mail Archives.
  About Merit   Services   Network   Resources & Support   Network Research   News   Events   Home

Discussion Communities: Merit Network Email List Archives

North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: IPv6 internet broken, Verizon route prefix length policy

  • From: Valdis.Kletnieks
  • Date: Tue Oct 13 00:13:52 2009

On Mon, 12 Oct 2009 17:40:36 PDT, David Conrad said:
> On Oct 12, 2009, at 5:09 PM, Owen DeLong wrote:
> > With IPv6, it probably won't be the ideal 1:1 ratio, but, it will come
> much closer.
>
> I wasn't aware people would be doing traffic engineering differently in
> IPv6 than in IPv4.

You get some substantial wins for the non-TE case by being able to fix
the legacy cruft.  For instance, AS1312 advertises 4 prefixes:
63.164.28.0/22, 128.173.0.0/16, 192.70.187.0/24, 198.82.0.0/16
but on the IPv6 side we've just got 2001:468:c80::/48.

And we're currently advertising *more* address space in one /48 than we
are in the 4 IPv4 prefixes - we have a large chunk of wireless network that
is currently NAT'ed into the 172.31 space because we simply ran out of room
in our 2 /16s - but we give those users globally routed IPv6 addresses.

Attachment: pgp00029.pgp
Description: PGP signature




Discussion Communities


About Merit | Services | Network | Resources & Support | Network Research
News | Events | Contact | Site Map | Merit Network Home


Merit Network, Inc.