%% You should probably cite rfc8303 instead of this I-D.
@techreport{ietf-taps-transports-usage-07,
    number =    {draft-ietf-taps-transports-usage-07},
    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-taps-transports-usage/07/},
    author =    {Michael Welzl and Michael Tüxen and Naeem Khademi},
    title =     {{On the Usage of Transport Features Provided by IETF Transport Protocols}},
    pagetotal = 50,
    year =      2017,
    month =     aug,
    day =       25,
    abstract =  {This document describes how the transport protocols Transmission Control Protocol (TCP), MultiPath TCP (MPTCP), Stream Control Transmission Protocol (SCTP), User Datagram Protocol (UDP) and Lightweight User Datagram Protocol (UDP-Lite) expose services to applications and how an application can configure and use the features that make up these services. It also discusses the service provided by the Low Extra Delay Background Transport (LEDBAT) congestion control mechanism. The description results in a set of transport abstractions that can be exported in a TAPS API. For UDP and UDP-Lite, the first step of the protocol analysis -- a discussion of relevant RFC text -- is documented in {[}FJ16{]}. XX RFC ED - PLEASE REPLACE {[}FJ16{]} WITH THE CORRECT RFC NUMBER XXX},
}