[Taps] RFC 9623 on Implementing Interfaces to Transport Services
rfc-editor@rfc-editor.org Wed, 22 January 2025 23:18 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: taps@ietf.org
Delivered-To: taps@ietfa.amsl.com
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (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 16340C1E0161; Wed, 22 Jan 2025 15:18:56 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id 89AE0C000061; Wed, 22 Jan 2025 15:18:55 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20250122231855.89AE0C000061@rfcpa.rfc-editor.org>
Date: Wed, 22 Jan 2025 15:18:55 -0800
Message-ID-Hash: F72XTZO74FXAC3GEACIMDG44GRUNY3CY
X-Message-ID-Hash: F72XTZO74FXAC3GEACIMDG44GRUNY3CY
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
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: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, taps@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Taps] RFC 9623 on Implementing Interfaces to Transport Services
List-Id: "IETF Transport Services (TAPS) Working Group" <taps.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/0bLEHKXLR24sWjI2-Ta6W7fgsws>
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 new Request for Comments is now available in online RFC libraries.
RFC 9623
Title: Implementing Interfaces to Transport Services
Author: A. Brunstrom, Ed.,
T. Pauly, Ed.,
R. Enghardt,
P.S. Tiesel,
M. Welzl
Status: Informational
Stream: IETF
Date: January 2025
Mailbox: anna.brunstrom@kau.se,
tpauly@apple.com,
ietf@tenghardt.net,
philipp@tiesel.net,
michawe@ifi.uio.no
Pages: 46
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-taps-impl-18.txt
URL: https://www.rfc-editor.org/info/rfc9623
DOI: 10.17487/RFC9623
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.
This document is a product of the Transport Services Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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 rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team