Re: Add application parameters to QUIC handshake and use it for H3 SETTINGS

David Schinazi <dschinazi.ietf@gmail.com> Thu, 17 October 2019 15:53 UTC

Return-Path: <dschinazi.ietf@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 82B3012099A for <quic@ietfa.amsl.com>; Thu, 17 Oct 2019 08:53:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-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, URIBL_BLOCKED=0.001] autolearn=unavailable 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 LQxxKBNmLqyy for <quic@ietfa.amsl.com>; Thu, 17 Oct 2019 08:53:32 -0700 (PDT)
Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (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 3CFB6120980 for <quic@ietf.org>; Thu, 17 Oct 2019 08:53:32 -0700 (PDT)
Received: by mail-lf1-x12f.google.com with SMTP id v8so1720406lfa.12 for <quic@ietf.org>; Thu, 17 Oct 2019 08:53:32 -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 :cc; bh=UG1VsHqG2u9ERaaDIQ/00wKbFfrQO5I5zR2bcrHTu58=; b=p5HJUAXkWx+cUwqRmJtxQi+8pXz7azstFJagnqjNRfC/LbpuSzIZzSR709h+QU6G8L t3rZuGT+rYPCpO1suP4TVvW+6SBvb9RjFEihRcZHocVto/xApWEYfqCfeDFmLCNXqJwv euIpq9XxbLwjrIRcpIij9Cf/GLP5lrHWuRb1oer9az4JQA9oKhWQmoGbSiBBEyacfCTY ITU/D+MXSxcRNRzL377RxeHnICBW9ZHfzhiCbKBU1epeWQOVydaD1x7wdb/acoxOW4ce wIcpM5VSTtQqy4qZgAdIXucpEI4+hB+A6uvjiQfb6cmBkJXtMZMmRVOIcjarcQCxAPIO y0JQ==
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:cc; bh=UG1VsHqG2u9ERaaDIQ/00wKbFfrQO5I5zR2bcrHTu58=; b=YRiT5N/3rLtIX/j1J/vSbUBwqlb0ohpZSeIEFe4CejlSGgte4IF9upin57H5WtQxdR RJ/WEfMCWjgxuBA6tSt5gE8Fm+rs8JfOF8JURhsCLmySaq7Y0jrtdjusP3itfkl7mMEJ nliTdDAEc+O+IZ17fTdDfS7Pt06p4gyMZT5636A77mPzQcG3eANsF/1lpivnWMrr3/Tu UQgHkoW7E5YcuyvWrEQ+gTEslfCwPsr5nCmgb1A14tuujhtKqVPzmUEsHfNulKMwCfg8 ldeYATJcGobyW1vBQ3nQiSv5RtoPPpANKE17BRB+QDsExaYz2LwUAoJ0f0YnYMa5GntI CAvA==
X-Gm-Message-State: APjAAAUNJqJAfeCZvnjsp5ZEO74Z7DP2yAYa/FjI6oHYgTSOn8t/WJUy JJaPcV1kLmWundXpuMulrxbJ6zJcbAa5fMmE8LQ=
X-Google-Smtp-Source: APXvYqw7/G65bb/vniWIjkjRhVWYb4gSJY5DEUpWiW4pxZwfrDwsVwf4aYZU4L/K+qE8Y3w0vlh8cMsqmp5m8D5zrlI=
X-Received: by 2002:ac2:53a7:: with SMTP id j7mr2898753lfh.10.1571327610475; Thu, 17 Oct 2019 08:53:30 -0700 (PDT)
MIME-Version: 1.0
References: <CACdeXiLEnvmqmxSgXbvAwEo0rgm-F59RL2sk0Ugu6PNuiDkfsw@mail.gmail.com> <CA+9kkMCOx-3cBq1_X4acHPjKtWUYSFLiLsu8HuEFOmDKxv7aww@mail.gmail.com> <CABcZeBNL0AYJF6J5Dn8LYYfK+Gv39_LPknSNtrMgRcp_tgayZQ@mail.gmail.com> <CACdeXiJFSo0-oK60ONnVfXFN66nO5f292m65znD9MW4DKRJJfg@mail.gmail.com> <CAPDSy+49Kk1GUS+WoyNaKTJ2AnyvhYmiAMXQk-Oi-Xczgenquw@mail.gmail.com> <CANatvzwb_Yp9dhpQv+Adv6JGk-wFYrc4XnJ0H7waNFzqb02wDg@mail.gmail.com> <CAPDSy+4aFG_JUUQYxhXFUmhShXML58uSp2v+pEW9cy6FPcyuCw@mail.gmail.com> <20191017144406.GA18835@ubuntu-dmitri>
In-Reply-To: <20191017144406.GA18835@ubuntu-dmitri>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Thu, 17 Oct 2019 08:53:12 -0700
Message-ID: <CAPDSy+7z9akKiPm03PyR7PjtrmUO=mWoFA4y6ft2ERkmEo=g9A@mail.gmail.com>
Subject: Re: Add application parameters to QUIC handshake and use it for H3 SETTINGS
To: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
Cc: Kazuho Oku <kazuhooku@gmail.com>, Eric Rescorla <ekr@rtfm.com>, Nick Harper <nharper=40google.com@dmarc.ietf.org>, Ted Hardie <ted.ietf@gmail.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000c5b1105951d38e5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/FgeqB4KI38JiUH3fpK_wyAWM_mY>
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: Thu, 17 Oct 2019 15:53:35 -0000

On Thu, Oct 17, 2019 at 7:44 AM Dmitri Tikhonov <dtikhonov@litespeedtech.com>
wrote:

> On Wed, Oct 02, 2019 at 02:20:52PM -0700, David Schinazi wrote:
> > If we decide that the first requests need to operate without knowledge
> > of settings, we're effectively crippling the main extension mechanism
> > we have in HTTP/3.  I'm not comfortable saying that for the entire
> > lifetime of QUICv1 we cannot have extensions that impact the first
> > requests. That feels like painting ourselves into a corner.
>
> Is there prior art?  That is, are there protocols that allow extension
> settings to be specified in a first request/packet?
>

TLS has client hello extensions. TCP has options that can travel with the
SYN.