IETF Logo Mail Archive

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

ianswett <notifications@github.com> Tue, 17 September 2019 10:53 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 371E912081B for <quic-issues@ietfa.amsl.com>; Tue, 17 Sep 2019 03:53:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.281
X-Spam-Level:
X-Spam-Status: No, score=-6.281 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
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 kYyDdFf3rTuF for <quic-issues@ietfa.amsl.com>; Tue, 17 Sep 2019 03:53:46 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9C3F120810 for <quic-issues@ietf.org>; Tue, 17 Sep 2019 03:53:45 -0700 (PDT)
Received: from github-lowworker-25680bd.va3-iad.github.net (github-lowworker-25680bd.va3-iad.github.net [10.48.17.61]) by smtp.github.com (Postfix) with ESMTP id E7CD3960E56 for <quic-issues@ietf.org>; Tue, 17 Sep 2019 03:53:44 -0700 (PDT)
Date: Tue, 17 Sep 2019 03:53:44 -0700
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK64EMLTFKKRSVUHJ653RX54REVBNHHB25D7KM@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3037/532169215@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3037@github.com>
References: <quicwg/base-drafts/issues/3037@github.com>
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_5d80bb38d96ae_75f33fd6a02cd95c12084f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/OsAgTjDFdLbCEAyy7TS0zT08y9I>
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: Tue, 17 Sep 2019 10:53:47 -0000

@kazuho I wouldn't encourage people to think of NEW_CONNECTION_ID and RETIRE_CONNECTION_ID as optional, but I agree that effectively they are in many cases.  However, if you sent NEW_CONNECTION_ID, I don't think it's optional to not correctly process RETIRE_CONNECTION_ID, and that's the question here(I copy-pasted the paragraph above).

If the peer never sends RETIRE_CONNECTION_ID because it doesn't fully implement connection ID functionality, then this is not a problem.

-- 
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/3037#issuecomment-532169215

v2.23.0 | Report a Bug | By Email