Multipath TCP Middlebox Behavior
draft-lopez-mptcp-middlebox-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Edward Lopez | ||
Last updated | 2015-05-17 (Latest revision 2014-11-13) | ||
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
As implementation of MPTCP continues to grow, there will be interaction concerns regarding MPTCP sessions relative to the functionality of middleboxes, particularly those focused on network- based security. The purpose of this draft is to review this interaction of MPTCp sessions and middleboxes, the likely response of middlebox providers in dealing with any functional degradation due to MPTCP, and the potential requirements to support proxy functionality for MPTCP sessions.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)