%% You should probably cite draft-ietf-taps-arch-19 instead of this revision. @techreport{ietf-taps-arch-04, number = {draft-ietf-taps-arch-04}, 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/04/}, 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 = 25, year = , month = , day = , abstract = {This document provides an overview of the architecture of Transport Services, a model for exposing transport protocol features to applications for network communication. In contrast to what is provided by most existing Application Programming Interfaces (APIs), Transport Services is based on an asynchronous, event-driven interaction pattern; it uses messages for representing data transfer to applications; and it assumes an implementation that can use multiple IP addresses, multiple protocols, and multiple paths, and provide multiple application streams. This document further defines the common set of terminology and concepts to be used in definitions of Transport Services APIs and implementations.}, }