IPv6 Multihoming without Network Address Translation
draft-ietf-v6ops-multihoming-without-nat66-00
Document | Type |
Replaced Internet-Draft
(v6ops WG)
Expired & archived
|
|
---|---|---|---|
Authors | Ole Trøan , David Miles , Satoru Matsushima , Tadahisa Okimoto , Dan Wing | ||
Last updated | 2011-03-30 (Latest revision 2010-12-06) | ||
Replaces | draft-troan-multihoming-without-nat66, draft-v6ops-multihoming-without-nat66 | ||
Replaced by | draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | WG Document | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-v6ops-ipv6-multihoming-without-ipv6nat | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 NAT. However, NAT should be avoided, if at all possible, to permit transparent host-to- host connectivity. In this document, we analyze the use cases of multihoming. We also describe functional requirements 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 .
Authors
Ole Trøan
David Miles
Satoru Matsushima
Tadahisa Okimoto
Dan Wing
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)