RFC 9621

Architecture and Requirements for Transport Services, January 2025

File formats:

icon for HTML icon for text file icon for v3pdf icon for XML
Also available: XML file for editing
 
Status:
PROPOSED STANDARD
Authors:
T. Pauly, Ed.
B. Trammell, Ed.
A. Brunstrom
G. Fairhurst
C. S. Perkins
Stream:
IETF
Source:
taps (wit)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC9621

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 9621


Abstract

This document describes an architecture that exposes transport protocol features to applications for network communication. 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 a Transport Services Implementation can use multiple IP addresses, multiple protocols, and multiple paths and can provide multiple application streams. This document provides the architecture and requirements. It defines common terminology and concepts to be used in definitions of a Transport Services API and a Transport Services Implementation.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search