IPv6-only Terminology Definition
draft-palet-v6ops-ipv6-only-03

Document Type Active Internet-Draft (individual)
Last updated 2017-10-30
Replaces draft-palet-ietf-v6ops-ipv6-only
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
v6ops                                                  J. Palet Martinez
Internet-Draft                                          The IPv6 Company
Intended status: Informational                          October 30, 2017
Expires: May 3, 2018

                    IPv6-only Terminology Definition
                     draft-palet-v6ops-ipv6-only-03

Abstract

   This document defines the terminology regarding the usage of
   expressions such as "IPv6-only", in order to avoid confusions when
   using them in IETF and other documents, in reference to what is the
   actual functionalities being used (not the actual protocol support).

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 https://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 May 3, 2018.

Copyright Notice

   Copyright (c) 2017 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
   (https://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.

Palet Martinez             Expires May 3, 2018                  [Page 1]
Internet-Draft            IPv6-only Definition              October 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Context . . . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Definition of IPv6-only . . . . . . . . . . . . . . . . . . .   3
   4.  Dual-stack  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Native dual-stack . . . . . . . . . . . . . . . . . . . . . .   3
   6.  IPv6-only network . . . . . . . . . . . . . . . . . . . . . .   3
   7.  IPv6-only WAN/access  . . . . . . . . . . . . . . . . . . . .   4
   8.  IPv6-only LAN . . . . . . . . . . . . . . . . . . . . . . . .   4
   9.  IPv6-only host/router . . . . . . . . . . . . . . . . . . . .   4
   10. Transitional IPv6 host/router . . . . . . . . . . . . . . . .   4
   11. Other cases . . . . . . . . . . . . . . . . . . . . . . . . .   4
   12. Security Considerations . . . . . . . . . . . . . . . . . . .   4
   13. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   14. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   Due to the nature of the Internet and the different types of users,
   parts of a network, providers, flows, etc., there is not a single and
   easy way to categorically say something such as "IPv6-only".

   The goal of this document is to depict this situation and agree in a
   common language to be used for IETF and other documents, in order to
   facilitate ourselves and future readers, the correct understanding of
   what we are talking about.

   Note that all the references in this document are regarding the
   actual usage of IPv4/IPv6, not the support of those protocols by
   nodes.  For example, a device or access network may support both IPv4
   and IPv6, however actually is only "natively" forwarding IPv6.

2.  Context

   The transition from IPv4 to IPv6 is not something that can be done,
   in the large majority of the cases, overnight and in a single step.
   Consequently, in general, we are unable to talk about a whole network
   having a "single and uniform" status regarding IPv6, at least not in
   the early deployment stages of an operator network.

   Even if possible, it is not frequent to deploy new IPv6 networks
   which have no IPv4 connectivity at all, because at the current phase
   of the universal goal of the IPv6 deployment, almost every network
   still need to provide some kind of "access" to IPv4 sites.  It is not
   feasible for most of the operators to tell their customers "I can
Show full document text