Internet Protocol, Version 4 64-bit Address Extension
draft-tian-ipv4-64-bit-00

Document Type Active Internet-Draft (individual)
Last updated 2019-04-15
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)
Versions: 00

INTERNET-DRAFT                                                   Bo Tian
Intended Status: Proposed Standard                                 Calix
Expires: October 2019

                                                          April 15, 2019

       Internet Protocol, Version 4 64-bit Address Extension
                    draft-tian-ipv4-64-bit-00

Abstract

   This document describes a 64-bit address mechanism that serves as an
   extension to IPv4, namely, IPv4_64.  As an add-on to IPv4, this
   extension is designed to solve the IPv4 address exhaustion issue in
   an innovative way, and slightly improve some IPv4 functions at the
   same time.

Status of This Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html



Copyright Notice

   Copyright (c) 2019 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  . . . . . . . . . . . . . . . . . . . . . . . .   4
     1.1  Motivation   . . . . . . . . . . . . . . . . . . . . . . .   4
     1.2  IPv4_64 Header . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
   3.  IPv4_64 Header Format . . . . . . . . . . . . . . . . . . . .   5
   4.  IPv4_64 Extension Headers . . . . . . . . . . . . . . . . . .   6
   5.  IPv4-Compatible Considerations  . . . . . . . . . . . . . . .   6
     5.1  Res Field  . . . . . . . . . . . . . . . . . . . . . . . .   7
     5.2  IPv4-Compatible IPv4_64 Address  . . . . . . . . . . . . .   7
     5.3  The Loose-in and Strict-out Rule . . . . . . . . . . . . .   7 
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   7. Security Considerations  . . . . . . . . . . . . . . . . . . .   8
   8. REFERENCES . . . . . . . . . . . . . . . . . . . . . . . . . .   9 
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   9 
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   9  
   Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10 


1.  Introduction

   Although IPv4 address exhaustion has occurred, due to the risk, cost
   and complexity of applying new network technologies, it is clear that
   IPv4 is going to exist for a long time.  But current methods used to
   prolong the lifespan of IPv4 can only alleviated IPv4 address
   exhaustion issue to some extent.  Applying those technologies will
   inevitably face the continuously growing costs of running the IPv4
   network and the deficiency of the network connectivity.  This
   document describes a 64-bit address mechanism that serves as the
   extension to IPv4, namely, IPv4_64.  As an add-on to IPv4, this
   extension is designed to solve the IPv4 address depleted issue in an
   innovative way, and slightly improve some IPv4 functions at the same
   time.

   The choice of 64-bit is because that modern computer science has
   favoured 64-bit more than other number of bits as the upgrade from
   32-bit.  The 64-bit addresses will be more natural for modern
   computer and human to handle.

1.1  Motivation

   To mitigate IPv4 address exhaustion issue, a 64-bit address mechanism
   is introduced.  And a new header format is introduced to keep those
   64-bit address information.  When the originator or recipient is
   64-bit address or need to bear any other 64-bit address information
   in the header, the IPv4_64 header is used instead of the IPv4 one. 

   The introduction of the IPv4_64 header also makes it possible to
   improve some functions of IPv4 while not breaking current IPv4
   network functions.  Most of those improvements are heavenly borrowed
Show full document text