Multihoming with IPv6-to-IPv6 Network Prefix Translation (NPTv6)
draft-bonica-v6-multihome-03
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Ron Bonica , Fred Baker , Margaret Cullen , Gregory Miller , Warren Kumari | ||
| Last updated | 2012-10-15 (latest revision 2012-04-13) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-bonica-v6-multihome-03.txt
Abstract
RFC 6296 introduces IPv6-to-IPv6 Network Prefix Translation (NPTv6). By deploying NPTv6, a site can achieve addressing independence without contributing to excessive routing table growth. Section 2.4 of RFC 6296 proposes an NPTv6 architecture for sites that are homed to multiple upstream providers. By deploying the proposed architecture, a multihomed site can achieve access redundancy and load balancing, in addition to addressing independence. This memo proposes an alternative NPTv6 architecture for hosts that are homed to multiple upstream providers. The architecture described herein provides transport-layer survivability, in addition to the benefits mentioned above. In order to provide transport-layer survivability, the architecture described herein requires a small amount of additional configuration. This memo updates RFC 6296.
Authors
Ron Bonica
(rbonica@juniper.net)
Fred Baker
(fred@cisco.com)
Margaret Cullen
(mrw@painless-security.com)
Gregory Miller
(gregory.j.miller@verizon.com)
Warren Kumari
(warren@kumari.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)