[address-policy-wg] Comments on proposal 2014-04 (Remove the IPv6 Requirement for receiving address space)

Hi Stefan,

On 22/01/2015 16:42, Stefan Schiele wrote:
> Andrea Cima from RIPE NCC wrote on 11 December 2014:
>> The RIPE NCC has started allocating /22s from the last /8 on 14
>> September 2012. Since then 4190 IPv6 allocations have been made, out
>> of which 1160 are currently visible in the BGP routing tables.
>>
>> If we take into consideration the total number of IPv6 allocations
>> made by the RIPE NCC, 8398 IPv6 allocations have been made, out of
>> which 4098 are currently visible in the BGP routing tables.
> 
> That means that more than 27% of those IPv6 allocations are really used;
> and that's a quite impressive figure. And I think we can conclude that
> the current policy does have a positive effect on IPv6 deployment. In
> comparison about 49% of all IPv6 allocations are visible in the BGP
> routing table; and that makes that 27% even more impressive.

I disagree with your interpretation: present in the routing table does
not imply being used. I used to take it as a good sign, but now I
believe it is a very low bar - someone thought to apply for the address
space and succeeded in configuring a BGP session somewhere. Maybe they
really use it and maybe they don't; it's just not a very useful metric.

Note that "arguments supporting the proposal" says that the status quo
is actively troublesome for users of IPv6 PI space: to get a /22, they
have to disrupt their IPv6 installation to return their PI assignment
and get a PA allocation. Having this in policy is currently doing harm
to IPv6, and we can do better outreach than this.

Best regards,
Dave

-- 
Dave Wilson, Project Manager                        web:   www.heanet.ie
HEAnet Ltd, 5 George's Dock, IFSC, Dublin 1         tel: +353-1-660-9040
Registered in Ireland, no 275301                    fax: +353-1-660-3666