[quicwg/base-drafts] Recouple QUIC version and ALPN (#3117)

Mike Bishop <notifications@github.com> Thu, 17 October 2019 22:09 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 51FC712082C for <quic-issues@ietfa.amsl.com>; Thu, 17 Oct 2019 15:09:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 cDneILoD19uc for <quic-issues@ietfa.amsl.com>; Thu, 17 Oct 2019 15:09:56 -0700 (PDT)
Received: from out-20.smtp.github.com (out-20.smtp.github.com [192.30.252.203]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2745C120046 for <quic-issues@ietf.org>; Thu, 17 Oct 2019 15:09:56 -0700 (PDT)
Received: from github-lowworker-9bcb4a1.ac4-iad.github.net (github-lowworker-9bcb4a1.ac4-iad.github.net [10.52.25.84]) by smtp.github.com (Postfix) with ESMTP id 3BFCC8C11A1 for <quic-issues@ietf.org>; Thu, 17 Oct 2019 15:09:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1571350195; bh=RQBJR/OhCou0WM2nHR/PLjU3qf2ZBKLR573BuOtkU6E=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=0qPSGw/cKcIyIeKnBNu5golUvraFIZK0JRl5fCYj+DF/M9VzlSJyooY6u0XckJ3fV PMAXtS1ev9ZqdOzONFrVaTCWd7UIdl4gAEuj+vka1xCA/SszSSf+rLQrzpjIzQvqYh 8uwbXbV3AzwR63J/tkqS1waKTtwRCyy5F3GxdJbM=
Date: Thu, 17 Oct 2019 15:09:55 -0700
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYKQYG7GIFC56KI7F53WYTUHEVBNHHB4UWXOE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3117@github.com>
Subject: [quicwg/base-drafts] Recouple QUIC version and ALPN (#3117)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5da8e6b32be94_73893f9f17acd960238617"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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/cwRm5T1yOh91ep7qgzYXW31tzlk>
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: Thu, 17 Oct 2019 22:09:59 -0000

We've removed the text saying that application protocols can constrain which QUIC versions they can run over.  We need to discuss where the correlation between ALPN tokens and version numbers gets considered.  Some proposals discussed in Cupertino:

- **ALPN tokens imply one specific QUIC version.**  This leads to a possible error case, where an ALPN token is offered/accepted over another QUIC version.
- **Application protocols can restrict which QUIC versions they run over.**  This implies that the QUIC version being spoken must be considered when selecting an ALPN token.

-- 
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/3117