IETF Logo Mail Archive

Re: [quicwg/base-drafts] Resume HTTP/2 TLS from QUIC ? (#941)

martinduke <notifications@github.com> Fri, 05 October 2018 22:57 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 D0437130DE2 for <quic-issues@ietfa.amsl.com>; Fri, 5 Oct 2018 15:57:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Level:
X-Spam-Status: No, score=-7.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=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 YF9WNZLXAT9v for <quic-issues@ietfa.amsl.com>; Fri, 5 Oct 2018 15:57:24 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4FC0E129AB8 for <quic-issues@ietf.org>; Fri, 5 Oct 2018 15:57:24 -0700 (PDT)
Date: Fri, 05 Oct 2018 15:57:23 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1538780243; bh=grFa5RmZBJYJkSSzv97Dlf6OPexPR/MitiffQKT3U3E=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=lpODyBbR6s5x83jaF11MY8U45HRBmL3/0ZR9/L8PV150Af15BLix4TnN5Rak1nsE0 xiDW1PVLfd2iZpnVFPQuZ5OIQsCOTxL8kWS7MV8ex5Ggy5siT82fenR3PaV/pRM0mF IgM2D6W/2cLKycXDIFfqJNAC2cRP4wIGnn+BMsz4=
From: martinduke <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab4d9ce8b17da12045fb33112138df7f57cfac688c92cf0000000117cfae5392a169ce105fcf55@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/941/427519947@github.com>
In-Reply-To: <quicwg/base-drafts/issues/941@github.com>
References: <quicwg/base-drafts/issues/941@github.com>
Subject: Re: [quicwg/base-drafts] Resume HTTP/2 TLS from QUIC ? (#941)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bb7ec538c78e_74f53fdb652d45bc20883c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinduke
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/jOb55S8PgvSi1vX3p6kS4PLe6Rw>
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: Fri, 05 Oct 2018 22:57:37 -0000

What would be the impact of changing the hq ALPN value to h2? Whatever we call it, it's basically HTTP/2 for QUIC, and on a QUIC connection there's no ambiguity as to what the client is asking for.

-- 
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/941#issuecomment-427519947

v2.23.0 | Report a Bug | By Email