A road-map for multihoming in IPv6
draft-kurtis-multi6-roadmap-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Kurt Erik Lindqvist | ||
| Last updated | 2003-02-25 | ||
| 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
IPv6 was decided as the replacement to the widely deployed IPv4 in 1992. The new protocol was designed to meet a number of criteria that at that time was seen as the failures of IPv4, such as security and limited address space. IPv6 meet these needs, but it fails to meet other needs of the Internet of today such as scalable solutions for multihoming and portable address space for end-sites. The effects of the lack of scalable solutions to this is widely documented. In order to solve the multihoming scalability problems, the multi6 working group was created in the IETF. This group have so far not yet produced any documents as it has been hard to find consensus on even the most basic documents such as requirements. Multi6 have also suffered from problems reaching consensus on what type of solution will be required moving forward, and the attempt of trying to come up with a 'fit-all' solution from day one. This document tries to outline steps that could be taken to better understand the problem and what steps could be taken as we bit by bit tries to address the problem.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)