Layer 4 Loadbalancing for MPTCP
draft-olteanu-mptcp-loadbalance-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Vladimir Olteanu , Costin Raiciu | ||
| Last updated | 2017-01-12 (Latest revision 2016-07-11) | ||
| 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
Layer 4 loadbalancers are widely used in the deployment of large- scale web services. A large number of servers accept incoming connections from clients, while multiple loadbalancers make sure that traffic is spread evenly across the servers. Due to its use of multiple subflows, Multipath TCP poses several issues to the design of a scalable layer 4 loadbalancer that supports it. This document presents two ways in which MPTCP connections can be loadbalanced across a large pool of servers. Both approaches entail using a slightly modified server stack and work well with unmodified MPTCP clients.
Authors
Vladimir Olteanu
Costin Raiciu
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)