IETF Logo Mail Archive

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

Nick Banks <notifications@github.com> Tue, 17 September 2019 14:52 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 06381120059 for <quic-issues@ietfa.amsl.com>; Tue, 17 Sep 2019 07:52:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.596
X-Spam-Level:
X-Spam-Status: No, score=-6.596 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_28=1.404, 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: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
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 18R5oCtjucvJ for <quic-issues@ietfa.amsl.com>; Tue, 17 Sep 2019 07:52:07 -0700 (PDT)
Received: from out-19.smtp.github.com (out-19.smtp.github.com [192.30.252.202]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 605F2120045 for <quic-issues@ietf.org>; Tue, 17 Sep 2019 07:52:07 -0700 (PDT)
Date: Tue, 17 Sep 2019 07:52:06 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1568731926; bh=K+dc+2YQ9OD4lHMiYE4dJz8eebVWgFS8NXsWaFjBSSs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=PT70AK3pnz3q9jAv6AtF36GiueXsUlsLnhEWCC1L46/nkftA7thzpBmkxdcmWl+mC JDN1cMXE03TrHsy27GVWkJQUEbQkqr3Z8Lwjy5xb6/d854s4jw+6pKcMaF7UnnrdQW oR0z1zSZ5z4TPAxpOktcbwMkaAEOr8H3i+K3WuOE=
From: Nick Banks <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7JBD5XOCFJVEC4X353RYZ2NEVBNHHB25D7KM@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/532256732@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_5d80f31667867_3b5c3fdbbfacd96c20302b"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nibanks
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/UhtNbXkbv5jTXCHNfPEAEF24jI8>
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 14:52:14 -0000

@kazuho sorry. You're right, I mean the NEW_CONNECTION_ID frame's Retire Prior To field. But I disagree on your interpretation of the `SHOULD`:
> Upon receipt, the peer SHOULD retire the corresponding connection IDs and send the corresponding RETIRE_CONNECTION_ID frames in a timely manner. Failing to do so can cause packets to be delayed, lost, or cause the original endpoint to send a stateless reset in response to a connection ID it can no longer route correctly.

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

-- 
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-532256732

v2.23.0 | Report a Bug | By Email