The IESG has received a request from the Transport Services WG (taps) to consider the following document: - 'An Abstract Application Layer Interface to Transport Services' <draft-ietf-taps-interface-25.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 2024-03-01. 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 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 network paths and potential transport protocols. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-taps-interface/ This draft is going for a 2nd IETF last call due to the changes resulted during the IESG evaluation. A diff towards the -20 version of this document should show the changes since the previous IETF last call. No IPR declarations have been submitted directly on this I-D. _______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
