IETF Logo Mail Archive

Re: H3 ALPN?

Martin Duke <martin.h.duke@gmail.com> Tue, 27 April 2021 23:00 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 C16BF3A2446 for <quic@ietfa.amsl.com>; Tue, 27 Apr 2021 16:00:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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_NONE=-0.0001, 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 wjUzqeu69uNM for <quic@ietfa.amsl.com>; Tue, 27 Apr 2021 16:00:04 -0700 (PDT)
Received: from mail-il1-x130.google.com (mail-il1-x130.google.com [IPv6:2607:f8b0:4864:20::130]) (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 EE4593A2443 for <quic@ietf.org>; Tue, 27 Apr 2021 16:00:03 -0700 (PDT)
Received: by mail-il1-x130.google.com with SMTP id l9so8307752ilh.10; Tue, 27 Apr 2021 16:00:03 -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=ie/kHSx4CdCNz4dX3RtIduRJiNJGWYn13VeXs2rQOoU=; b=d7BfUcvyV63swVACAJf0/SCNVn8Kd47WggZu4ZbjrH6Kt1Nmp9vBIcHwa3h6jtBxIJ HnE152ZkJEEeInGeVO7cCjGP9hLL7iRyUI8OoKSVan21cUitF7srImR0LVwxEf2aDVHg 0cXW7lnhImVIbfzX1pRewLALRtTkO4foAjjvRI8+4I9+aqB+WrIL/zd77TJLI1i2Ws+s p7ug6z1j7+QpqfX03EroP1MlwL/b08ST08kErvnV/WyeYSIDphN6MQSaQTNzwNumJcXP E8gJLCSrBrfxnvZ9z4AApuLGXfV66zDt0DgX2Td9wntbaQd4tvcvIqZVtMCen/tUdX1x DscA==
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=ie/kHSx4CdCNz4dX3RtIduRJiNJGWYn13VeXs2rQOoU=; b=P0vGqUvBOonnyJVWQnSvR5EUzNYBNCHMHpJl9Ld4NDEMii4nF3VJbqqazFWg0k8CuL DNzOVhzNYmtS9B9lFQecBa16pMSCuLdFpn1YviV1mTLk5tCg2VEyX8YbTvu0vEYRhuYB rLvBYZDYLpPZh3Zw46TW6MiNa9QkSQKPN/ySLptmF4UNnx4ypI/mE2fp1euEqjgCxS6P nyasyRoieOqZpW9kwdHITgJrh4OwEq7/BZe3Ugtq4dfzxcQ6udPfGlcSHLm3NYMhR/xg ipQZaErF05C1VKSnofxXM+PYRm3GLHc5MIwimXTa1PZzKxJSRTsXHNTQM1vBjjLbyhKu U3eQ==
X-Gm-Message-State: AOAM531nA0Ap0I9BjViclO9JHfMZNKU1uS8kBUcaGkgx5RbCnjgGuVVu nm1UEfekYi4M7tRqJFnDoSBN2RujguAZDX90EHYph82ipW0=
X-Google-Smtp-Source: ABdhPJxwpB1fH7Naieim8N8kak8/WcoInpdBlA39dbcQQXmvoJLTE3YjngcS0zI375ou2Fwo9W1yMmRWSHMBdd6rQiU=
X-Received: by 2002:a05:6e02:1c42:: with SMTP id d2mr19196362ilg.287.1619564401738; Tue, 27 Apr 2021 16:00:01 -0700 (PDT)
MIME-Version: 1.0
References: <CAM4esxRFzsuhCfXeeuEp2Yyd396b2cLKhK=erxaRm-MC3CUo6A@mail.gmail.com>
In-Reply-To: <CAM4esxRFzsuhCfXeeuEp2Yyd396b2cLKhK=erxaRm-MC3CUo6A@mail.gmail.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Tue, 27 Apr 2021 15:59:51 -0700
Message-ID: <CAM4esxRuPdhC_Ur+RA5C6QZFaof0ywsdmNtkr3HzPAmyw4Ov0w@mail.gmail.com>
Subject: Re: H3 ALPN?
To: IETF QUIC WG <quic@ietf.org>, httpbis@ietf.org
Content-Type: multipart/alternative; boundary="000000000000db480305c0fc38e5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/4b_g66c17p7Yf6f26LCOeahXepY>
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:00:07 -0000

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.8.10 | Report a Bug | By Email