%% You should probably cite draft-ietf-taps-arch-19 instead of this revision. @techreport{ietf-taps-arch-09, number = {draft-ietf-taps-arch-09}, 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-arch/09/}, author = {Tommy Pauly and Brian Trammell and Anna Brunstrom and Gorry Fairhurst and Colin Perkins and Philipp S. Tiesel and Christopher A. Wood}, title = {{An Architecture for Transport Services}}, pagetotal = 28, year = 2020, month = nov, day = 2, abstract = {This document describes an architecture for exposing transport protocol features to applications for network communication, the Transport Services architecture. The Transport Services Application Programming Interface (API) is based on an asynchronous, event-driven interaction pattern. It uses messages for representing data transfer to applications, and it describes how implementations can use multiple IP addresses, multiple protocols, and multiple paths, and provide multiple application streams. This document further defines common terminology and concepts to be used in definitions of Transport Services APIs and implementations.}, }