RFC 9623: Implementing Interfaces to Transport Services
In plain English — editorial summary, not part of the RFC
The Transport Services System enables applications to use transport protocols flexibly for network communication and defines a protocol-independent Transport Services Application Programming Interface (API) that is based on an asynchronous, event-driven interaction pattern. This document serves as a guide to implementing such a system.
Document record
- Document ID
- RFC9623
- Published
- January 2025
- Authors
- A. Brunstrom; T. Pauly; R. Enghardt; P.S. Tiesel; M. Welzl
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 46
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9622An Abstract Application Programming Interface (API) for Transport ServicesCurrent
January 2025
- RFC 9621Architecture and Requirements for Transport ServicesCurrent
January 2025
- RFC 9626Video Frame Marking RTP Header ExtensionCurrent
March 2025
- RFC 9628RTP Payload Format for VP9 VideoCurrent
March 2025
- RFC 9607RTP Payload Format for the Secure Communication Interoperability Protocol (SCIP) CodecCurrent
July 2024
- RFC 9601Propagating Explicit Congestion Notification across IP Tunnel Headers Separated by a ShimCurrent
August 2024
- RFC 9599Guidelines for Adding Congestion Notification to Protocols that Encapsulate IPCurrent
August 2024
- RFC 9648YANG Data Model for TCPCurrent
October 2024
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?