Routing support for IPv6 Multi-homing
draft-bragg-ipv6-multihoming-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Nigel Bragg | ||
| Last updated | 2000-12-01 | ||
| 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
The IPv6 Addressing scheme mandates provider addressing to achieve aggregation. Multi-homing is a fact of life. Current proposals to reconcile these requirements involve mitigation, by constraining deployment topologies to avoid loss of aggregation in the backbone only. This draft views the combined requirement as equivalent to the use of loose source routing by hosts, and makes some outline proposals as to how this can be achieved.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)