Re: Transport parameters for version negotiation and v2
Christian Huitema <huitema@huitema.net> Fri, 18 November 2022 00:27 UTC
Return-Path: <huitema@huitema.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33CF2C1522AC for <quic@ietfa.amsl.com>; Thu, 17 Nov 2022 16:27:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 n16r58TfJHeZ for <quic@ietfa.amsl.com>; Thu, 17 Nov 2022 16:27:38 -0800 (PST)
Received: from mx36-out21.antispamcloud.com (mx36-out21.antispamcloud.com [209.126.121.69]) (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 75FC8C14CF1E for <quic@ietf.org>; Thu, 17 Nov 2022 16:27:38 -0800 (PST)
Received: from xse75.mail2web.com ([66.113.196.75] helo=xse.mail2web.com) by mx259.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1ovpE1-0007Nk-8Y for quic@ietf.org; Fri, 18 Nov 2022 01:27:36 +0100
Received: from xsmtp22.mail2web.com (unknown [10.100.68.61]) by xse.mail2web.com (Postfix) with ESMTPS id 4NCyKL06gWz9h3 for <quic@ietf.org>; Thu, 17 Nov 2022 16:27:18 -0800 (PST)
Received: from [10.5.2.12] (helo=xmail02.myhosting.com) by xsmtp22.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1ovpDx-0002a4-RD for quic@ietf.org; Thu, 17 Nov 2022 16:27:17 -0800
Received: (qmail 8287 invoked from network); 18 Nov 2022 00:27:17 -0000
Received: from unknown (HELO [192.168.1.102]) (Authenticated-user:_huitema@huitema.net@[172.58.43.133]) (envelope-sender <huitema@huitema.net>) by xmail02.myhosting.com (qmail-ldap-1.03) with ESMTPA for <mt@lowentropy.net>; 18 Nov 2022 00:27:17 -0000
Message-ID: <9599180d-4dcc-691b-c63d-e8e7e838db42@huitema.net>
Date: Thu, 17 Nov 2022 16:27:16 -0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2
Subject: Re: Transport parameters for version negotiation and v2
Content-Language: en-US
To: Martin Thomson <mt@lowentropy.net>, quic@ietf.org
References: <85208613-d3b1-4955-a71a-b22ac7ada0a1@betaapp.fastmail.com>
From: Christian Huitema <huitema@huitema.net>
In-Reply-To: <85208613-d3b1-4955-a71a-b22ac7ada0a1@betaapp.fastmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: 66.113.196.75
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.0/24@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT9WLQux0N3HQm8ltz8rnu+BPUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5x6h2yQpzTslcOqazQkKtAFKj/EwzSHE5FGYwwjsNRPCBuy lpd6qMxoaE91u4S/lHDmD6wdmZPcItWbGe10hXJtXL4FsauCVkDjmcYJdU3yWp7KuHNaaKdg7iBE ZefdsNUFWKwa/wzJUjmazeC7ImcaRheSNpO0AJesbSAIiXl91RQ6V51u76v35b1wNe/MvdLK0iWX QXXTLFLETKH72XTe2+J9PgaoF8SQHto3le4zsHTaeQtlKubP6iUTjj6yPARK6buALVaA782LKxg6 vRmng8N1aLhXqdc+jC1RcnVud53D5caUhbVtvqItBqoizkEt9O20UjkwI0v+LOlw05G4BS+iyyNq bT8dUMXMJ4tUCMj6G37ZfAMLceP5aNHPt26RBupu5v1nytoNnc138GfEEIgtEXyXj6S3SDvReMcV 8TXUjLjYWQt1/5xnQymMoPsgr/U0flMcy2Vi/IcBgY4arPaiJ1W6hAyiRC61jekdwIcXNugoOEbH RyFULpSjm7hMIABpqqRGKyDs8xujM3cqBeOl1vvorVlRuGVSovFiMQyCQDqx2wczc50GoPHyJBH/ E/keuBSaIyk0OOaqzEQ7EnFzsC48bTEFY06/YbB87aZA2T1TDpm1DkXX6Es5zXntCB3G1CwpaI3Z 4ESkMWDVEmlGVTLa11kLY1eVj2D9MMF4tnaeNxJyHhD4Yo5thYjZcpPgEJKLbDyaC/LdLvvYyUMu zCQeVtJvUlQoBtl7U/pVB9v9zY0h8asEYmbGGsLRRrpb2yB+9SGl7QVSZMRQBAfqzqen+1iMC8MC WyrL7h0sl4OFxBT1d23OUWLVuGpBtL9ewJnoHKUNLZpf7DfZK/JdWvgd2/FibEdMM0Jnxu/VcARR JJg0CPVGXFYA7xCx7SWZBpdAUArn/St00aGa08t44IPL25P8DLNzMDIRDLdvK/cKOEqlCIPGIfYQ DNLcNVwigJ23suxKKQl6t4RW
X-Report-Abuse-To: spam@quarantine14.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Y8vZ5XX5uXnk5Y6Kk9l2tV2YNHc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Nov 2022 00:27:42 -0000
On 11/17/2022 4:15 PM, Martin Thomson wrote: > How many people have shipped version negotiation and v2 already? > > I assume that implementations are using the codepoints for the transport parameter in the draft (0xFF73DB), but the drafts says this: > >> When this document is approved, it will request permanent allocation of a codepoint in the 0-63 range to replace the provisional codepoint described above. > > IANA are about to make that new allocation, but that might not do good things for interoperability. > > We're not changing the v2 version number and v2 *requires* the use of this transport parameter: https://quicwg.org/quic-v2/draft-ietf-quic-v2.html#section-4-2 > > Consequently, an implementation that uses the current transport parameter codepoint will not interoperate successfully with an implementation that uses any new transport parameter codepoint. > > So, we either allocate a new codepoint for both, or we keep the existing ones. Which do people prefer? > > Or, am I wrong about this? The way I read it, QUIC-V2 makes a reference to QUIC-VN, which is documented in the reference section as pointing to draft-ietf-quic-version-negotiation-13. But I fully expect that the next QUIC-V2 draft will refer to the updated version of QUIC-VN, and thus to the final transport parameter. -- Christian Huitema
- Transport parameters for version negotiation and … Martin Thomson
- Re: Transport parameters for version negotiation … Christian Huitema
- Re: Transport parameters for version negotiation … Martin Duke
- Re: Transport parameters for version negotiation … Frederic Lecaille
- RE: Transport parameters for version negotiation … Nick Banks
- Re: Transport parameters for version negotiation … Martin Duke
- Re: Transport parameters for version negotiation … Martin Thomson
- Re: Transport parameters for version negotiation … David Schinazi
- Re: Transport parameters for version negotiation … Tatsuhiro Tsujikawa