%% You should probably cite draft-ietf-tcpinc-tcpcrypt instead of this I-D.
@techreport{bittau-tcpinc-tcpcrypt-04,
    number =    {draft-bittau-tcpinc-tcpcrypt-04},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-bittau-tcpinc-tcpcrypt/04/},
    author =    {Andrea Bittau and Dan Boneh and Daniel B. Giffin and Mike Hamburg and Mark J. Handley and David Mazieres and Quinn Slack and Eric W. Smith},
    title =     {{Cryptographic protection of TCP Streams (tcpcrypt)}},
    pagetotal = 25,
    year =      2015,
    month =     oct,
    day =       17,
    abstract =  {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.},
}