https://amrelhusseiny.github.io/tags/backbone/Recent content in Backbone on Amro ElhusseiniHugoen-usSat, 10 Sep 2022 11:11:25 +0200https://amrelhusseiny.github.io/blog/001_networks_0003_extending_rfc_1918/001_networks_0003_extending_rfc_1918/Sat, 10 Sep 2022 11:11:25 +0200https://amrelhusseiny.github.io/blog/001_networks_0003_extending_rfc_1918/001_networks_0003_extending_rfc_1918/<div> <h2>Table Of Contents</h2> <nav id="TableOfContents"> <ul> <li><a href="#cgnat-carrier-grade-nat">CGNAT (Carrier Grade NAT)</a></li> </ul> </nav> </div> <h1 id="introduction">introduction</h1> <p>We are all familiar with the RFC-1918 AKA Private IP Spaces (10.x.x.x , 172.16.x.x , 192.168.x.x), called private IP addresses because they can be duplicated by any user as long as the duplicated IP assigned devices does not meet in same L3 network.</p> <p>But due to the exhaustion of the Public IPv4 space , IANA has assigned a second address space like RFC-1918 , this time though <a href="https://datatracker.ietf.org/doc/html/rfc6598">RFC-6598</a> and its called the <strong>Shared Address space</strong> since 2012 , while it was originaly intended to be used for CGNAT (Carrier Grade Natting), IANA stated in the standard, that it also can be used in the same manner as RFC-1918 addresses , quoting from RFC-6598:</p>