IPv4 shared address space

Last updated

In order to ensure proper working of carrier-grade NAT (CGN), and, by doing so, alleviating the demand for the last remaining IPv4 addresses, a /10 size IPv4 address block was assigned by Internet Assigned Numbers Authority (IANA) to be used as shared address space. [1] This block of addresses is specifically meant to be used by Internet service providers (or ISPs) that implement carrier-grade NAT, to connect their customer-premises equipment (CPE) to their core routers.

Contents

Instead of using unique addresses from the rapidly depleting pool of available globally unique IPv4 addresses, ISPs use addresses in 100.64.0.0/10 for this purpose. Because the network between CPEs and the ISP's routers is private to each ISP, all ISPs may share this block of addresses.

Background

If an ISP deploys a CGN and uses private Internet address space [2] (networks 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) to connect their customers, there is a risk that customer equipment using an internal network in the same range will stop working. The reason is that routing will not work if the same address ranges are used on both the private and the public side of a customer’s network address translation (NAT) equipment. Normal packet flow can therefore be disrupted and the customer effectively cut off the Internet, unless the customer chooses another private address range that does not conflict with the range selected by their ISP.

This prompted some ISPs to develop policy within American Registry for Internet Numbers (ARIN) to allocate new private address space for CGNs. ARIN, however, deferred to the Internet Engineering Task Force (IETF) before implementing the policy, indicating that the matter was not typical allocation but a reservation for technical purposes. [3]

In 2012, the IETF defined a Shared Address Space [4] for use in ISP CGN deployments and NAT devices that can handle the same addresses occurring on both inbound and outbound interfaces. ARIN returned space to the IANA as needed for this allocation and [5] "The allocated address block is 100.64.0.0/10". [4] [6]

Transition to IPv6

The use of shared address space is one of the various methods to allow transition from IPv4 to IPv6. Its main purpose was to postpone the depletion of IPv4 addresses, by allowing ISPs to introduce a second layer of NATting. A common practice is to give CPEs a unique IPv4 address on their Internet-facing interface and use NAT to hide all addresses on the home LAN. Since the pool of available public IPv4 addresses is depleted, it is no longer possible for most ISPs to assign unique IPv4 addresses to CPEs, because there are none left to them to acquire. Instead, an address in the 100.64.0.0/10 range is assigned on the CPE's Internet-facing interface, and this address is translated again to one of the public IPv4 addresses of the ISP's core routers. Using shared address space allows ISPs to continue to use IPv4 as they were used to. This scheme hides a large number of IP addresses behind a small set of public addresses, the same way the CPE does this locally, slowing down the rate IPv4 addresses are depleted. The shared address space contains 222 or 4194304 addresses, so each ISP is able to connect over 4 million subscribers this way.

Other occurrences

In BIND, empty reverse mapping zones for 100.64.0.0/16 through 100.127.0.0/16 (64 zones in total) are automatically created in the 'internal' view, if not configured otherwise.

See also

Related Research Articles

An Internet Protocol address is a numerical label such as 192.0.2.1 that is assigned to a device connected to a computer network that uses the Internet Protocol for communication. IP addresses serve two main functions: network interface identification, and location addressing.

<span class="mw-page-title-main">IPv4</span> Fourth version of the Internet Protocol

Internet Protocol version 4 (IPv4) is the first version of the Internet Protocol (IP) as a standalone specification. It is one of the core protocols of standards-based internetworking methods in the Internet and other packet-switched networks. IPv4 was the first version deployed for production on SATNET in 1982 and on the ARPANET in January 1983. It is still used to route most Internet traffic today, even with the ongoing deployment of Internet Protocol version 6 (IPv6), its successor.

<span class="mw-page-title-main">IPv6</span> Version 6 of the Internet Protocol

Internet Protocol version 6 (IPv6) is the most recent version of the Internet Protocol (IP), the communications protocol that provides an identification and location system for computers on networks and routes traffic across the Internet. IPv6 was developed by the Internet Engineering Task Force (IETF) to deal with the long-anticipated problem of IPv4 address exhaustion, and was intended to replace IPv4. In December 1998, IPv6 became a Draft Standard for the IETF, which subsequently ratified it as an Internet Standard on 14 July 2017.

Classless Inter-Domain Routing is a method for allocating IP addresses for IP routing. The Internet Engineering Task Force introduced CIDR in 1993 to replace the previous classful network addressing architecture on the Internet. Its goal was to slow the growth of routing tables on routers across the Internet, and to help slow the rapid exhaustion of IPv4 addresses.

A multicast address is a logical identifier for a group of hosts in a computer network that are available to process datagrams or frames intended to be multicast for a designated network service. Multicast addressing can be used in the link layer, such as Ethernet multicast, and at the internet layer for Internet Protocol Version 4 (IPv4) or Version 6 (IPv6) multicast.

<span class="mw-page-title-main">Subnet</span> Logical subdivision of an IP network

A subnetwork, or subnet, is a logical subdivision of an IP network. The practice of dividing a network into two or more networks is called subnetting.

<span class="mw-page-title-main">Classful network</span> Early system for organizing the IPv4 address space

A classful network is an obsolete network addressing architecture used in the Internet from 1981 until the introduction of Classless Inter-Domain Routing (CIDR) in 1993. The method divides the IP address space for Internet Protocol version 4 (IPv4) into five address classes based on the leading four address bits. Classes A, B, and C provide unicast addresses for networks of three different network sizes. Class D is for multicast networking and the class E address range is reserved for future or experimental purposes.

