Browse Prior Art Database

IPv6 Multihoming without Network Address Translation (RFC7157)

IP.com Disclosure Number: IPCOM000235966D
Original Publication Date: 2014-Mar-01
Included in the Prior Art Database: 2014-Apr-01
Document File: 44 page(s) / 49K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

O. Troan: AUTHOR [+6]

Abstract

In this document, we analyze the use cases of multihoming, describe functional requirements, and describe the problems with IPv6 multihoming. There are two ways to avoid the problems of IPv6 multihoming:

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 5% of the total text.

Internet Engineering Task Force (IETF)                     O. Troan, Ed. Request for Comments: 7157                                         Cisco Category: Informational                                         D. Miles ISSN: 2070-1721                                             Google Fiber                                                            S. Matsushima                                                         Softbank Telecom                                                               T. Okimoto                                                                 NTT West                                                                  D. Wing                                                                    Cisco                                                               March 2014

           IPv6 Multihoming without Network Address Translation

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 IPv6-to-IPv6 Network    Prefix Translation (NPTv6).  However, NAT and NPTv6 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, but NPTv6 may be required as an intermediate solution.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see Sect...