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/[email protected]/
[address-policy-wg] 2015-05 Discussion Period extended until 13 May 2016 (Last /8 Allocation Criteria Revision)
- Previous message (by thread): [address-policy-wg] 2015-05 Discussion Period extended until 13 May 2016 (Last /8 Allocation Criteria Revision)
- Next message (by thread): [address-policy-wg] 2015-05 Discussion Period extended until 13 May 2016 (Last /8 Allocation Criteria Revision)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Radu-Adrian FEURDEAN
ripe-wgs at radu-adrian.feurdean.net
Sat Apr 16 13:24:06 CEST 2016
On Fri, Apr 15, 2016, at 11:21, Tim Chown wrote: > > On 15 Apr 2016, at 10:02, Adrian Pitulac <adrian at idsys.ro> wrote: > > > > but from statistics and from my point of view, ARIN depletion of pools, resulted directly in IPV6 growth. > > Well, no, not if you look at > https://www.google.com/intl/en/ipv6/statistics.html, which shows steady > IPv6 growth towards Google services (approaching 11% now). That's global. For Canada : http://stats.labs.apnic.net/ipv6/CA that's clearly visible. Less so for the US. > Similarly wrt active IPv6 routes - > http://bgp.potaroo.net/v6/as2.0/index.html Route count, like allocations made by RIRs is completely irrelevant. Having IPv6 announced but null-routed at the border and completely absent inside the network (or only present on core equipment) is commonplace.
- Previous message (by thread): [address-policy-wg] 2015-05 Discussion Period extended until 13 May 2016 (Last /8 Allocation Criteria Revision)
- Next message (by thread): [address-policy-wg] 2015-05 Discussion Period extended until 13 May 2016 (Last /8 Allocation Criteria Revision)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]