Gap Analysis for IPv4 Sunset
draft-ietf-sunset4-gapanalysis-07

 
Document
Type Active Internet-Draft (sunset4 WG)
Last updated 2015-04-22
Replaces draft-dionne-sunset4-v4gapanalysis
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream
WG state WG Document Dec 2015
Document shepherd No shepherd assigned
IESG
IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

Network Working Group                                       S. Perreault
Internet-Draft                                       Jive Communications
Intended status: Informational                                   T. Tsou
Expires: October 24, 2015                      Huawei Technologies (USA)
                                                                 C. Zhou
                                                     Huawei Technologies
                                                                  P. Fan
                                                            China Mobile
                                                          April 22, 2015

                      Gap Analysis for IPv4 Sunset
                   draft-ietf-sunset4-gapanalysis-07

Abstract

   Sunsetting IPv4 refers to the process of turning off IPv4
   definitively.  It can be seen as the final phase of the migration to
   IPv6.  This memo enumerates difficulties arising when sunsetting
   IPv4, and identifies the gaps requiring additional work.

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 October 24, 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

Perreault, et al.       Expires October 24, 2015                [Page 1]
Internet-Draft          IPv4 Sunsetting Analysis              April 2015

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Related Work  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Remotely Disabling IPv4 . . . . . . . . . . . . . . . . . . .   4
     3.1.  Indicating that IPv4 connectivity is unavailable  . . . .   4
     3.2.  Disabling IPv4 in the LAN . . . . . . . . . . . . . . . .   4
   4.  Client Connection Establishment Behavior  . . . . . . . . . .   5
   5.  Disabling IPv4 in Operating System and Applications . . . . .   5
   6.  On-Demand Provisioning of IPv4 Addresses  . . . . . . . . . .   6
   7.  IPv4 Address Literals . . . . . . . . . . . . . . . . . . . .   6
   8.  Managing Router Identifiers . . . . . . . . . . . . . . . . .   7
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   10. Security Considerations . . . . . . . . . . . . . . . . . . .   7
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   7
   12. Informative References  . . . . . . . . . . . . . . . . . . .   7
   Appendix A.  Solution Ideas . . . . . . . . . . . . . . . . . . .   9
     A.1.  Remotely Disabling IPv4 . . . . . . . . . . . . . . . . .   9
       A.1.1.  Indicating that IPv4 connectivity is unavailable  . .   9
       A.1.2.  Disabling IPv4 in the LAN . . . . . . . . . . . . . .   9
     A.2.  Client Connection Establishment Behavior  . . . . . . . .  10
     A.3.  Disabling IPv4 in Operating System and Applications . . .  10
     A.4.  Managing Router Identifiers . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   The final phase of the migration to IPv6 is the sunset of IPv4, that
   is turning off IPv4 definitively on the attached networks and on the
   upstream networks.

   Some current implementation behavior makes it hard to sunset IPv4.
   Additionally, some new features could be added to IPv4 to make its
   sunsetting easier.  This document analyzes the current situation and
   proposes new work in this area.

   The decision about when to turn off IPv4 is out of scope.  This
   document merely attempts to enumerate the issues one might encounter
   if that decision is made.
Show full document text