RFC 8548: Cryptographic Protection of TCP Streams (tcpcrypt)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8548
- Published
- May 2019
- Authors
- A. Bittau; D. Giffin; M. Handley; D. Mazieres; Q. Slack; E. Smith
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- tsv
- Pages
- 32
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8547TCP-ENO: Encryption Negotiation OptionCurrent
May 2019
- RFC 8684TCP Extensions for Multipath Operation with Multiple AddressesCurrent
March 2020
- RFC 8699Coupled Congestion Control for RTP MediaCurrent
January 2020
- RFC 8087The Benefits of Using Explicit Congestion Notification (ECN)Current
March 2017
- RFC 8041Use Cases and Operational Experience with Multipath TCPCurrent
January 2017
- RFC 7350Datagram Transport Layer Security (DTLS) as Transport for Session Traversal Utilities for NAT (STUN)Current
August 2014
- RFC 6356Coupled Congestion Control for Multipath Transport ProtocolsCurrent
October 2011
- RFC 4850Declarative Public Extension Key for Internet Small Computer Systems Interface (iSCSI) Node ArchitectureObsoleted
April 2007
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?