[quicwg/base-drafts] Unclear what to do when QUIC Version Hints are missing (#3061)

David Schinazi <notifications@github.com> Mon, 23 September 2019 23:49 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DBFB120098 for <quic-issues@ietfa.amsl.com>; Mon, 23 Sep 2019 16:49:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.281
X-Spam-Level:
X-Spam-Status: No, score=-6.281 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 1KrX_-IUCLUL for <quic-issues@ietfa.amsl.com>; Mon, 23 Sep 2019 16:49:31 -0700 (PDT)
Received: from out-24.smtp.github.com (out-24.smtp.github.com [192.30.252.207]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7F9D120077 for <quic-issues@ietf.org>; Mon, 23 Sep 2019 16:49:30 -0700 (PDT)
Received: from github-lowworker-f62aa54.va3-iad.github.net (github-lowworker-f62aa54.va3-iad.github.net [10.48.17.68]) by smtp.github.com (Postfix) with ESMTP id D707B6A0C91 for <quic-issues@ietf.org>; Mon, 23 Sep 2019 16:49:29 -0700 (PDT)
Date: Mon, 23 Sep 2019 16:49:29 -0700
From: David Schinazi <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2NX5CFIUIIOKYJMO53S2NJTEVBNHHB3JLRAU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3061@github.com>
Subject: [quicwg/base-drafts] Unclear what to do when QUIC Version Hints are missing (#3061)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d895a09c7bbb_26893f81c6ccd968471b3"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: DavidSchinazi
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/MJo_jX_LCyplVUP-KaMKEbm9asE>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Sep 2019 23:49:33 -0000

[draft-quic-http defines QUIC Version Hints](https://tools.ietf.org/html/draft-ietf-quic-http-23#section-3.2.1). This allows the server to indicate which versions of quic-transport it prefers. However, there is no guidance as to what to do in the absence of such hints.

If a client receives `Alt-Svc: h3=":443"` (without any hints), is it expected to start with QUIC version 1, or with the client's preferred QUIC version?

If a client receives `Alt-Svc: h3-23=":443"`, is it expected to start with `0xff000017` (draft-ietf-quic-transport-23)?

We may want to provide guidance in draft-quic-http to ensure everyone's on the same page.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/3061