TCP Encapsulation Considerations
draft-pauly-tcp-encapsulation-00

Document Type Replaced Internet-Draft (individual)
Last updated 2018-06-25
Replaced by draft-pauly-tsvwg-tcp-encapsulation
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 Replaced by draft-pauly-tsvwg-tcp-encapsulation
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-pauly-tcp-encapsulation-00.txt

Abstract

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.

Authors

Tommy Pauly (tpauly@apple.com)
Eric Kinnear (ekinnear@apple.com)

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