The IESG has received a request from the Transport Services WG (taps) to consider the following document: - 'An Architecture for Transport Services' <draft-ietf-taps-arch-17.txt> as Proposed Standard
The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the [email protected] mailing lists by 2023-04-14. Exceptionally, comments may be sent to [email protected] instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document describes an architecture for exposing transport protocol features to applications for network communication, a Transport Services system. The Transport Services Application Programming Interface (API) is based on an asynchronous, event-driven interaction pattern. This API uses messages for representing data transfer to applications, and 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 a Transport Service API and a Transport Services implementation. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-taps-arch/ No IPR declarations have been submitted directly on this I-D. _______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
