<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-tcpinc-tcpeno" target="https://datatracker.ietf.org/doc/html/draft-ietf-tcpinc-tcpeno-15">
   <front>
      <title>TCP-ENO: Encryption Negotiation Option</title>
      <author initials="A." surname="Bittau" fullname="Andrea Bittau">
         <organization>Google</organization>
      </author>
      <author initials="D. B." surname="Giffin" fullname="Daniel B. Giffin">
         <organization>Stanford University</organization>
      </author>
      <author initials="M. J." surname="Handley" fullname="Mark J. Handley">
         <organization>University College London</organization>
      </author>
      <author initials="D." surname="Mazieres" fullname="David Mazieres">
         <organization>Stanford University</organization>
      </author>
      <author initials="E. W." surname="Smith" fullname="Eric W. Smith">
         <organization>Kestrel Institute</organization>
      </author>
      <date month="November" day="16" year="2017" />
      <abstract>
	 <t>   Despite growing adoption of TLS, 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
   &quot;STARTTLS&quot; 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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-tcpinc-tcpeno-15" />
   
</reference>
