Multihoming in Homenet
draft-haddad-homenet-multihomed-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Wassim Haddad , Damien Saucez , Joel M. Halpern | ||
| Last updated | 2013-03-29 (Latest revision 2012-09-25) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| 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
So far, multihoming in Homenet must be supported by the hosts as there is no mean to use simultaneously the different Internet Service Providers of the "Homenet" without risking flow disruption. In this memo, we describe the problem statement for multihoming in Homenet. We also propose a high level solution that answers this particular problem.
Authors
Wassim Haddad
Damien Saucez
Joel M. Halpern
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)