Skip to main content

Cryptographic Protection of TCP Streams (tcpcrypt)
RFC 8548

Revision differences

Document history

Date By Action
2019-05-23
(System) IANA registries were updated to include RFC8548
2019-05-22
(System)
Received changes through RFC Editor sync (created alias RFC 8548, changed title to 'Cryptographic Protection of TCP Streams (tcpcrypt)', changed abstract to 'This document …
Received changes through RFC Editor sync (created alias RFC 8548, changed title to 'Cryptographic Protection of TCP Streams (tcpcrypt)', changed abstract to 'This document specifies "tcpcrypt", a TCP encryption protocol designed for use in conjunction with the TCP Encryption Negotiation Option (TCP-ENO).  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 the size of TCP options is limited, the protocol requires one additional one-way message latency to perform key exchange before application data can be transmitted.  However, the extra latency can be avoided between two hosts that have recently established a previous tcpcrypt connection.', changed pages to 32, changed standardization level to Experimental, changed state to RFC, added RFC published event at 2019-05-22, changed IESG state to RFC Published)
2019-05-22
(System) RFC published