[Taps] Re: RFC 9622 on An Abstract Application Programming Interface (API) for Transport Services

[Michael Welzl <[e-mail]>]

Hipp hipp !!
:-)


> On 23 Jan 2025, at 13:52, Mirja Kuehlewind <mirja.kuehlewind=[e-mail]> wrote:
> 
> Yeah!!! Thanks everybody!
> 
> 
> 
> On 23.01.25, 00:22, "[e-mail] <mailto:[e-mail]>" <[e-mail] <mailto:[e-mail]>> wrote:
> 
> 
> A new Request for Comments is now available in online RFC libraries.
> 
> 
> 
> 
> RFC 9622
> 
> 
> Title: An Abstract Application Programming Interface (API)
> for Transport Services
> Author: B. Trammell, Ed.,
> M. Welzl, Ed.,
> R. Enghardt,
> G. Fairhurst,
> M. Kühlewind,
> C. S. Perkins,
> P.S. Tiesel,
> T. Pauly
> Status: Standards Track
> Stream: IETF
> Date: January 2025
> Mailbox: [e-mail] <mailto:[e-mail]>,
> [e-mail] <mailto:[e-mail]>,
> [e-mail] <mailto:[e-mail]>,
> [e-mail] <mailto:[e-mail]>,
> [e-mail] <mailto:[e-mail]>,
> [e-mail] <mailto:[e-mail]>,
> [e-mail] <mailto:[e-mail]>,
> [e-mail] <mailto:[e-mail]>
> Pages: 84
> Updates/Obsoletes/SeeAlso: None
> 
> 
> I-D Tag: draft-ietf-taps-interface-26.txt
> 
> 
> URL: https://www.rfc-editor.org/info/rfc9622 <https://www.rfc-editor.org/info/rfc9622>
> 
> 
> DOI: 10.17487/RFC9622
> 
> 
> 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.
> 
> 
> 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 <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://www.ietf.org/mailman/listinfo/ietf-announce>
> https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>
> 
> 
> For searching the RFC series, see https://www.rfc-editor.org/search <https://www.rfc-editor.org/search>
> For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk <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 [e-mail] <mailto:[e-mail]>. Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
> 
> 
> 
> 
> The RFC Editor Team
> 
> 
> 
> 
> _______________________________________________
> Taps mailing list -- [e-mail] <mailto:[e-mail]>
> To unsubscribe send an email to [e-mail] <mailto:[e-mail]>
> 
> 
> 
> _______________________________________________
> Taps mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]