Re: [quicwg/base-drafts] Asymmetry in the handling of SETTINGS frame (#1846)

Mike Bishop <notifications@github.com> Tue, 09 October 2018 22:50 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 5583F130E0C for <quic-issues@ietfa.amsl.com>; Tue, 9 Oct 2018 15:50:44 -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 K7cBabWQVtK2 for <quic-issues@ietfa.amsl.com>; Tue, 9 Oct 2018 15:50:42 -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 7A4CB130E25 for <quic-issues@ietf.org>; Tue, 9 Oct 2018 15:50:42 -0700 (PDT)
Date: Tue, 09 Oct 2018 15:50:40 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1539125440; bh=Vz81Lr52uUnXhD/R2Hyt9C/ksNtDcu+69+AIvN6iJho=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=LHMGO66FgST9BYIaKVyppl8gBT8MRFh12fff3zFSE2rhAEoFo2hk4YbyPGovgpEd2 BI5CecdBnlm36avrPPSDmQsUzKluBt/drPQYk2iHSJvzgfWkEWRmEUadlQZ9Tl/aJR zHhwq3BFAzOYnGTg2RaTuVzbmMjXiefzHva824HA=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab0d63ce300d4741bb78a10560271b50a5a9d67a7e92cf0000000117d4f2c092a169ce15f10683@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1846/428379797@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1846@github.com>
References: <quicwg/base-drafts/issues/1846@github.com>
Subject: Re: [quicwg/base-drafts] Asymmetry in the handling of SETTINGS frame (#1846)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bbd30c046ab9_49243fad4aed45b8134298"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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/Ov_u3mLCtBUJwaWw0-jaHAcdFFg>
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: Tue, 09 Oct 2018 22:50:44 -0000

I think the mechanism for "negotiation" looks like this:  each side unilaterally declares something (the set of options it supports for a particular extension, say), then each side performs the same calculation and derives the same result (mutually supported values, select most preferred by some measure if a single choice is required).

The implied ACK currently is that neither side is supposed to send until it knows what the other side supports, so if you're seeing bytes on other streams, they know what your settings are.

-- 
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/1846#issuecomment-428379797