DHCP Options for 0-RTT TCP Converters
draft-boucadair-tcpm-dhc-converter-00

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2018-10-05 (latest revision 2018-04-03)
Replaces draft-boucadair-mptcp-dhc
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-boucadair-tcpm-dhc-converter-00.txt

Abstract

Because of the lack of Multipath TCP (MPTCP) support at the server side, some service providers now consider a network-assisted model that relies upon the activation of a dedicated function called Converters. Network-assisted MPTCP deployment models are designed to facilitate the adoption of MPTCP for the establishment of multi-path communications without making any assumption about the support of MPTCP by the communicating peers. Converters located in the network are responsible for establishing multi-path communications on behalf of endpoints, thereby taking advantage of MPTCP capabilities to achieve different goals that include (but are not limited to) optimization of resource usage (e.g., bandwidth aggregation), of resiliency (e.g., primary/backup communication paths), and traffic offload management. This document focuses on the explicit deployment scheme where the identity of the Converters is explicitly configured on connected hosts. This document specifies DHCP (IPv4 and IPv6) options to configure hosts with Converters parameters.

Authors

Mohamed Boucadair (mohamed.boucadair@orange.com)
Christian Jacquenet (christian.jacquenet@orange.com)
Reddy K (tireddy@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)