[Taps] Re: RFC 9622 on An Abstract Application Programming Interface (API) for Transport Services
"Philipp S. Tiesel" <phils@in-panik.de> Fri, 31 January 2025 16:27 UTC
Return-Path: <phils@in-panik.de>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3801C14F6A5 for <taps@ietfa.amsl.com>; Fri, 31 Jan 2025 08:27:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UeRx8goOCLAI for <taps@ietfa.amsl.com>; Fri, 31 Jan 2025 08:26:58 -0800 (PST)
Received: from einhorn-mail-out.in-berlin.de (einhorn.in-berlin.de [192.109.42.8]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D038C14F686 for <taps@ietf.org>; Fri, 31 Jan 2025 08:26:57 -0800 (PST)
X-Envelope-From: phils@in-panik.de
Received: from x-berg.in-berlin.de ([IPv6:2a0a:4580:1018:0:5054:ff:feb2:aa6a]) by einhorn.in-berlin.de with ESMTPS id 50VGQp5r1799341 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Fri, 31 Jan 2025 17:26:51 +0100
Received: from [2a0a:4580:1018:451:9de9:de4d:c6fe:4553] (helo=smtpclient.apple) by x-berg.in-berlin.de with esmtpsa (TLS1.2) tls TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <phils@in-panik.de>) id 1tdtr1-00026J-Gm; Fri, 31 Jan 2025 17:26:51 +0100
From: "Philipp S. Tiesel" <phils@in-panik.de>
Message-Id: <45151F75-9AF6-4D44-9B46-42F3FDF3622F@in-panik.de>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E0A91A5F-E048-406E-86C2-6D69461990A3"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.300.87.4.3\))
Date: Fri, 31 Jan 2025 17:26:41 +0100
In-Reply-To: <6FA11D99-93AB-4286-874D-CBA9848658B4@apple.com>
To: taps@ietf.org
References: <FDBAC46E-7AC7-42EF-B462-EFA0969001D7@ifi.uio.no> <6FA11D99-93AB-4286-874D-CBA9848658B4@apple.com>
X-Mailer: Apple Mail (2.3826.300.87.4.3)
Message-ID-Hash: CVNZCYI4BRPPD7MAKXFHBH4Q442J4D3T
X-Message-ID-Hash: CVNZCYI4BRPPD7MAKXFHBH4Q442J4D3T
X-MailFrom: phils@in-panik.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-taps.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Michael Welzl <michawe@ifi.uio.no>, Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Taps] Re: RFC 9622 on An Abstract Application Programming Interface (API) for Transport Services
List-Id: "IETF Transport Services (TAPS) Working Group" <taps.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/4gDDaVs1nQXpGviboor07u_Qb4o>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Owner: <mailto:taps-owner@ietf.org>
List-Post: <mailto:taps@ietf.org>
List-Subscribe: <mailto:taps-join@ietf.org>
List-Unsubscribe: <mailto:taps-leave@ietf.org>
A great milestone and glad we finally got it published! Thanks to everyone involved – hope see you all in Madrid! AVE! Philipp > On 23. Jan 2025, at 15:19, Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org> wrote: > > How great to see these published! Thanks to all who worked on these and helped review. > > Tommy > >> On Jan 23, 2025, at 4:58 AM, Michael Welzl <michawe@ifi.uio.no> wrote: >> >> Hipp hipp !! >> :-) >> >> >>> On 23 Jan 2025, at 13:52, Mirja Kuehlewind <mirja.kuehlewind=40ericsson.com@dmarc.ietf.org> wrote: >>> >>> Yeah!!! Thanks everybody! >>> >>> >>> >>> On 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: >>> >>> >>> 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: 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 >>> >>> >>> 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 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. >>> >>> >>> >>> >>> The RFC Editor Team >>> >>> >>> >>> >>> _______________________________________________ >>> 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> >>> >>> >>> >>> _______________________________________________ >>> Taps mailing list -- taps@ietf.org >>> To unsubscribe send an email to taps-leave@ietf.org >> >> _______________________________________________ >> Taps mailing list -- taps@ietf.org >> To unsubscribe send an email to taps-leave@ietf.org > > _______________________________________________ > Taps mailing list -- taps@ietf.org > To unsubscribe send an email to taps-leave@ietf.org AVE! Philipp S. Tiesel / phils… -- {phils}--->---(phils@in-panik.de)--->---(http://phils.in-panik.de)----, wenn w eine aube ist dn man au dran dre en | o Schr an muss hc h (Kurt Schwitters) | :wq! <----(phone: +49-179-6737439)---<---(jabber: phils@in-panik.de)----'
- [Taps] RFC 9622 on An Abstract Application Progra… rfc-editor
- [Taps] Re: RFC 9622 on An Abstract Application Pr… Mirja Kuehlewind
- [Taps] Re: RFC 9622 on An Abstract Application Pr… Michael Welzl
- [Taps] Re: RFC 9622 on An Abstract Application Pr… Tommy Pauly
- [Taps] Re: RFC 9622 on An Abstract Application Pr… Philipp S. Tiesel
- [Taps] Re: RFC 9622 on An Abstract Application Pr… jon.crowcroft
- [Taps] Re: RFC 9622 on An Abstract Application Pr… Devon H. O'Dell
- [Taps] Re: RFC 9622 on An Abstract Application Pr… Aaron Falk