[139974] in North American Network Operators' Group
RE: IPv6 Prefix announcing
daemon@ATHENA.MIT.EDU (George Bonser)
Tue Apr 26 13:12:51 2011
Date: Tue, 26 Apr 2011 10:12:40 -0700
In-Reply-To: <4B4120B1642DCF48ACA84E4F82C8E1F65B83E20FC4@EXCH>
From: George Bonser <gbonser@seven.com>
To: Kate Gerry <kate@quadranet.com>, "Justin M. Streiner"
<streiner@cluebyfour.org>, <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
> From: Kate Gerry=20
> Sent: Tuesday, April 26, 2011 9:39 AM
> To: 'Justin M. Streiner'; nanog@nanog.org
> Subject: RE: IPv6 Prefix announcing
>=20
> Funny enough, some carriers actually require the 'smallest' as being
> /32... :(
>=20
That might be true in PA space, but PI space is issued down to /48. I
am not aware of anyone who filters smaller than a /32 in PI space though
that doesn't mean it doesn't happen. The largest holdout was Verizon
but my understanding is they now accept a /48 in PI space.
So:=20
A /32 is the smallest prefix issued in PA and some networks will not
accept a prefix smaller than /32 from PA address space.
A /48 is the smallest prefix issued in PI and some networks will not
accept a prefix smaller than /48 from PI address space.
In other words, if you are going to attempt to multihome a /48
allocation from your provider's aggregate, you are better off getting
your own provider independent block.
