%% You should probably cite rfc8473 instead of this I-D.
@techreport{ietf-tokbind-https-00,
    number =    {draft-ietf-tokbind-https-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-ietf-tokbind-https/00/},
    author =    {Andrei Popov and Magnus Nyström and Dirk Balfanz and Adam Langley},
    title =     {{Token Binding over HTTP}},
    pagetotal = 9,
    year =      2015,
    month =     mar,
    day =       27,
    abstract =  {This document describes a collection of mechanisms that allow HTTP servers to cryptographically bind authentication tokens (such as cookies and OAuth tokens) to a TLS {[}RFC5246{]} connection. We describe both \_first-party\_ as well as \_federated\_ scenarios. In a first-party scenario, an HTTP server issues a security token (such as a cookie) to a client, and expects the client to send the security token back to the server at a later time in order to authenticate. Binding the token to the TLS connection between client and server protects the security token from theft, and ensures that the security token can only be used by the client that it was issued to. Federated token bindings, on the other hand, allow servers to cryptographically bind security tokens to a TLS {[}RFC5246{]} connection that the client has with a \_different\_ server than the one issuing the token. This Internet-Draft is a companion document to The Token Binding Protocol {[}TBPROTO{]}},
}