Multihoming support for Residential Gateways
draft-seite-dmm-rg-multihoming-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Pierrick Seite , Alper E. Yegin , Sri Gundavelli | ||
| Last updated | 2015-04-30 (Latest revision 2014-10-27) | ||
| Replaced by | draft-ietf-dmm-mag-multihoming, RFC 8278 | ||
| RFC stream | (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 Quality-of-Experience of a fixed-network user can be significantly improved by enabling the Residential Gateway (RG) providing IP connectivity services to connect to the internet through multiple access networks (Example: LTE and DSL) and use all the available network bandwidth for the user traffic. This approach enables a service provider to leverage all the availble access networks and to offer guaranteed Quality-of-Service to the end-user on any application basis. Furthermore, the mobility functions in the residential gateway and in the service provider network will be able to monitor the performance of all the access paths and dynamically change the routing path for an application. This document investigates the use of IP mobility protocols for supporting this use-case and it also identifies the needed protocol extensions. However, those extensions will be specified in a companion document.
Authors
Pierrick Seite
Alper E. Yegin
Sri Gundavelli
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)