%% You should probably cite draft-kuehlewind-taps-crypto-sep-03 instead of this revision.
@techreport{kuehlewind-taps-crypto-sep-00,
    number =    {draft-kuehlewind-taps-crypto-sep-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-kuehlewind-taps-crypto-sep/00/},
    author =    {Mirja Kühlewind and Tommy Pauly and Christopher A. Wood},
    title =     {{Separating Crypto Negotiation and Communication}},
    pagetotal = 12,
    year =      2017,
    month =     jul,
    day =       3,
    abstract =  {Due to the latency involved in connection setup and security handshakes, there is an increasing deployment of cryptographic session resumption mechanisms. While cryptographic context and endpoint capabilities need to be be known before encrypted application data can be sent, there is otherwise no technical constraint that the crypto handshake must be performed on the same transport connection. This document recommends a logical separation between the mechanism(s) used to negotiate capabilities and set up encryption context (handshake protocol), the application of encryption and authentication state to data (record protocol), and the associated transport connection(s).},
}