metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 9621: Architecture and Requirements for Transport Services

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

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.

Document record

Document ID
RFC9621
Published
January 2025
Authors
T. Pauly; B. Trammell; A. Brunstrom; G. Fairhurst; C. S. Perkins
Status
PROPOSED STANDARD
Stream
IETF
Area
wit
Pages
29
Also known as
—

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/9621-architecture-and-requirements-for-transport-services