Multi-Homing Tunnel Broker (MHTB)
draft-bagnulo-multi6-mhtb-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Marcelo Bagnulo | ||
| Last updated | 2004-02-02 | ||
| 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-bagnulo-multi6-mhtb-00.txt
Abstract
RFC 3178 [1] describes a solution to provide site multi-homing support in IPv6. RFC 3178 multi-homing solution uses tunnels between the different ISPs and the multi-homed site to provide alternative paths in case that one of the exit links is down, protecting the multi-homed site from outages in the direct link with its providers. However, the wide adoption of RFC 3178 multi-homing solution implies the manual configuration of numerous tunnels on the ISPs, which may impose an important workload in ISP network administrators. This note proposes the usage of Multi-Homing Tunnel Brokers to automatically configure the ISP tunnel endpoint in order to ease the adoption of the solution.
Authors
Marcelo Bagnulo (marcelo@it.uc3m.es)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)