{"id":38460,"date":"2019-10-31T22:23:50","date_gmt":"2019-10-31T19:23:50","guid":{"rendered":"https:\/\/prohoster.info\/blog\/adresa-ipv4-v-ripe-zakonchilis-sovsem-zakonchilis\/"},"modified":"2019-10-31T22:23:50","modified_gmt":"2019-10-31T19:23:50","slug":"adresa-ipv4-v-ripe-zakonchilis-sovsem-zakonchilis","status":"publish","type":"post","link":"https:\/\/prohoster.info\/et\/blog\/administrirovanie\/adresa-ipv4-v-ripe-zakonchilis-sovsem-zakonchilis","title":{"rendered":"IPv4 aadressid RIPE's on otsa saanud. T\u00e4iesti otsa...","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Ok, not exactly. It was a small dirty clickbait. But at the RIPE NCC Days conference held on September 24-25 in Kyiv, the imminent end of the distribution of \/22 subnets to new LIRs was announced. The issue of IPv4 address space exhaustion has been discussed for a long time. It's been about 7 years since the last \/8 blocks were allocated to regional registries. Despite all the deterrent and restrictive measures, the inevitable couldn't be avoided. What awaits us in this regard is discussed in detail below.<\/p>\n

\"IPv4
\n<\/a><\/noindex><\/p>\n

Historical Overview<\/h3>\n

\nWhen all these internets were just being created, people thought that 32 bits for addressing would be more than enough. 232 is approximately 4.2 billion addresses for network devices. Could the first few organizations that came together in the distant 80s ever think that someone would need more? Back then, the first address registry was maintained by a guy named Jon Postel manually, almost in a regular notebook. Requesting a new block could be done over the phone. Occasionally, the current allocated addressing was published as an RFC document. For example, in RFC790<\/a><\/noindex>, published in September 1981, we first encounter the familiar 32-bit IP address notation.<\/p>\n

But the concept took off, and the global network began to develop actively. This gave rise to the first electronic registries, but there was still no smell of smoke. If there was justification, one could easily get even a \/8 block (more than 16 million addresses) in one hand. It wasn't to say that the justification was thoroughly checked back then.<\/p>\n

We all understand that if you consume a resource actively, sooner or later it will run out (rest in peace, mammoths). In 2011, IANA, which allocated address blocks on a global scale, distributed the last \/8s to regional registries. On September 15, 2012, RIPE NCC announced the exhaustion of IPv4 and began distributing no more than \/22 (1024 addresses) to one LIR (though it allowed opening multiple LIRs under one company). On April 17, 2018, the last block 185\/8 was depleted, and since then for a year and a half, new LIRs have been subsisting on breadcrumbs and forage \u2013 blocks returned to the pool for various reasons. Now they are running out too. You can observe this process in real-time at the address https:\/\/www.ripe.net\/manage-ips-and-asns\/ipv4\/ipv4-available-pool<\/a><\/noindex>.<\/p>\n

The train has left<\/h3>\n

\nKonverentsi raporti kirjutamise hetkeks oli ligikaudu 1200 pidevat plokki \/22 veel saadaval. Ja \u00fcsna suur hulk t\u00f6\u00f6tlemata taotlusi eraldamiseks. Teisis\u00f5nu, kui te pole veel LIR, siis viimane plokk \/22 ei ole enam teie jaoks saadaval. Kui olete juba LIR, kuid pole taotlenud viimast \/22, on teil siiski v\u00f5imalus. Kuid taotluse esitamine oleks olnud parem juba eile.<\/p>\n

Lisaks pidevale \/22 on veel v\u00f5imalus saada kombineeritud eraldamine \u2013 kombinatsioon \/23 ja\/v\u00f5i \/24. Siiski, hetkeseisuga l\u00e4hevad k\u00f5ik need v\u00f5imalused t\u00f5en\u00e4oliselt juba n\u00e4dala jooksul otsa. Kindlasti saab \/22-st unustada selle aasta l\u00f5puks.<\/p>\n

Veidi reserve<\/h3>\n

\nLoomulikult ei puhastata aadresse nulli. Kindel aadressiruum on RIPE j\u00e4tnud erinevate vajaduste tarbeks:<\/p>\n