A Multihoming solution using NATs
draft-akkiraju-nat-multihoming-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Yakov Rekhter , Praveen Akkiraju | ||
| Last updated | 1998-11-10 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
Multihoming to upstream ISPs is a requirement today for most networks in the Internet. The most common motivation to multihome is for reliable, non-stop access to the Internet. However, Multihoming creates scaling problems for the global routing infrastructure by making route aggregation more difficult for multihomed networks. Multihoming also complicates the addressing scheme used by the network. Another requirement for multihomed networks is the ability to load balance traffic between the multiple links to upstream ISPs. This requirement is difficult to fulfill for traffic flow in both directions as the multihomed network has no control over the return path of the packet.
Authors
Yakov Rekhter
Praveen Akkiraju
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)