IPv4 Run-Out And the consequences Alex Semenyaka | UADOM, Kyiv | 6 December 2019
Timeline • 2011 IANA ran-out of /8s • 15 Sept 2012 RIPE NCC: exhaustion - final /22 per member • 17 April 2018 RIPE NCC: final 185/8 block depleted • 25 November 2019, 14:35 UTC: last /22 run-out Alex Semenyaka | UADOM, Kyiv | 6 December 2019 2
Remaining IPv4 Pool in Millions Alex Semenyaka | UADOM, Kyiv | 6 December 2019 3
Alex Semenyaka | Yandex Next Hop, Moscow | 7 October 2019 4
Reserved IPv4 • /13: temporary assignments • Approx. /16: Internet Exchange Points (IXPs) - Of /15 reserved for this purposes - With the current rate, enough for 10 years more • /13: quarantine - Will be allocated later • IPv4 dust Alex Semenyaka | UADOM, Kyiv | 6 December 2019 5
The Waiting List • Supported by the IPv4 policy • First, you have to become LIR. • Only if you did not already get an allocation from the RIPE NCC • /24 Alex Semenyaka | UADOM, Kyiv | 6 December 2019 6
Addresses being returned • Continues after run-out • Closures • Recovered space: approx. 2000 /24s in 2019 Alex Semenyaka | UADOM, Kyiv | 6 December 2019 7
What about other RIRs? APNIC AfriNIC LACNIC ARIN Alex Semenyaka | UADOM, Kyiv | 6 December 2019 8
Transfers: RIPE community 2012 response • Trading in IPv4 is inevitable • Priority accurate registry • Current policy: - IPv4 transfers are allowed - 24 month holding period 9 Alex Semenyaka | UADOM, Kyiv | 6 December 2019
PI vs PA • You have to have a LIR status to get a PA block • PI cannot be used to make further assignments to other parties. - Both IPv4 and IPv6 - Even 1 address - Thus, PI is suitable for Internet resources, but for ISPs - There was no strict control over this rule, but it can be invented 10 Alex Semenyaka | UADOM, Kyiv | 6 December 2019
IPv4 Lifespan Extension Rearranging Deck Chairs on the Titanic 11 Alex Semenyaka | UADOM, Kyiv | 6 December 2019
IPv6 in Ukraine • The grows just started - Current level is sufficiently lower than the world average: 27%, according to Google • IPv6 operators: - Netassist - ITL.ua - Triolan - ? Alex Semenyaka | UADOM, Kyiv | 6 December 2019 12
IPv6 in Ukraine • There are powerful reasons for such a low IPv6 penetration • However, nursing these causes instead of trying to fight them will now lead to operational problems for operators • It is easies for content providers, and they can help telecom operators - Content over IPv6 saves money on NAT/CGNAT expanding Alex Semenyaka | UADOM, Kyiv | 6 December 2019 13
Popularity of IPv6-capable websites Source of Similar • It makes perfect BigMir Liveinternet InAU TNS data Web sense for operators Number of to implement IPv6 300 300 3000 25 50 25 resources - The most popular IPv6-enabled, resources are IPv6- 30,0% 30,7% 25,9% 36,0% 32,0% 24,0% % enabled (Google, Protected by Youtube, Facebook) 27,3% 24,7% 11,9% 4,0% 10,0% 0,0% Cloudflare, % • Cloudflare helps Native IPv6 2,7% 6,0% 14,0% 32,0% 22,0% 24,0% } } support, % • Most of local resources do not see the reason to turn IPv6 on Count only local Include global resources resources (Google, Facebook etc) Alex Semenyaka | UADOM, Kyiv | 6 December 2019 14
? Questions
Recommend
More recommend