Bogon filtering is the practice of blocking packets known as bogons, which are ones sent to a computer network claiming to originate from invalid or bogus IP addresses, known as bogon addresses.

An autonomous system (AS) is a collection of connected Internet Protocol (IP) routing prefixes under the control of one or more network operators on behalf of a single administrative entity or domain, that presents a common and clearly defined routing policy to the Internet. Each AS is assigned an autonomous system number (ASN), for use in Border Gateway Protocol (BGP) routing. Autonomous System Numbers are assigned to Local Internet Registries (LIRs) and end-user organizations by their respective Regional Internet Registries (RIRs), which in turn receive blocks of ASNs for reassignment from the Internet Assigned Numbers Authority (IANA). The IANA also maintains a registry of ASNs which are reserved for private use.

In computer networking, localhost is a hostname that refers to the current computer used to access it. The name localhost is reserved for loopback purposes. It is used to access the network services that are running on the host via the loopback network interface. Using the loopback interface bypasses any local network interface hardware.

In Internet networking, a private network is a computer network that restricts access to it. Only devices, systems, and users with appropriate authorization and authentication can connect to a private network.

In the Internet addressing architecture, the Internet Engineering Task Force (IETF) and the Internet Assigned Numbers Authority (IANA) have reserved various Internet Protocol (IP) addresses for special purposes.

<span class="mw-page-title-main">IPv4 address exhaustion</span> Depletion of unallocated IPv4 addresses

IPv4 address exhaustion is the depletion of the pool of unallocated IPv4 addresses. Because the original Internet architecture had fewer than 4.3 billion addresses available, depletion has been anticipated since the late 1980s when the Internet started experiencing dramatic growth. This depletion is one of the reasons for the development and deployment of its successor protocol, IPv6. IPv4 and IPv6 coexist on the Internet.

An IPv6 transition mechanism is a technology that facilitates the transitioning of the Internet from the Internet Protocol version 4 (IPv4) infrastructure in use since 1983 to the successor addressing and routing system of Internet Protocol Version 6 (IPv6). As IPv4 and IPv6 networks are not directly interoperable, transition technologies are designed to permit hosts on either network type to communicate with any other host.

A unique local address (ULA) is an Internet Protocol version 6 (IPv6) address in the address range fc00::/7. These addresses are non-globally reachable. For this reason, ULAs are somewhat analogous to IPv4 private network addressing, but with significant differences. Unique local addresses may be used freely, without centralized registration, inside a single site or organization or spanning a limited number of sites or organizations.

Blackhole DNS servers are Domain Name System (DNS) servers that return a "nonexistent address" answer to reverse DNS lookups for addresses reserved for private use.

<span class="mw-page-title-main">IPv6 address</span> Label to identify a network interface of a computer or other network node

An Internet Protocol version 6 address is a numeric label that is used to identify and locate a network interface of a computer or a network node participating in a computer network using IPv6. IP addresses are included in the packet header to indicate the source and the destination of each packet. The IP address of the destination is used to make decisions about routing IP packets to other networks.

<span class="mw-page-title-main">Carrier-grade NAT</span> Type of network address translation

Carrier-grade NAT, also known as large-scale NAT (LSN), is a type of network address translation (NAT) used by ISPs in IPv4 network design. With CGNAT, end sites, in particular residential networks, are configured with private network addresses that are translated to public IPv4 addresses by middlebox network address translator devices embedded in the network operator's network, permitting the sharing of small pools of public addresses among many end users. This essentially repeats the traditional customer-premise NAT function at the ISP level.

dIVI Translation IPv4/IPv6 translation technique

dIVI Translation refers to a dual stateless IPv4/IPv6 translation technique. dIVI is an extension of 1:1 stateless IPv4/IPv6 translation with features of IPv4 address sharing and dual translation. dIVI-PD is a further extension of dIVI to be well used in Wireline and Wireless (3G/4G) access environment, where the prefix delegation is preferred. dIVI-PD is now standardized as MAP-T in the IETF.

References

  1. ↑ M. Cotton; L. Vegoda; B. Haberman (April 2013). R. Bonica (ed.). Special-Purpose IP Address Registries. IETF. doi: 10.17487/RFC6890 . ISSN   2070-1721. BCP 153. RFC 6890.Best Current Practice 153. Obsoletes RFC  4773, 5156, 5735 and 5736. Updated by RFC  8190.
  2. ↑ Y. Rekhter; B. Moskowitz; D. Karrenberg; G. J. de Groot; E. Lear (February 1996). Address Allocation for Private Internets. Network Working Group. doi: 10.17487/RFC1918 . BCP 5. RFC 1918.Best Current Practice 5. Obsoletes RFC  1627 and 1597. Updated by RFC  6761.
  3. ↑ B. Carpenter; F. Baker; M. Roberts (June 2000). Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers Authority. Network Working Group. doi: 10.17487/RFC2860 . RFC 2860.Informational.
  4. 1 2 J. Weil; V. Kuarsingh; C. Donley; C. Liljenstolpe; M. Azinger (April 2012). IANA-Reserved IPv4 Prefix for Shared Address Space. Internet Engineering Task Force. doi: 10.17487/RFC6598 . ISSN   2070-1721. BCP 153. RFC 6598.Best Common Practice. Updates RFC  5735.
  5. ↑ "Re: shared address space... a reality!" . Retrieved 13 September 2012.
  6. ↑ "100.64.0.0/10 – Shared Transition Space". 2012-03-14.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.