%% You should probably cite draft-ietf-taps-interface-26 instead of this revision.
@techreport{ietf-taps-interface-18,
    number =    {draft-ietf-taps-interface-18},
    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-interface/18/},
    author =    {Brian Trammell and Michael Welzl and Reese Enghardt and Gorry Fairhurst and Mirja Kühlewind and Colin Perkins and Philipp S. Tiesel and Tommy Pauly},
    title =     {{An Abstract Application Layer Interface to Transport Services}},
    pagetotal = 91,
    year =      2022,
    month =     oct,
    day =       24,
    abstract =  {This document describes an abstract application programming interface, API, to the transport layer that enables the selection of transport protocols and network paths dynamically at runtime. This API enables faster deployment of new protocols and protocol features without requiring changes to the applications. The specified API follows the Transport Services architecture by providing asynchronous, atomic transmission of messages. It is intended to replace the BSD sockets API as the common interface to the transport layer, in an environment where endpoints could select from multiple interfaces and potential transport protocols.},
}