Re: [Taps] Protocol Action: 'An Abstract Application Layer Interface to Transport Services' to Proposed Standard (draft-ietf-taps-interface-26.txt)
Michael Welzl <michawe@ifi.uio.no> Thu, 18 April 2024 18:52 UTC
Return-Path: <michawe@ifi.uio.no>
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 B0B17C14F616 for <taps@ietfa.amsl.com>; Thu, 18 Apr 2024 11:52:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ifi.uio.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 Xm8X4qW-egoC for <taps@ietfa.amsl.com>; Thu, 18 Apr 2024 11:52:16 -0700 (PDT)
Received: from mail-out02.uio.no (mail-out02.uio.no [IPv6:2001:700:100:8210::71]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D84EAC14F61D for <taps@ietf.org>; Thu, 18 Apr 2024 11:52:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ifi.uio.no; s=key2309; h=Message-Id:In-Reply-To:To:References:Date:Subject:Mime-Version: Content-Transfer-Encoding:Content-Type:From:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=kZ+lM63fFkdEMeIq5mcWIKBUFf1tDMw/IEcvTMkQiR4=; b=QqCAiMoFlVfqw+E17ZwkSqFZux utVVsxJj6WjVQ39SYtXfXNxff10k8dLliU3AfCZUTsvPhqB6WxpfaeIJDliFSFp1qsxyLf49CBEef rj2P0SFqCYOYLMFxp+bFUgI4goZv22g0RV5kRJcwwGv5k6MmdK0N4mg2t2Pnb7qVfO7Jo/uljOmXg e+0n2CLQBhju8QpoIevjOnDpznBksjicby7fF796np/ElyvkHJq4XEp4oiiAUawJvoC4O/BYxFExF uKk9BWJzKvm63y80/MLgw8XoaFavLF2HI5/hixeKSr1/I5sHU+VocnubW6uFcydngYqg/m5rf7Hqw FFA4k+9A==;
Received: from mail-mx03.uio.no ([129.240.10.15]) by mail-out02.uio.no with esmtps (TLS1.2) tls TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (Exim 4.96.2) (envelope-from <michawe@ifi.uio.no>) id 1rxWrj-00Enc1-2i for taps@ietf.org; Thu, 18 Apr 2024 20:52:11 +0200
Received: from [4.28.11.157] (helo=smtpclient.apple) by mail-mx03.uio.no with esmtpsa (TLS1.2:ECDHE-ECDSA-AES256-GCM-SHA384:256) user michawe (Exim 4.96.2) (envelope-from <michawe@ifi.uio.no>) id 1rxWrj-000D95-0W for taps@ietf.org; Thu, 18 Apr 2024 20:52:11 +0200
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 \(3774.500.171.1.1\))
Date: Thu, 18 Apr 2024 11:51:58 -0700
References: <171346498521.35849.15360222205963883010@ietfa.amsl.com>
To: taps WG <taps@ietf.org>
In-Reply-To: <171346498521.35849.15360222205963883010@ietfa.amsl.com>
Message-Id: <3104A6EB-1E84-4DB2-87CD-892B80F0D561@ifi.uio.no>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
X-UiO-SPF-Received: Received-SPF: neutral (mail-mx03.uio.no: 4.28.11.157 is neither permitted nor denied by domain of ifi.uio.no) client-ip=4.28.11.157; envelope-from=michawe@ifi.uio.no; helo=smtpclient.apple;
X-UiO-Spam-info: not spam, SpamAssassin (score=-4.9, required=5.0, autolearn=disabled, AWL=0.128, UIO_MAIL_IS_INTERNAL=-5)
X-UiO-Scanned: 4F947D68BBDD901A834E0B73DE0EF89922AFC8D7
X-UiOonly: 7C3F9D4A71EEB6BB8F228D2FDC84FDB92867058D
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/bhAfnHqXGWgtJqFTXJSZh_6TVuc>
Subject: Re: [Taps] Protocol Action: 'An Abstract Application Layer Interface to Transport Services' to Proposed Standard (draft-ietf-taps-interface-26.txt)
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF Transport Services \(TAPS\) Working Group" <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Apr 2024 18:52:20 -0000
Oh my god. I have a hole in my life now. :-D > On Apr 18, 2024, at 11:29 AM, The IESG <iesg-secretary@ietf.org> wrote: > > The IESG has approved the following document: > - 'An Abstract Application Layer Interface to Transport Services' > (draft-ietf-taps-interface-26.txt) as Proposed Standard > > This document is the product of the Transport Services Working Group. > > The IESG contact persons are Zaheduzzaman Sarker and Francesca Palombini. > > A URL of this Internet-Draft is: > https://datatracker.ietf.org/doc/draft-ietf-taps-interface/ > > > > > Technical Summary > > 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 sockets API as the common interface to the transport > layer, in an environment where endpoints could select from multiple > interfaces and potential transport protocols. > > Working Group Summary > > This document reached broad agreement, with contributions from most active WG > members. > > Document Quality > > This document specifies and abstract API for the Transport Services reference > architecture described in the -arch draft; the proposed API is based on > experience gained in one widely deployed production implementation and two open > implementations deployed for research purposes, as listed in Appendix C of the > -implementation draft. > This draft has benefited from broad TSV area review within the WG itself, and > has had secdir and artart early review. > > Personnel > > The Document Shepherd for this document is Anna Brunstrom. The > Responsible Area Director is Zaheduzzaman Sarker. > > > > _______________________________________________ > Taps mailing list > Taps@ietf.org > https://www.ietf.org/mailman/listinfo/taps
- [Taps] Protocol Action: 'An Abstract Application … The IESG
- Re: [Taps] Protocol Action: 'An Abstract Applicat… Michael Welzl
- Re: [Taps] Protocol Action: 'An Abstract Applicat… Michael Welzl