IPv6 Multihoming without Network Address Translation
draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat-04

The information below is for an old version of the document
Document Type Active Internet-Draft (v6ops WG)
Last updated 2012-02-22 (latest revision 2012-02-21)
Replaces draft-v6ops-multihoming-without-ipv6nat, draft-ietf-v6ops-multihoming-without-nat66
Stream IETF
Intended RFC status Informational
Formats plain text pdf html
Stream WG state WG Document
Consensus Unknown
Document shepherd None
IESG IESG state RFC Ed Queue
Telechat date
Responsible AD Ron Bonica
IESG note Fred Baker (fred@cisco.com) is the document shepherd.
Send notices to v6ops-chairs@tools.ietf.org, draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat@tools.ietf.org
RFC Editor RFC Editor state MISSREF
Internet Engineering Task Force                            O. Troan, Ed.
Internet-Draft                                                     Cisco
Intended status: Informational                                  D. Miles
Expires: August 24, 2012                                  Alcatel-Lucent
                                                           S. Matsushima
                                                        Softbank Telecom
                                                              T. Okimoto
                                                                NTT West
                                                                 D. Wing
                                                                   Cisco
                                                       February 21, 2012

          IPv6 Multihoming without Network Address Translation
          draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat-04

Abstract

   Network Address and Port Translation (NAPT) works well for conserving
   global addresses and addressing multihoming requirements, because an
   IPv4 NAPT router implements three functions: source address
   selection, next-hop resolution and optionally DNS resolution.  For
   IPv6 hosts one approach could be the use of NPTv6.  However, NAT
   should be avoided, if at all possible, to permit transparent end-to-
   end connectivity.  In this document, we analyze the use cases of
   multihoming.  We also describe functional requirements and possible
   solutions for multihoming without the use of NAT in IPv6 for hosts
   and small IPv6 networks that would otherwise be unable to meet
   minimum IPv6 allocation criteria.  We conclude that DHCPv6 based
   solutions are suitable to solve the multihoming issues, described in
   this document, while NPTv6 may be required as an intermediate
   solution.

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

Troan, et al.            Expires August 24, 2012                [Page 1]
Internet-Draft        IPv6 Multihoming without NAT         February 2012

   This Internet-Draft will expire on August 24, 2012.

Copyright Notice

   Copyright (c) 2012 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.

Troan, et al.            Expires August 24, 2012                [Page 2]
Internet-Draft        IPv6 Multihoming without NAT         February 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  6
   3.  IPv6 multihomed network scenarios  . . . . . . . . . . . . . .  6
     3.1.  Classification of network scenarios for multihomed host  .  6
     3.2.  Multihomed network environment . . . . . . . . . . . . . .  9
     3.3.  Problem Statement  . . . . . . . . . . . . . . . . . . . . 10
   4.  Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 11
     4.1.  End-to-End transparency  . . . . . . . . . . . . . . . . . 11
     4.2.  Scalability  . . . . . . . . . . . . . . . . . . . . . . . 12
   5.  Problem statement and analysis . . . . . . . . . . . . . . . . 12
     5.1.  Source address selection . . . . . . . . . . . . . . . . . 12
     5.2.  Next-hop selection . . . . . . . . . . . . . . . . . . . . 13
     5.3.  DNS recursive name server selection  . . . . . . . . . . . 14
   6.  Implementation approach  . . . . . . . . . . . . . . . . . . . 14
     6.1.  Source address selection . . . . . . . . . . . . . . . . . 15
     6.2.  Next-hop selection . . . . . . . . . . . . . . . . . . . . 15
     6.3.  DNS recursive name server selection  . . . . . . . . . . . 16
Show full document text