Re: [quicwg/base-drafts] Add application parameters to QUIC handshake and use it for H3 SETTINGS (#3086)

ianswett <> Fri, 11 October 2019 01:01 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7CEC11200FF for <>; Thu, 10 Oct 2019 18:01:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id fc5G9AxYX31S for <>; Thu, 10 Oct 2019 18:00:59 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 78D9B12004F for <>; Thu, 10 Oct 2019 18:00:59 -0700 (PDT)
Date: Thu, 10 Oct 2019 18:00:58 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1570755658; bh=Nrl+93aaJXUz1YdTJ2pO4+cTqte1zzv3Ob/3n6JKRJE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=yrf4k/Q17OZJBWjavaysmxpVcZ4PzMbdwqE4/IiYkDDjJ57/evhEcXZ8x/OPOiV3J 48dxBVe+06aIR5BNNu+9ArZbMyC9ymJ4lpXq9oIYMuLmj8SNx43F9LIfEieE7RaFqO 3D/lzTRUoRdXgcWnQ3kcrulVas7cSV0pV9jEGgzc=
From: ianswett <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3086/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Add application parameters to QUIC handshake and use it for H3 SETTINGS (#3086)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d9fd44a740d6_45ad3fe2740cd96079241"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 11 Oct 2019 01:01:02 -0000

To me, there are two clear approaches:
 1) Add application negotiation to the handshake
 2) Make the application implement negotiation

Currently QUIC and HTTP/3 use the 2nd approach, and you're suggesting the 1st.

If those are the only two (reasonable) options, then adding application parameters allows HTTP/3 to do 1, while still allowing other applications to do 2, if they choose.  This provides more options for future applications, not fewer in my opinion.

Strictly speaking, I don't think this is necessary for v1, but I think this is something we'll want soon and I believe it is a net reduction in complexity for HTTP/3(please tell me if I'm wrong about that).

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: