Skip to main content

TCP Encapsulation Considerations

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Tommy Pauly , Eric Kinnear
Last updated 2019-01-03 (Latest revision 2018-07-02)
Replaces draft-pauly-tcp-encapsulation
RFC stream (None)
Intended RFC status (None)
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:


Network protocols other than TCP, such as UDP, are often blocked or suboptimally handled by network middleboxes. One strategy that applications can use to continue to send non-TCP traffic on such networks is to encapsulate datagrams or messages within in a TCP stream. However, encapsulating datagrams within TCP streams can lead to performance degradation. This document provides guidelines for how to use TCP for encapsulation, a summary of performance concerns, and some suggested mitigations for these concerns.


Tommy Pauly
Eric Kinnear

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