Re: Documenting the "QUIC API"
Michael Welzl <michawe@ifi.uio.no> Wed, 26 March 2025 07:38 UTC
Return-Path: <michawe@ifi.uio.no>
X-Original-To: quic@mail2.ietf.org
Delivered-To: quic@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 64E991279138; Wed, 26 Mar 2025 00:38:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=ifi.uio.no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hT0HQYjfz49B; Wed, 26 Mar 2025 00:38:52 -0700 (PDT)
Received: from mail-out04.uio.no (mail-out04.uio.no [IPv6:2001:700:100:8210::76]) (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 mail2.ietf.org (Postfix) with ESMTPS id EE7051279131; Wed, 26 Mar 2025 00:38:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ifi.uio.no; s=key2309; h=References:To:Cc:In-Reply-To:Date:Subject:Mime-Version: Content-Type:Message-Id:From:Sender:Reply-To: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=k8wd1RoM87Sn53HE5k6Gb6rJOgX4AQux43XXAfAXBg4=; b=F5C4y+xpLdQ8wXFzmQz3ExMEkc MySs3UBbPMLmNyCIlm308ralgIApX8UUVHFTNKiw6BL5k7bmhDLnXSkJkLaWmYZt1XabfmFj1bb8l AJw+7aRdS9Mzk6qO0R1/KlsuAlk/gS04SPAZz1ESiPS97mEq7B+/VZ5ll0QxiS8d30HV7zvjXDolX ipcyZydEuMy9zFq2xXTQ6tty+v4SFGocm0JLHkU3VQgd9tzjNQi444kOvbMeZM2uOdP2L5QPy7brP zhuDZ4P6zUsTEDXeyzSXOnrUo8FK3WTSkh6BvSn3heTzeuRB3VVdFH7imHStvRIVCtSIamMckijuX eiAC9TWw==;
Received: from mail-mx11.uio.no ([129.240.10.83]) by mail-out04.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 1txLLd-00GPGX-1D; Wed, 26 Mar 2025 08:38:49 +0100
Received: from [129.240.136.194] (helo=smtpclient.apple) by mail-mx11.uio.no with esmtps (TLS1.2:ECDHE-ECDSA-AES256-GCM-SHA384:256) (Exim 4.98) (envelope-from <michawe@ifi.uio.no>) id 1txLLc-000000007or-3Vbe; Wed, 26 Mar 2025 08:38:49 +0100
From: Michael Welzl <michawe@ifi.uio.no>
Message-Id: <F1B358B2-11BB-4137-B49A-BCE13CCBFA60@ifi.uio.no>
Content-Type: multipart/alternative; boundary="Apple-Mail=_279A972E-C612-4BB7-AF14-D2410A560692"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.400.131.1.6\))
Subject: Re: Documenting the "QUIC API"
Date: Wed, 26 Mar 2025 08:38:38 +0100
In-Reply-To: <042C4DD9-441C-4292-BDDC-42A140E25701@fb.com>
To: Alan Frindell <afrind=40meta.com@dmarc.ietf.org>
References: <042C4DD9-441C-4292-BDDC-42A140E25701@fb.com>
X-Mailer: Apple Mail (2.3826.400.131.1.6)
X-UiO-SPF-Received: Received-SPF: neutral (mail-mx11.uio.no: 129.240.136.194 is neither permitted nor denied by domain of ifi.uio.no) client-ip=129.240.136.194; envelope-from=michawe@ifi.uio.no; helo=smtpclient.apple;
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.0, required=5.0, autolearn=disabled, HTML_MESSAGE=0.001,RDNS_NONE=0.001,UIO_MAIL_IS_INTERNAL=-5)
X-UiO-Scanned: 8121440A13932685C6442DD5C7994649F38C638B
Message-ID-Hash: 437YDDWUIL6K2J3LWPNRQQBYHGIQEK2F
X-Message-ID-Hash: 437YDDWUIL6K2J3LWPNRQQBYHGIQEK2F
X-MailFrom: michawe@ifi.uio.no
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-quic.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "quic@ietf.org" <quic@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/_oo-G2QqY_XcdZXEIsDsuLs0igg>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Owner: <mailto:quic-owner@ietf.org>
List-Post: <mailto:quic@ietf.org>
List-Subscribe: <mailto:quic-join@ietf.org>
List-Unsubscribe: <mailto:quic-leave@ietf.org>
…. following up, I would also like to raise awareness of RFC 9622. This doesn't specifically expose QUIC (part of the point! explained in RFC 9621), but QUIC was *very much* a part of the design logic and discussions underlying this API. Cheers, Michael > On 25 Mar 2025, at 22:28, Alan Frindell <afrind=40meta.com@dmarc.ietf.org> wrote: > > During the QUIC session at IETF 122 while discussing QMux (formerly QUIC on Streams), a couple folks at the mic advocated for documenting the “QUIC API”. I wanted to raise awareness that this is something like this is covered today in the WebTransport Overview draft, section 4 “Transport Features”. > > https://www.ietf.org/archive/id/draft-ietf-webtrans-overview-09.html#section-4 > > Thanks > > -Alan
- Documenting the "QUIC API" Alan Frindell
- Re: Documenting the "QUIC API" Michael Welzl
- Re: Documenting the "QUIC API" Lucas Pardue
- Re: Documenting the "QUIC API" Kazuho Oku
- Re: Documenting the "QUIC API" Martin Thomson
- Re: Documenting the "QUIC API" Lucas Pardue
- Re: Documenting the "QUIC API" Lars Eggert
- Re: Documenting the "QUIC API" Ian Swett