0-RTT TCP Convert Protocol
RFC 8803, “0-RTT TCP Convert Protocol”, is an Experimental document published in July 2020 by O. Bonaventure, M. Boucadair, S. Gundavelli, S. Seo, B. Hesmans. The canonical text is published by the RFC Editor.
Abstract
This document specifies an application proxy, called Transport Converter, to assist the deployment of TCP extensions such as Multipath TCP. A Transport Converter may provide conversion service for one or more TCP extensions. The conversion service is provided by means of the 0-RTT TCP Convert Protocol (Convert).
This protocol provides 0-RTT (Zero Round-Trip Time) conversion service since no extra delay is induced by the protocol compared to connections that are not proxied. Also, the Convert Protocol does not require any encapsulation (no tunnels whatsoever).
This specification assumes an explicit model, where the Transport Converter is explicitly configured on hosts. As a sample applicability use case, this document specifies how the Convert Protocol applies for Multipath TCP.
What “Experimental” means
Describes a specification that is part of a research or development effort, published so the community can gain experience with it.
The canonical text of RFC 8803 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
- RFC 8802 The Quality for Service Protocol
- RFC 8804 Content Delivery Network Interconnection Request Routing Extensions
- RFC 8801 Discovering Provisioning Domain Names and Data
- RFC 8805 A Format for Self-Published IP Geolocation Feeds
- RFC 8800 Path Computation Element Communication Protocol Extension for Label Switched Path Diversity Constraint Signaling
- RFC 8806 Running a Root Server Local to a Resolver
- RFC 8799 Limited Domains and Internet Protocols
- RFC 8807 Login Security Extension for the Extensible Provisioning Protocol