Cryptographic protection of TCP Streams (tcpcrypt)

Document Type Replaced Internet-Draft (individual in tsv area)
Authors Andrea Bittau , Dan Boneh  , Daniel Giffin  , Mike Hamburg  , Mark Handley  , David Mazieres  , Quinn Slack  , Eric Smith 
Last updated 2015-10-17
Replaced by RFC 8548
Stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-tcpinc-tcpcrypt
Action Holders
Consensus Boilerplate Unknown
Telechat date
Responsible AD Martin Stiemerling
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


This document specifies tcpcrypt, a cryptographic protocol that protects TCP payload data and is negotiated by means of the TCP Encryption Negotiation Option (TCP-ENO) [I-D.ietf-tcpinc-tcpeno]. Tcpcrypt coexists with middleboxes by tolerating resegmentation, NATs, and other manipulations of the TCP header. The protocol is self-contained and specifically tailored to TCP implementations, which often reside in kernels or other environments in which large external software dependencies can be undesirable. Because of option size restrictions, the protocol requires one additional one-way message latency to perform key exchange. However, this cost is avoided between two hosts that have recently established a previous tcpcrypt connection.


Andrea Bittau (
Dan Boneh (
Daniel Giffin (
Mike Hamburg (
Mark Handley (
David Mazieres (
Quinn Slack (
Eric Smith (

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