[92338] in North American Network Operators' Group
Re: IPv6 PI block is announced - update your filters 2620:0000::/23
daemon@ATHENA.MIT.EDU (Jeroen Massar)
Thu Sep 14 11:56:59 2006
Date: Thu, 14 Sep 2006 17:56:05 +0200
From: Jeroen Massar <jeroen@unfix.org>
To: Stephen Sprunk <stephen@sprunk.org>
Cc: IPv6 Ops list <ipv6-ops@lists.cluenet.de>, nanog@merit.edu
In-Reply-To: <01dc01c6d789$69e8be70$6401a8c0@atlanta.polycom.com>
Errors-To: owner-nanog@merit.edu
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig178095183A048709504B57E7
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Stephen Sprunk wrote:
> Thus spake "Jeroen Massar" <jeroen@unfix.org>
>> 8<-----------------------------------------
>> IPv6 Assignment Blocks CIDR Block
>> 2620:0000:/23
>> ----------------------------------------->8
>> Expect blocks in between /40 and /48 there.
>=20
> Expect mostly /48s and /44s, given that ARIN has not defined any=20
> criteria for what justifies more than a /48.
The first three are already available:
2620::/48 - U.S. Securities & Exchange Commission
2620:0:10:/48 - S. D. Warren Services Co.
2620:0:20:/48 - CollabNet
These have been added to GRH (http://www.sixxs.net/tools/grh/) now lets=20
see how long it takes for them to show up in the global tables and how=20
far their reach will be. Hallway talk: one of them was requested 6 sept, =
answer on the same day that it will be issued, received on 13 sept, nice =
work there ARIN :)
> Of course, some folks will
> announce a /44 instead since the block is reserved, but it should
> still only be one route.
That it is reserved as a /44 doesn't mean one can announce that /48 as=20
it is not assigned to them.
> Still, even if every org that qualified for an assignment today got one=
,=20
> you're still only looking at a couple tens of thousands of routes max. =
> ARIN using a /23 for PIv6 is either serious overkill or "we'll never=20
> need to allocate another block" at work.
The /23 is a good thing indeed, people won't most likely have to ever=20
update their filters for that one.
[..]
> IMHO, BGP will fall over and die long before we get to that many ASNs.
I guess that will indeed be the case.
> Remember, the goal in giving people really big v6 blocks, vs. IPv4-styl=
e=20
> multiple allocations/assignments, is to reduce the necessary number of =
> routes to (roughly) the number of ASNs.
But people require Traffic Engineering, as such they might want to do=20
some routing tricks and thus split up their /48. Only the future will tel=
l.
> If PIv6 folks start announcing absurd numbers of routes within their=20
> allocation, I'd expect ISPs to start filtering everything longer than=20
> /48 -- if they don't do so from the start.
Most ISP's already do this now. In effect /19 - /48 is unfiltered in=20
most places.
Greets,
Jeroen
PS: Anybody knows when ARIN will finally learn CIDR? :)
8<-----------------------------------
$ whois -h whois.arin.net 2620::/48
CIDR queries are not accepted
No match found for 2620::/48.
-------------------------------->8
They clearly understand it is CIDR and the resulting record even has a=20
CIDR field; they really should move to the RPSL based db that RIPE provid=
es.
--------------enig178095183A048709504B57E7
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/
iHUEARECADUFAkUJe5UuFIAAAAAAFQAQcGthLWFkZHJlc3NAZ251cGcub3JnamVy
b2VuQHVuZml4Lm9yZwAKCRApqihSMz58I7u5AJ9qYNhUEJxklbruqTzEE9x+x7nm
+QCgorOLkiG7S5Fnt6UtmPMwxYaxy2c=
=TxCk
-----END PGP SIGNATURE-----
--------------enig178095183A048709504B57E7--
