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

Kazuho Oku <> Tue, 17 September 2019 15:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1F3151200D8 for <>; Tue, 17 Sep 2019 08:56:14 -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 RePmpPsq8rNN for <>; Tue, 17 Sep 2019 08:56:12 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7CE3012009E for <>; Tue, 17 Sep 2019 08:56:12 -0700 (PDT)
Date: Tue, 17 Sep 2019 08:56:11 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1568735771; bh=BJUyw/MTneTpZe5PXXzSlPakh4nG5r4q0yBxriTPLCQ=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=DArPEIgkWJaiyJUXx+tZ3VVd4R/BX7UXS7yOrdutk9/JxkZ+LkJmoCrKtAfqAZNiW ZZgL6+xet4MxWW5DyyK7zrdSpL9axHGfWNhGbefi0h9sN1uvSOwn3Q99cI68VXUF4U SYXFIUBPNkoQtOZ3tDUcY9bD7DmVLGzr+eeLDxLU=
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_5d81021b6bfc5_16f13fdc1c6cd9682030f3"; 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 15:56:14 -0000

> The `SHOULD` is for `in a timely manner`. If you don't do it, the connection will eventually break, likely via a stateless reset.

The question is the intent of using "SHOULD in a timely manner" rather than "MUST in a timely manner". Yes, the connection would break, if the receiver does not migrate to a new connection ID. However, because we use a SHOULD, that is one of the expected outcomes when an endpoint sends a NEW_CONNECTION_ID frame carrying non-zero Retire Prior To field.

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