RFC 9622
An Abstract Application Programming Interface (API) for Transport Services, January 2025
- File formats:
- Also available: XML file for editing
- Status:
- PROPOSED STANDARD
- Authors:
- B. Trammell, Ed.
M. Welzl, Ed.
R. Enghardt
G. Fairhurst
M. Kühlewind
C. S. Perkins
P.S. Tiesel
T. Pauly - Stream:
- IETF
- Source:
- taps (wit)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC9622
Discuss this RFC: Send questions or comments to the mailing list taps@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 9622
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 Socket API as the common interface to the transport layer, in an environment where endpoints could select from multiple network paths and potential transport protocols.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.