A new Request for Comments is now available in online RFC libraries.
RFC 9621
Title: Architecture and Requirements for Transport
Services
Author: T. Pauly, Ed.,
B. Trammell, Ed.,
A. Brunstrom,
G. Fairhurst,
C. S. Perkins
Status: Standards Track
Stream: IETF
Date: January 2025
Mailbox: [email protected],
[email protected],
[email protected],
[email protected],
[email protected]
Pages: 29
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-taps-arch-19.txt
URL: https://www.rfc-editor.org/info/rfc9621
DOI: 10.17487/RFC9621
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.
This document is a product of the Transport Services Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email protected]. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
_______________________________________________
rfc-dist mailing list -- [email protected]
To unsubscribe send an email to [email protected]
http://www.rfc-editor.org
