IETF Logo Mail Archive

Re: H3 ALPN?

Martin Duke <martin.h.duke@gmail.com> Tue, 27 April 2021 23:03 UTC

Return-Path: <martin.h.duke@gmail.com>
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 6569A3A246C for <quic@ietfa.amsl.com>; Tue, 27 Apr 2021 16:03:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b7acUbcqlYns for <quic@ietfa.amsl.com>; Tue, 27 Apr 2021 16:03:51 -0700 (PDT)
Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE9E43A246A for <quic@ietf.org>; Tue, 27 Apr 2021 16:03:50 -0700 (PDT)
Received: by mail-io1-xd2d.google.com with SMTP id q25so17796229iog.5 for <quic@ietf.org>; Tue, 27 Apr 2021 16:03:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=RAPUrDSLHumqUL46k57TEaCX20dnDjRNmzkxNzqFUcg=; b=ajOxBKakSILEjUFNQuw9oHHVYJ8mFM82Rl5+9AyyFiTEZ3naJ4LCqcapkxvQXS2OKZ Mx4y3DaIWBRGG8FORhqKM1PmIluNBOh96jJqih3nsyk8O4PnBEcjWOL5rEdzM68lnU88 8DvGjruWoCfMmADjO0jcEjhivhb1qy/6KZrhJQxe4QWLQMbc6cZ8AugRH4aKUdGd8I3W uGOop27csQaKcw6nDl98rwzJWtb9HppgWV6bb68pftiwo1ICH8nuf4OKDceBnvSGD9IK U54MhPKyw1bUH4Pr4aBaht/My1CqZT+7xtgSNXSLIwetLfwZOPZFJ8k8ivg2DWoA+Qm4 DhTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=RAPUrDSLHumqUL46k57TEaCX20dnDjRNmzkxNzqFUcg=; b=HNLp8l6jBLFOxe87wsb5z+Q7WgfXZGhHzhfzslpn9AQJRkF68KAdD83rvl2MubaOTx zXnFmYJscLW0O8nHmC1/yEb1IK18SHcDV83TX6UkZnOYQXEaHJ9dGzOCIBaoAfAWS5pO +00JSKpdI7UzCtc8pqNVfjh6C1yHsGhEdRRmIZW8FOLSWdIBTK01CPhXUzBDGmN7tvPn yx10DLBQHYF6Hm3aUTH5B85Xth+w9f/iR9SWlwHaXIUOOYvzhaLmCxsH0+INHagvu2PQ flkzgS/Nu0HqVLhK/i9DyzXTflIsHr8VPphh59ROUDMKt5l7pXxLDRKUWsV15oCYwmzB aOvQ==
X-Gm-Message-State: AOAM531VGCaHTASvfWH3JBjGYQgDx0/F4iGYbo2KNr848+fD/OqQUWe7 w5aS6iYqwmzj/GAlzK7UHvxAOBR+tKRoXzuu+EL2d75bkGc=
X-Google-Smtp-Source: ABdhPJxkjxFBDUPJLAIhim6wwRSclmOHgB4QbpLUWY3t1wb/VqsuLaThz3D1k1SGM6ifoCuxmGs5eBBRcxJA/20KVf4=
X-Received: by 2002:a6b:7b45:: with SMTP id m5mr21797343iop.97.1619564629480; Tue, 27 Apr 2021 16:03:49 -0700 (PDT)
MIME-Version: 1.0
References: <CAM4esxRFzsuhCfXeeuEp2Yyd396b2cLKhK=erxaRm-MC3CUo6A@mail.gmail.com> <CAM4esxRuPdhC_Ur+RA5C6QZFaof0ywsdmNtkr3HzPAmyw4Ov0w@mail.gmail.com>
In-Reply-To: <CAM4esxRuPdhC_Ur+RA5C6QZFaof0ywsdmNtkr3HzPAmyw4Ov0w@mail.gmail.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Tue, 27 Apr 2021 16:03:39 -0700
Message-ID: <CAM4esxS4ZwAGEnTUgKgLzcOUKwzrWOqt3+vdLkakLUVfFEjbjg@mail.gmail.com>
Subject: Re: H3 ALPN?
To: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006e585505c0fc4642"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Dkk0Ey-w648xe6ql-Idq1GV6X_0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 27 Apr 2021 23:03:52 -0000

QUIC, sorry the confusion. The original message in this thread included
HTTPbis, and you should reply to that one to keep everyone in the loop.

On Tue, Apr 27, 2021 at 3:59 PM Martin Duke <martin.h.duke@gmail.com> wrote:

> Damn it, wrong http
>
> On Tue, Apr 27, 2021 at 3:40 PM Martin Duke <martin.h.duke@gmail.com>
> wrote:
>
>> In the quicdev slack channel today, we realized that we had a disconnect
>> on what ALPN to use in the interval between the QUIC RFCs publishing and
>> the HTTP/3 RFCs being ready (due to a MISREF with http-semantics, etc).
>>
>> It's lost in the slack archives now, but I *think* we had concluded that
>> once the QUIC RFCs ship the endpoints should use 0x00000001/h3, not h3-29
>> or h3-32, because the chance of something in http-semantics breaking
>> interoperability was nil. I personally don't really care how we converge,
>> as long as we converge.
>>
>> To summarize the choices, in the ~months between the RFCs, are endpoints
>> doing a QUIC version + ALPN of
>> 1) 0x00000001/h3 or
>> 2) 0x00000001/h3-xx
>>
>> Can we come to an agreement on this point?
>>
>> Martin
>>
>

v2.23.0 | Report a Bug | By Email