IETF Logo Mail Archive

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

Martin Thomson <notifications@github.com> Fri, 23 August 2019 00:08 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 0CECE120043 for <quic-issues@ietfa.amsl.com>; Thu, 22 Aug 2019 17:08:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.353
X-Spam-Level:
X-Spam-Status: No, score=-6.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
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 AiZRsg7SfhFl for <quic-issues@ietfa.amsl.com>; Thu, 22 Aug 2019 17:08:41 -0700 (PDT)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 239C31200E3 for <quic-issues@ietf.org>; Thu, 22 Aug 2019 17:08:41 -0700 (PDT)
Received: from github-lowworker-d31a065.va3-iad.github.net (github-lowworker-d31a065.va3-iad.github.net [10.48.17.70]) by smtp.github.com (Postfix) with ESMTP id 40A67C60928 for <quic-issues@ietf.org>; Thu, 22 Aug 2019 17:08:40 -0700 (PDT)
Date: Thu, 22 Aug 2019 17:08:39 -0700
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK254E27VCEO2ANHKGV3NRQQPEVBNHHBZWRADI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2985/524123468@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2985@github.com>
References: <quicwg/base-drafts/issues/2985@github.com>
Subject: Re: [quicwg/base-drafts] Changing protocol elements: Is this text strong enough? (#2985)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d5f2e87ebd35_3d2e3ff8416cd9686997d"; 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/rFp7-SarlkeuxZDU_CS0ADwncLU>
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: Fri, 23 Aug 2019 00:08:43 -0000

Yes, that is how I would do it.  The idea would be that once you advertise support for HEADERS2, you could receive one at any time, but you might still receive the old version for an indefinite period.  You probably shouldn't even rely on seeing an ACK for the SETTINGS frame bits.

-- 
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/2985#issuecomment-524123468

v2.23.0 | Report a Bug | By Email