IETF Logo Mail Archive

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 19:09 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 B1A8FC14F619 for <taps@ietfa.amsl.com>; Thu, 18 Apr 2024 12:09:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.997
X-Spam-Level:
X-Spam-Status: No, score=-6.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 dDlN-TjtMGjc for <taps@ietfa.amsl.com>; Thu, 18 Apr 2024 12:09:03 -0700 (PDT)
Received: from mail-out01.uio.no (mail-out01.uio.no [IPv6:2001:700:100:10::50]) (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 03CB0C14F60D for <taps@ietf.org>; Thu, 18 Apr 2024 12:09:01 -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-Type:From:Sender:Reply-To:Cc:Content-Transfer-Encoding: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=GkPqYEQ3l1qmMUiQolxNZsPVIu5yUKa1LTIYbWGQ/Uk=; b=sQuszlYaR+JlPJv6a6Z0P21jxK UHGnSXXTBF9tY6lwNuEbCbimkKnFcel9OqqlrQGvybbqjAsOhh1thjb/hpZqBpz4TLElYhroinLV4 IdZDB5k10pRFPkmUOc4LnF2c6JcbEoYyZ7z1vHtg8dxNPPQlVQS5udwBOo24zghZrRCxLvS0PTBOH 9N0XL1r9aXUOqrXQcTzBxxGJNmYxuE2BcVfHe9FOWh9ynebESjYUgiJm+IEgIz3oTYFYljINSZmt0 YUYuygC1H6T2pSz/Q6nmNezqYccvQwc6zu9Sbdkx0ogDlHJ3VUkKf/ohtsSVeIoHQPHs3wWGtWezX 4HaPRARQ==;
Received: from mail-mx03.uio.no ([129.240.10.15]) by mail-out01.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 1rxX7y-00H09U-0E for taps@ietf.org; Thu, 18 Apr 2024 21:08:58 +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 1rxX7r-000Eqc-2o for taps@ietf.org; Thu, 18 Apr 2024 21:08:58 +0200
From: Michael Welzl <michawe@ifi.uio.no>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D25FA68C-A40F-4248-B759-01DA3437DC56"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
Date: Thu, 18 Apr 2024 12:08:39 -0700
References: <171346498521.35849.15360222205963883010@ietfa.amsl.com> <3104A6EB-1E84-4DB2-87CD-892B80F0D561@ifi.uio.no>
To: taps WG <taps@ietf.org>
In-Reply-To: <3104A6EB-1E84-4DB2-87CD-892B80F0D561@ifi.uio.no>
Message-Id: <827B3901-7874-48FE-8B77-747F20CF5FC0@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.110, HTML_MESSAGE=0.001, UIO_MAIL_IS_INTERNAL=-5)
X-UiO-Scanned: 8FDEE09E13455853A7A144EBA9F63B70A6FB0538
X-UiOonly: C6BCC9DDE2450CE42E7DC80DA94A8A41EFE16012
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/Ld7mXZRwftrUsmxfML9fkhJaL2g>
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 19:09:07 -0000

For some fun - this was published in May 2004, so almost exactly 20 years ago:

https://folk.universitetetioslo.no/michawe/research/publications/ngnm04.pdf
ngnm04
PDF Document · 70 KB

Surely there’s a fair amount of nonsense in there, but… section 4 isn’t too far from what we made, right?  :-)

Cheers,
Michael



> On Apr 18, 2024, at 11:51 AM, Michael Welzl <michawe@ifi.uio.no> wrote:
> 
> 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 mailing list
> Taps@ietf.org
> https://www.ietf.org/mailman/listinfo/taps

v2.23.0 | Report a Bug | By Email