Considerations on HIP based IPv6 multi-homing
draft-nikander-multi6-hip-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Pekka Nikander | ||
| Last updated | 2004-07-15 | ||
| 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 Host Identity Protocol implements the identifier locator separation by introduing a new name space and a new layer to the IP stack. The new structure insulates the transport layer protocols from the internetworking layer, thereby allowing transport sessions to remain unaffected even if the underlying IP addresses change. That, in turn, seems to make it easier to solve the so called site multi-homing problem than without introducing such an indirection layer. This document discusses how the proposed HIP mobility and multi-homing solution, described separately, would fit to the IETF multi6 working group requirements.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)