IPv4 with 64 bit Address Space
draft-chimiak-enhanced-ipv4-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2015-12-08
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         W. Chimiak
Internet-Draft                                                 S. Patton
Intended status: Experimental                                   J. Brown
Expires: June 10, 2016         Laboratory for Telecommunication Sciences
                                                              J. Bezerra
                                        Florida International University
                                                               H. Galiza
                  Rede Nacional de Ensino e Pesquisa (RNP) - NEG AmLight
                                                                J. Smith
                                              University of Pennsylvania
                                                       December 08, 2015

                     IPv4 with 64 bit Address Space
                     draft-chimiak-enhanced-ipv4-02

Abstract

   This document describes a solution to the Internet address depletion
   problem through use of a clever IPv4 options mechanism as a solution.
   This IPv4 protocol extension is called enhanced IP (EnIP).  Because
   it is IPv4, it maximizes backward compatibility while increasing
   address space by a factor of 17.9 million.  Unlike other similar
   proposals, care was taken to avoid costly changes and requirements to
   the core network and border routers, with the exception that options
   be passed in that equipment as described below.  Because it is
   backward compatible, current IPv4 software, network equipment,
   firewalls, intrusion detection/protection, and layer 5 firewalls can
   be maintained until IPv6 system information security reaches
   acceptable maturity and availability.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on June 10, 2016.

Chimiak, et al.           Expires June 10, 2016                 [Page 1]
Internet-Draft       IPv4 with 64 bit Address Space        December 2015

Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Protocol Transitions  . . . . . . . . . . . . . . . . . .   3
     1.2.  EnIP's Use of IP Options  . . . . . . . . . . . . . . . .   4
     1.3.  Contents of this Paper  . . . . . . . . . . . . . . . . .   4
   2.  Introduction to EnIP (EnIP) . . . . . . . . . . . . . . . . .   5
     2.1.  EnIP Addressing Example . . . . . . . . . . . . . . . . .   5
     2.2.  IPv4 Header with EnIP Option Header . . . . . . . . . . .   5
       2.2.1.  IPv4 Header Fields used for EnIP  . . . . . . . . . .   6
   3.  EnIP Operation  . . . . . . . . . . . . . . . . . . . . . . .   8
     3.1.  IPv4 NAT Explanation using Figure 2 . . . . . . . . . . .   8
       3.1.1.  Typical Private IPv4 Host to a Typical Public IPv4
               Host using NAT  . . . . . . . . . . . . . . . . . . .   8
       3.1.2.  Typical Private IPv4 Host to a Typical Private IPv4
               Host using NAT  . . . . . . . . . . . . . . . . . . .   9
       3.1.3.  Private EnIP Host to a Typical Public IPv4 Host
               NAT . . . . . . . . . . . . . . . . . . . . . . . . .   9
       3.1.4.  Private EnIP Host to a Typical Private IPv4 Host
               using NAT . . . . . . . . . . . . . . . . . . . . . .  10
     3.2.  Enhanced IPv4 Explanation using an Example Figure 7 . . .  11
       3.2.1.  EIP1 constructs the Packet  . . . . . . . . . . . . .  11
       3.2.2.  EIP1 Transmits the Packet to N1 . . . . . . . . . . .  12
       3.2.3.  Packet Arrives at N2 (192.0.2.2)  . . . . . . . . . .  12
       3.2.4.  EIP2 Receives the Packet  . . . . . . . . . . . . . .  12
       3.2.5.  EIP2 Transmits a Packet to EIP1 . . . . . . . . . . .  13
Show full document text