[140491] in North American Network Operators' Group
Re: IPv6 foot-dragging
daemon@ATHENA.MIT.EDU (Martin Millnert)
Thu May 12 12:48:08 2011
In-Reply-To: <5A6D953473350C4B9995546AFE9939EE0C9E320F@RWC-EX1.corp.seven.com>
Date: Thu, 12 May 2011 12:46:31 -0400
From: Martin Millnert <millnert@gmail.com>
To: George Bonser <gbonser@seven.com>
Cc: Bernhard Schmidt <berni@birkenwald.de>, nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
George,
On Thu, May 12, 2011 at 11:41 AM, George Bonser <gbonser@seven.com> wrote:
>> A lot. I see /48 breakouts from /32 PA blocks for instance, announced
>> by a
>> customer AS of the PA holder AS.
>>
>> --
>> Mikael Abrahamsson =A0 =A0email: swmike@swm.pp.se
>
> Which is kinda sad.
It's reality.
> If those customer AS are multihomed or plan to be
> multihomed, they can get their own allocation out of PI space. If they
> are not multihomed outside of the provider AS, there is no need for the
> provider to "leak" that /48 out of their AS to their peers.
In the RIPE region, being multihomed or planning to be it is not a
sufficient condition for getting a PI prefix. And even if it was, the
hit on DFZ is the same as from getting allocation from LIR. Even if
they get their own /32, the hit would be the same (modulo individual
FIB/RIB implementations).
Consequently, there's work in progress to modernize RIPE IPv6 address polic=
y.
http://ripe62.ripe.net/presentations/148-wg.pdf p. 19 and forward.
Cheers,
Martin
