[Taps] Transport protocol racing in Network Framework

Michael Welzl <michawe@ifi.uio.no> Fri, 10 June 2022 06:55 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 8A643C159492 for <taps@ietfa.amsl.com>; Thu, 9 Jun 2022 23:55:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham 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 dZeicE7ep_pD for <taps@ietfa.amsl.com>; Thu, 9 Jun 2022 23:55:29 -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 72390C1527AF for <taps@ietf.org>; Thu, 9 Jun 2022 23:55:28 -0700 (PDT)
Received: from mail-mx11.uio.no ([129.240.10.83]) by mail-out02.uio.no with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <michawe@ifi.uio.no>) id 1nzYYG-00GNqO-66 for taps@ietf.org; Fri, 10 Jun 2022 08:55:24 +0200
Received: from collaborix.ifi.uio.no ([129.240.69.78] helo=smtpclient.apple) by mail-mx11.uio.no with esmtps (TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.94.2) (envelope-from <michawe@ifi.uio.no>) id 1nzYYF-000Cov-1Z for taps@ietf.org; Fri, 10 Jun 2022 08:55:24 +0200
From: Michael Welzl <michawe@ifi.uio.no>
Content-Type: multipart/alternative; boundary="Apple-Mail=_1958FCBE-33DF-4047-8DE9-D27982EB9A05"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\))
Message-Id: <AE6C4EE9-27BE-4880-9211-65B3D810CA40@ifi.uio.no>
Date: Fri, 10 Jun 2022 08:55:22 +0200
To: taps WG <taps@ietf.org>
X-Mailer: Apple Mail (2.3696.80.82.1.1)
X-UiO-SPF-Received: Received-SPF: neutral (mail-mx11.uio.no: 129.240.69.78 is neither permitted nor denied by domain of ifi.uio.no) client-ip=129.240.69.78; envelope-from=michawe@ifi.uio.no; helo=smtpclient.apple;
X-UiO-Spam-info: not spam, SpamAssassin (score=-4.4, required=5.0, autolearn=disabled, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.652, T_SCC_BODY_TEXT_LINE=-0.01, UIO_MAIL_IS_INTERNAL=-5)
X-UiO-Scanned: BD4F0DD6F86F35AA67AF0E36C35FCF97ADFCE140
X-UiOonly: 97C3D9871C20D361DA1A4B1C44EBE4C8B3C66E62
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/BASzfFjZuMKYpmXzDQ-p4gTBApw>
Subject: [Taps] Transport protocol racing in Network Framework
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: Fri, 10 Jun 2022 06:55:31 -0000

Hi everyone,

My work day is just beginning, and already, my morning has really been brightened up by this (somewhat implicit) announcement of transport protocol racing in Network Framework!
https://developer.apple.com/videos/play/wwdc2022/10078/ <https://developer.apple.com/videos/play/wwdc2022/10078/>

From the transcript: "You can reduce your app's latency significantly by adopting modern protocols such as IPv6, TLS 1.3 and HTTP/3. And all you need to do is use URLSession and Network.framework APIs in your app and these protocols will be used automatically once they are enabled on your server.”

Very cool !!!

Now, of course, every year I anxiously await the WWDC presentation that says “and this is called Transport Services, a standard from the IETF that we recommend everyone to follow” … but I suppose that for this, I must first anxiously wait for us to finish these documents!

We should run, not walk, through this finish line. I can already see it!

Cheers,
Michael