This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/
[address-policy-wg] Removal of multihomed requirement for IPv6
- Previous message (by thread): [address-policy-wg] Removal of multihomed requirement for IPv6
- Next message (by thread): [address-policy-wg] Removal of multihomed requirement for IPv6
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Alex Le Heux
alexlh at ripe.net
Sat May 7 07:50:18 CEST 2011
On May 7, 2011, at 05:31, Mikael Abrahamsson wrote: > On Fri, 6 May 2011, Gert Doering wrote: > >> We still don't know, but given that IPv4 PI is much less restrictive, IPv4 PI is only contributing 21% of the BGP routes in the RIPE region, and the restrictive IPv6 PI policy is holding up deployment plans, people are asking to get this changed. > > <meetings.ripe.net/ripe-53/presentations/address_space.pdf> seems to indicate that it's 59% ? Is there newer data available that shows what's happened since 2011 that could be had? Dear Mikael, The 59% is the number of IPv4 PI assignments that the RIPE NCC made at the time. Looking at the IPv4 numbers today, we find: - Using 1996 as a start date for counting, the RIPE NCC has allocated 15k prefixes to LIRs and assigned 16k prefixes as PI - In 2011 so far, 57% of all prefixes given out were PI In the BGP routing table the de-aggregation levels are much higher for PA allocations than for PI assignments though, 1:3.8 for PA allocations and 1:1.1 for PI assignments. This is the 21% number that Gert quotes. Best regards, Alex Le Heux RIPE NCC
- Previous message (by thread): [address-policy-wg] Removal of multihomed requirement for IPv6
- Next message (by thread): [address-policy-wg] Removal of multihomed requirement for IPv6
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]