[92318] in North American Network Operators' Group
IPv6 PI block is announced - update your filters 2620:0000::/23
daemon@ATHENA.MIT.EDU (Jeroen Massar)
Wed Sep 13 18:12:47 2006
Date: Thu, 14 Sep 2006 00:05:16 +0200
From: Jeroen Massar <jeroen@unfix.org>
To: IPv6 Ops list <ipv6-ops@lists.cluenet.de>
Cc: nanog@merit.edu
In-Reply-To: <A82D39C7-B176-4583-B952-208CD5524CD7@cisco.com>
Errors-To: owner-nanog@merit.edu
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig53CA6F516B4CCDCB81BBABF6
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
It's update your IPv6 filters time:
http://www.arin.net/reference/ip_blocks.html
8<-----------------------------------------
IPv6 Assignment Blocks CIDR Block
2620:0000:/23
----------------------------------------->8
Expect blocks in between /40 and /48 there.
That is enough space for best-case 2^(40-23) =3D 131.072 routes, worst=20
case 2^(48-23) =3D 33.554.432 extra routes in your routing table, I hope =
Vendor C can handle it by the time that happens. In order words: better=20
start saving up those bonus points, you will be buying quite a lot of=20
new gear if this ever comes off the ground ;)
Most likely case is a bit more optimistic if one takes /44's: 2.097.152
Still a lot more than the IPv4 routing table is now. It will take time,=20
and possibly a lot, but it could just happen...
On NANOG Roland Dobbins wrote:
[..sarcasm mode..]
> turning every host=20
> on the network into a router via a Shim-6-like mechanism isn't, either
If you would follow shim6 then you would notice that there is also an=20
option for doing it side-wide. But I guess Vendor C doesn't like that=20
option as then they can't sell bigger fatter routers ;)
> (can you imagine help-desks who can barely cope with basic Windows=20
> issues trying to support Shim-6, heh?).
Ever tried to ask a help-desk if they knew what IPv4, BGP, ASN or any=20
other simple term was? ;) Most times they don't even know what=20
'traceroute' means.
[..]
> Vendors, network operators and=20
> those participating in standards bodies must understand the seriousness=
=20
> of these issues for customers and work to address them (pardon the pun,=
=20
> heh).
Indeed a certain Vendor C should really start working on fixing a lot of =
bugs quickly.
Greets,
Jeroen
--------------enig53CA6F516B4CCDCB81BBABF6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Jeroen Massar / http://unfix.org/~jeroen/
iHUEARECADUFAkUIgKQuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I27DAJ0a1HCQHpgnXsrbq99n9B3PyBaO
tACgsFanATMb6ZZzbUVpvGi+97eslcU=
=B4yV
-----END PGP SIGNATURE-----
--------------enig53CA6F516B4CCDCB81BBABF6--
