Re: [quicwg/base-drafts] Server's SETTINGS can be omitted in 0-RTT (#1809)

Mike Bishop <> Fri, 28 September 2018 20:22 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 62747130E68 for <>; Fri, 28 Sep 2018 13:22:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.456
X-Spam-Status: No, score=-8.456 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, 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] 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 D65mziASCv6J for <>; Fri, 28 Sep 2018 13:22:43 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BD2F812F1A2 for <>; Fri, 28 Sep 2018 13:22:43 -0700 (PDT)
Date: Fri, 28 Sep 2018 13:22:42 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1538166162; bh=scpVy/pYd1kHkV6n3UJiEx56miEhNnt4/pkvLhsCyh8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0JrEW9JiLMIqFGlXesNDeDxDheKqzgQoMe/+NH6cFMkNi6VOZ9mJ0XncehgQEuBg4 G8gTN9eLoKdS0IPmkclXn6X6PAgy8ufnG2mXKaSYwUeZeQs5MGA8qlawnFK+GV1VCr O7j3G0ctcxWsTdDZH1QN5BSaruGMJctN8H5nlqW8=
From: Mike Bishop <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/1809/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Server's SETTINGS can be omitted in 0-RTT (#1809)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bae8d92589f9_34793f9b3ced45c41417fb"; 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
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, 28 Sep 2018 20:22:46 -0000

I agree; I don't like the idea of banning SETTINGS, because it means rejecting 0-RTT any time the server's settings are different, not just when they've become more restrictive.  The real question is whether it's worth introducing a mechanism to ensure the SETTINGS frame is present.

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