Re: [quicwg/base-drafts] Changing protocol elements: Is this text strong enough? (#2985)

Mike Bishop <> Thu, 22 August 2019 17:21 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 52056120905 for <>; Thu, 22 Aug 2019 10:21:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Status: No, score=-6.454 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_20=1.546, 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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id wj1payuvTKru for <>; Thu, 22 Aug 2019 10:21:13 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1C599120903 for <>; Thu, 22 Aug 2019 10:21:13 -0700 (PDT)
Date: Thu, 22 Aug 2019 10:21:11 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1566494472; bh=m7GAq9KcCQN1AMrSXNJmiX2XpN2tNlGh6kt05gJn/9U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=O719mKycz5en6WtcOayM/hj3w7iX8T6WbVca4PzNS3kmjS+vcQri9bMnbDpdRinU9 vbIHmCUycfPmxkEF5Go0LbxKe9nriLbmCORlCEQv9175mfMFiuFdWynE9JmpRGNQMf Te49gC/feJDMOWWZe5g1WPCKTMUOOPUAArtzDkPw=
From: Mike Bishop <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2985/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Changing protocol elements: Is this text strong enough? (#2985)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d5ecf07eaea2_70403f8162ccd968910783"; 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: Thu, 22 Aug 2019 17:21:14 -0000

I think what a client would do is send HEADERS until it sees the SETTINGS frame and discovers it can use HEADERS2 from now on, including in 0-RTT in the future.  No gamble involved, but the server has to continue to support the "old" elements as well.

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