Re: [quicwg/base-drafts] MUST retire Connection IDs becoming stale (#3096)

Mike Bishop <notifications@github.com> Tue, 29 October 2019 15:20 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 1611E120868 for <quic-issues@ietfa.amsl.com>; Tue, 29 Oct 2019 08:20:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3
X-Spam-Level:
X-Spam-Status: No, score=-3 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_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, 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 LBAU3PK2ZKMT for <quic-issues@ietfa.amsl.com>; Tue, 29 Oct 2019 08:20:54 -0700 (PDT)
Received: from o5.sgmail.github.com (o5.sgmail.github.com [192.254.113.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8792120904 for <quic-issues@ietf.org>; Tue, 29 Oct 2019 08:20:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=96tUTVtNOyMiK9/BcWmisFZyvhNDqnuTvxxbyh4CBVk=; b= cInrMBQnpAEfSWlawZz5D1v2Ml853KxxfO/2MkuFW4ZWBT4gllEdOHiEOINBh4Ul Nhok50G/guahaQMqxb9lOYpTxtbBE0nEK9RLV2DyZvNLQsZix1vOUMZ1LloYiLrn zgd14fVRUnmZ4t/0yfwzknxpXBJAQ8mQAZpiQQL5cyA=
Received: by filter1453p1las1.sendgrid.net with SMTP id filter1453p1las1-30451-5DB858CE-6D 2019-10-29 15:20:46.687756345 +0000 UTC m=+75506.207260927
Received: from github-lowworker-56a5eb2.cp1-iad.github.net (unknown [140.82.115.70]) by ismtpd0055p1iad1.sendgrid.net (SG) with ESMTP id BvieX5gLTCCEioTMK9o42Q for <quic-issues@ietf.org>; Tue, 29 Oct 2019 15:20:46.476 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-56a5eb2.cp1-iad.github.net (Postfix) with ESMTP id 68CE9C0AA2 for <quic-issues@ietf.org>; Tue, 29 Oct 2019 08:20:46 -0700 (PDT)
Date: Tue, 29 Oct 2019 15:20:46 +0000 (UTC)
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7FLW2QOB4JQTOGA3F3YWMV5EVBNHHB4QFASQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3096/review/308596243@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3096@github.com>
References: <quicwg/base-drafts/pull/3096@github.com>
Subject: Re: [quicwg/base-drafts] MUST retire Connection IDs becoming stale (#3096)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5db858ce66e22_f5a3fe5ebecd9642684be"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak16tLBFrMcC5d4oi4HFluMx5WSDaG0k/KpnRR oHhHWPCTL5316Nul4ejN0eB+Bn9c//cX70tqRTPBnyIR1EUqk6VSGfNLjqpD6/edSGDB+bpAYNqOZF 3ZJnZIZ7k9wkIJmTY9CchjNjcAWyv9QIUoIJtSpL445DSrL2a8qXfP7sEi0jGhUtFHNSlyd9B5IFGf c=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/nlAv4Nmple_A85J15hmeGFcUp-U>
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, 29 Oct 2019 15:20:57 -0000

MikeBishop approved this pull request.

@mikkelfj, the delayed packets are handled by this text:

>  Tokens are invalidated when their associated connection ID is retired via a RETIRE_CONNECTION_ID frame (Section 19.16).

> An endpoint MUST NOT check for any Stateless Reset Tokens associated with connection IDs it has not used or for connection IDs that have been retired.

If you've followed the requirement to retire as indicated, then a delayed packet triggering stateless reset can't hurt you.

> @@ -1032,16 +1032,19 @@ longer plans to use that address.
 
 An endpoint can request that its peer retire connection IDs by sending a

This isn't really a request any more, is it?
```suggestion
An endpoint can cause its peer to retire connection IDs by sending a
```

-- 
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/pull/3096#pullrequestreview-308596243