Hi Martin, These numbers give me a different interpretation: <div class="gmail_quote">On Thu, Aug 18, 2011 at 3:43 PM, Martin Millnert <<a href="mailto:millnert@gmail.com" target="_blank">millnert@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Turchani, <div> On Wed, Aug 17, 2011 at 7:41 PM, Turchanyi Geza <<a href="mailto:turchanyi.geza@gmail.com" target="_blank">turchanyi.geza@gmail.com</a>> wrote: > Hi Alex, > > May I interpret your slide29 in this way: > > 3,5% off the address space had been allocated as PI in the RIPE NCC service > region and this PI address space is responsible for 21% of the BGP prefixes > (originated in this region). > > So 3,5% AND 21%.... > > In IPv6 PI this ratio probably will be even worse... </div>But is that ratio actually such a useful metric for IPv6? I think you overlooked page 30, which IMO is much more useful: 15417 PA allocations => 59126 prefixes in the DFZ, a ratio of 3.8. 16340 PI assignments => 17468 prefizes in the DFZ, a ratio of 1.1. </blockquote><div> </div></div>PI address space creates very scattered allocation as 16340 PI assignments just covers 3,5% of the RIPE allocated address space. This is the point, is n't it? BTW, the 3,5% is not mentionned on the slides... but it was included in the letter of Alex. Second point: if ALL IPv4 PI holder would request IPv6 PI then you might expect another 17K prefixes in the routing table just from the RIPE Region! And this is just the start! Thanks, Géza