Re: [quicwg/base-drafts] When to send the SETTINGS frame (#2945)

Martin Thomson <notifications@github.com> Thu, 08 August 2019 02:51 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 DF6BA120091 for <quic-issues@ietfa.amsl.com>; Wed, 7 Aug 2019 19:51:13 -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 tqh4lbUTN75a for <quic-issues@ietfa.amsl.com>; Wed, 7 Aug 2019 19:51:12 -0700 (PDT)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0DFE120033 for <quic-issues@ietf.org>; Wed, 7 Aug 2019 19:51:11 -0700 (PDT)
Date: Wed, 07 Aug 2019 19:51:10 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1565232670; bh=e3JWvr8i1iEMz38BYPCkV9u1p00QhfQqSsqsXs2A1SM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=w8YYm12abIZ/bUJKrGDe9PPxrykuE1KF/G5YtrwpxtQ5na74sBcgi0g4kBUk8cV5H nyp8Z3igde/THbFKEV5T9EtyUnFNF92DbcV7m3kCgj6DwwM3yfV6ZC3xgVrtjd4/ha 0dudR1vtd24xgwJrEk1JGBURA9wpU0kghy4A9XOg=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZ4IJIQWTDJNT2DKU53LDAJ5EVBNHHBYVUFKY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2945/519342219@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2945@github.com>
References: <quicwg/base-drafts/issues/2945@github.com>
Subject: Re: [quicwg/base-drafts] When to send the SETTINGS frame (#2945)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d4b8e1edd5e8_b3f3f96ab8cd968784575"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/JxvUSZvfwbt2sB2ZvxPC6X4k8w0>
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, 08 Aug 2019 02:51:14 -0000

I think that's overstating the complexities.

If you don't do this, you get vanilla h3.  That's the fallback position.  It's almost like you are arguing for that, because most of these relate directly to that point.

If you do bind SETTINGS to tickets, you get to use nice h3 features like QPACK in 0-RTT and after resumption.  The question we're grappling with is not whether to have the feature (I hope; if we are please open an issue so we can have that discussion), but more how to most cleanly implement that coupling.

Putting SETTINGS in the transport parameters doesn't fix the problem, it just moves it around.  The asymmetry it adds doesn't do anything to remove any asymmetries elsewhere.

-- 
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/2945#issuecomment-519342219