IETF Logo Mail Archive

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

Dmitri Tikhonov <dtikhonov@litespeedtech.com> Thu, 17 October 2019 14:44 UTC

Return-Path: <dtikhonov@litespeedtech.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 2F03B1200B8 for <quic@ietfa.amsl.com>; Thu, 17 Oct 2019 07:44:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=litespeedtech-com.20150623.gappssmtp.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 ElFPbdAlCO82 for <quic@ietfa.amsl.com>; Thu, 17 Oct 2019 07:44:15 -0700 (PDT)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (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 66B101200F9 for <quic@ietf.org>; Thu, 17 Oct 2019 07:44:15 -0700 (PDT)
Received: by mail-qt1-x82b.google.com with SMTP id o12so3963853qtf.3 for <quic@ietf.org>; Thu, 17 Oct 2019 07:44:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=WJmcf8DquE3qtxWZpsr2MVXQ9XHYLAKr+NFd8McuNC0=; b=jNpF3Z93xnDzACfr374Nq8SwI+RcvzVHtviD0Mrcw1ZJ1yFnMyuwwiUmsQalE12FjZ dFM/tZ3Q+rbu8FqGsVLwUHNhyvnEQ6ilm9J82GBrdT5LKUGuJN/0WoI+g1bB7RASbAtw KVLEyQZ4S5TZ9i/giIBCzUKxdDJSeXApTdl23MLjxY0Vsw4COmQatpMK+YOP4QsNWthO wNsmRA7MSvk9oDXskrZAVsNUIPZE9W0Ue0UDgqJXrYkFKpHKXVXhvdSkzela/uv0Z3BS 06KET+jPqTFKbyxODC61sFkZfik0s/ewfjfY1Wj0M0hObeyOLRFS7gI/a+zkifUabASP NVaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=WJmcf8DquE3qtxWZpsr2MVXQ9XHYLAKr+NFd8McuNC0=; b=YAFQE/d4NstSJXgtox/I71qIIxwV4oZxVefeMqIAFP7haNMTe4EaAURARgXO1fjjEb EPA9gD09vAaJUgVb2TAStZEkw2sQ9P0Q3XL6BZxvNQUJozqVAafZ1rfuvadWnH1Przzx 3IO1lZyYRmxA+SZGrVGnLxbQJqJi/bErmxjQGnjJXj2JT7nKNu/Ujr4cpAz+2gusgStw UwieU8cR7OlvxGNlmStdtOofFaLFN7YcCAYfrSez8OHEdLEPqY3PfxU5OphdSD/I8t/y Wud/EeLnE4OgCz+zHbc95Lyxa9AFcbFM2yP1omJPZe3hE17yxEPU+UpqBwxKsvr1dgA+ RhYg==
X-Gm-Message-State: APjAAAURe3qzMfGOTS22XyUKemdIskJqwTcB2fT+b+KO1kvp5KwbloQT n3/ikHdfUgSMfpgI+Ur18ZFSww==
X-Google-Smtp-Source: APXvYqyYU8nCgg/jvUKTfWuzPtYXlnIbJdM3BbJfXGZqt4C6bhLZz9ZDTR7Ul39gmENo+BdSG92dcw==
X-Received: by 2002:ac8:3408:: with SMTP id u8mr4251892qtb.380.1571323454509; Thu, 17 Oct 2019 07:44:14 -0700 (PDT)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id l185sm1465487qkd.20.2019.10.17.07.44.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 Oct 2019 07:44:13 -0700 (PDT)
Date: Thu, 17 Oct 2019 10:44:07 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: David Schinazi <dschinazi.ietf@gmail.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>
Subject: Re: Add application parameters to QUIC handshake and use it for H3 SETTINGS
Message-ID: <20191017144406.GA18835@ubuntu-dmitri>
Mail-Followup-To: David Schinazi <dschinazi.ietf@gmail.com>, 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>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAPDSy+4aFG_JUUQYxhXFUmhShXML58uSp2v+pEW9cy6FPcyuCw@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/R43d80-zkUkorFQMsr-GvZIAkAQ>
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 14:44:17 -0000

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?

  - Dmitri.

v2.23.0 | Report a Bug | By Email