Re: [quicwg/base-drafts] Require peers to check if RETIRE_CONNECTION_ID sequence number is valid (#3037)

Kazuho Oku <> Tue, 17 September 2019 09:01 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 013D01200FF for <>; Tue, 17 Sep 2019 02:01:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.382
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id udCnSG8qEAqT for <>; Tue, 17 Sep 2019 02:01:24 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7844B1200EF for <>; Tue, 17 Sep 2019 02:01:24 -0700 (PDT)
Date: Tue, 17 Sep 2019 02:01:23 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1568710883; bh=NM9uAXeel5Ra1EplyB/VFnJ3WjJqGRiMtx7ETfh4l6o=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=P2GMHR56LayyazWZGef/d4/OxCmigTTdYr1Et8idgAqcRfZJU2Ysbn7FQeeGbsqba XG7/HFXZbw2whjsQekqHTEB9o9hujXpzL1IvJ1ckt+NzCAZVC1LRGWmOSkWr2QLmNy UgJMXTW3zDob82RvHIjVgD4dl/ckHudeJSaOHFkc=
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3037/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Require peers to check if RETIRE_CONNECTION_ID sequence number is valid (#3037)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d80a0e3954a0_7393fbced0cd96c155596"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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: Tue, 17 Sep 2019 09:01:26 -0000

I think the question is if we consider *processing* of NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames as a mandatory feature.

Migration is an optional feature of QUIC. For endpoints that do not migrate, there is no reason to update the Connection IDs (note that even though we recently introduced Retire Prior To field, we do not mandate endpoints to respect it - the keyword is "SHOULD"). If we consider that way, I think it is reasonable to never use a MUST for anything related to NEW_CONNECTION_ID or RETIRE_CONNECTION_ID frames.

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