From: Michael Welzl <michawe@ifi.uio.no>
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.10\))
Date: Thu, 23 Jan 2025 13:58:27 +0100
References: <20250122231824.3E8BCC000061@rfcpa.rfc-editor.org>
 <59FE5DB8-53D9-4E27-A79D-8612096EF3BB@ericsson.com>
To: "taps@ietf.org" <taps@ietf.org>
In-Reply-To: <59FE5DB8-53D9-4E27-A79D-8612096EF3BB@ericsson.com>
Message-Id: <FDBAC46E-7AC7-42EF-B462-EFA0969001D7@ifi.uio.no>
Message-ID-Hash: S4QTWREXDYTB6BKECDEBAS5QLTKC2PFS
Precedence: list
Subject: =?utf-8?q?=5BTaps=5D_Re=3A_RFC_9622_on_An_Abstract_Application_Programming_I?=
 =?utf-8?q?nterface_=28API=29_for_Transport_Services?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/taps/N8lUxB0yawlcyJAPgsUGCanxR_g>

Hipp hipp !!
:-)


> On 23 Jan 2025, at 13:52, Mirja Kuehlewind =
<mirja.kuehlewind=3D40ericsson.com@dmarc.ietf.org> wrote:
>=20
> Yeah!!! Thanks everybody!
>=20
>=20
>=20
> =EF=BB=BFOn 23.01.25, 00:22, "rfc-editor@rfc-editor.org =
<mailto:rfc-editor@rfc-editor.org>" <rfc-editor@rfc-editor.org =
<mailto:rfc-editor@rfc-editor.org>> wrote:
>=20
>=20
> A new Request for Comments is now available in online RFC libraries.
>=20
>=20
>=20
>=20
> RFC 9622
>=20
>=20
> Title: An Abstract Application Programming Interface (API)
> for Transport Services
> Author: B. Trammell, Ed.,
> M. Welzl, Ed.,
> R. Enghardt,
> G. Fairhurst,
> M. K=C3=BChlewind,
> C. S. Perkins,
> P.S. Tiesel,
> T. Pauly
> Status: Standards Track
> Stream: IETF
> Date: January 2025
> Mailbox: ietf@trammell.ch <mailto:ietf@trammell.ch>,
> michawe@ifi.uio.no <mailto:michawe@ifi.uio.no>,
> ietf@tenghardt.net <mailto:ietf@tenghardt.net>,
> gorry@erg.abdn.ac.uk <mailto:gorry@erg.abdn.ac.uk>,
> mirja.kuehlewind@ericsson.com <mailto:mirja.kuehlewind@ericsson.com>,
> csp@csperkins.org <mailto:csp@csperkins.org>,
> philipp@tiesel.net <mailto:philipp@tiesel.net>,
> tpauly@apple.com <mailto:tpauly@apple.com>
> Pages: 84
> Updates/Obsoletes/SeeAlso: None
>=20
>=20
> I-D Tag: draft-ietf-taps-interface-26.txt
>=20
>=20
> URL: https://www.rfc-editor.org/info/rfc9622 =
<https://www.rfc-editor.org/info/rfc9622>
>=20
>=20
> DOI: 10.17487/RFC9622
>=20
>=20
> 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.
>=20
>=20
> This document is a product of the Transport Services Working Group of =
the IETF.
>=20
>=20
> This is now a Proposed Standard.
>=20
>=20
> 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.
>=20
>=20
> 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>
>=20
>=20
> 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>
>=20
>=20
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor@rfc-editor.org =
<mailto:rfc-editor@rfc-editor.org>. Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>=20
>=20
>=20
>=20
> The RFC Editor Team
>=20
>=20
>=20
>=20
> _______________________________________________
> Taps mailing list -- taps@ietf.org <mailto:taps@ietf.org>
> To unsubscribe send an email to taps-leave@ietf.org =
<mailto:taps-leave@ietf.org>
>=20
>=20
>=20
> _______________________________________________
> Taps mailing list -- taps@ietf.org
> To unsubscribe send an email to taps-leave@ietf.org