IETF Proposes IPv4 Service over IPv6-Only Networks Without ARP

Introduction to the Proposal

IPv6-only networks typically rely on legacy IPv4 subnets and ARP for compatibility. The IETF proposal seeks to eliminate this dependency, enabling IPv4 to function as a service directly over an IPv6-only framework, streamlining network operations.

Background of the Discussion

The proposal emerged from discussions at RIPE 91, where many network operators acknowledged the challenges of maintaining IPv4 alongside IPv6. The Internet-Draft, titled draft-vanmook-intarea-ipv6-resolved-gateway, has reached its third version and will be presented at IETF 126 in Vienna.

Challenges of Dual-Stack Networks

Despite advancements, many operators continue to operate dual-stack environments due to legacy applications and systems expecting IPv4. This leads to increased complexity, including managing two address families and the overhead from ARP operations, which can create significant network issues.

Operational Costs of ARP

ARP protocols can be detrimental in large-scale environments, leading to broadcast storms and cache problems. Data suggests that networks can experience high levels of ARP requests, causing operational inefficiencies and complexity in debugging and maintenances.

Significance of IPv4 Over IPv6

This proposal could potentially reduce operational tasks while addressing the increasing market prices of IPv4 addresses. By simplifying the network structure to an IPv6-only model with IPv4 as a service, operators can enhance both performance and reliability.