RFC 8803: 0-RTT TCP Convert Protocol
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8803
- Published
- July 2020
- Authors
- O. Bonaventure; M. Boucadair; S. Gundavelli; S. Seo; B. Hesmans
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- wit
- Pages
- 47
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8673HTTP Random Access and Live ContentCurrent
November 2019
- RFC 9343IPv6 Application of the Alternate-Marking MethodCurrent
December 2022
- RFC 9422The LIMITS SMTP Service ExtensionCurrent
February 2024
- RFC 9557Date and Time on the Internet: Timestamps with Additional InformationCurrent
April 2024
- RFC 7926Problem Statement and Architecture for Information Exchange between Interconnected Traffic-Engineered NetworksCurrent
July 2016
- RFC 9809X.509 Certificate Extended Key Usage (EKU) for Configuration, Updates, and Safety-Critical CommunicationCurrent
July 2025
- RFC 7781Transparent Interconnection of Lots of Links (TRILL): Pseudo-Nickname for Active-Active AccessCurrent
February 2016
- RFC 7629Flow-Binding Support for Mobile IPCurrent
August 2015
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?