metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 9622: An Abstract Application Programming Interface (API) for Transport Services

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC9622
Published
January 2025
Authors
B. Trammell; M. Welzl; R. Enghardt; G. Fairhurst; M. Kühlewind; C. S. Perkins; P.S. Tiesel; T. Pauly
Status
PROPOSED STANDARD
Stream
IETF
Area
wit
Pages
84
Also known as
—

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/9622-an-abstract-application-programming-interface-api-for-transport-services