Skip to main content

TCP-ENO: Encryption Negotiation Option
draft-bittau-tcpinc-tcpeno-02

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Andrea Bittau, Dan Boneh , Daniel B. Giffin , Mark J. Handley , David Mazieres , Eric W. Smith
Last updated 2015-09-10
Replaced by draft-ietf-tcpinc-tcpeno
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-tcpinc-tcpeno
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:

Abstract

Despite growing adoption of TLS [RFC5246], a significant fraction of TCP traffic on the Internet remains unencrypted. The persistence of unencrypted traffic can be attributed to at least two factors. First, some legacy protocols lack a signaling mechanism (such as a "STARTTLS" command) by which to convey support for encryption, making incremental deployment impossible. Second, legacy applications themselves cannot always be upgraded, requiring a way to implement encryption transparently entirely within the transport layer. The TCP Encryption Negotiation Option (TCP-ENO) addresses both of these problems through a new TCP option kind providing out-of-band, fully backward-compatible negotiation of encryption.

Authors

Andrea Bittau
Dan Boneh
Daniel B. Giffin
Mark J. Handley
David Mazieres
Eric W. Smith

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