I-D Action: draft-chen-ati-adaptive-ipv4-address-space-14.txt

internet-drafts@ietf.org Thu, 14 December 2023 22:52 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: i-d-announce@ietf.org
Delivered-To: i-d-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E368C14F5FF for <i-d-announce@ietf.org>; Thu, 14 Dec 2023 14:52:05 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-chen-ati-adaptive-ipv4-address-space-14.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 12.0.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <170259432522.33107.2120608575562554135@ietfa.amsl.com>
Date: Thu, 14 Dec 2023 14:52:05 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/i-d-announce/g12_mdI6UeXtZBvfXBJfpFIE_9g>
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.39
List-Id: Internet Draft Announcements only <i-d-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/i-d-announce/>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>, <mailto:i-d-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2023 22:52:05 -0000

Internet-Draft draft-chen-ati-adaptive-ipv4-address-space-14.txt is now
available.

   Title:   Adaptive IPv4 Address Space
   Authors: Abraham Y. Chen
            Ramamurthy R. Ati
            Abhay Karandikar
            David R. Crowe
   Name:    draft-chen-ati-adaptive-ipv4-address-space-14.txt
   Pages:   70
   Dates:   2023-12-14

Abstract:

   This document describes a solution to the Internet address depletion
   issue through the use of an existing Option mechanism that is part of
   the original IPv4 protocol. This proposal, named EzIP (phonetic for
   Easy IPv4), outlines the IPv4 public address pool expansion and the
   Internet system architecture enhancement considerations. EzIP may
   expand an IPv4 address by a factor of 256M without affecting the
   existing IPv4 based Internet, or the current private networks. It is
   in full conformance with the IPv4 protocol, and supports not only
   both direct and private network connectivity, but also their
   interoperability. EzIP deployments may coexist with existing Internet
   traffic and IoTs (Internet of Things) operations without perturbing
   their setups, while offering end-users the freedom to indepdently
   choose which service. EzIP may be implemented as a software or
   firmware enhancement to Internet edge routers or private network
   routing gateways, wherever needed, or simply installed as an inline
   adjunct hardware module between the two, enabling a seamless
   introduction. The 256M case detailed here establishes a complete
   spherical layer of an overlay of routers for interfacing between the
   Internet fabic (core plus edge routers) and the end user premises or
   IoTs. Incorporating caching proxy technology in the gateway, a fairly
   large geographical region may enjoy address expansion based on as few
   as one ordinary IPv4 public address utilizing IP packets with
   degenerated EzIP header. If IPv4 public pool allocations were
   reorganized, the assignable pool could be multiplied 512M fold or
   even more. Enabling hierarchical address architecture which
   facilitates both hierarchical and mesh routing, EzIP can provide
   nearly the same order of magnitude of address pool resources as IPv6
   while streamlining the administrative aspects of it. The basic EzIP
   will immediately resolve the local IPv4 address shortage, while being
   transparent to the rest of the Internet as a new parallel facility.
   Under the Dual-Stack environment, these proposed interim facilities
   will relieve the IPv4 address shortage issue, while affording IPv6
   more time to reach maturity for providing the availability levels
   required for delivering a long-term general service. The basic EzIP
   may be deployed in two distinctive phases. First, the CG-NAT
   operation may be enhanced by enabling the use of 240/4 netblock in
   addition to the current 100.64/10 netblock of RFC6598. This makes
   end-to-end connectivity feasible within the service area of each
   240/4 netblock. Second, this capability may extend to global coverage
   with the use of the Option Word mechanism in the IP header.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-chen-ati-adaptive-ipv4-address-space/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-chen-ati-adaptive-ipv4-address-space-14

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-chen-ati-adaptive-ipv4-address-space-14

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts