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

Martin Thomson <notifications@github.com> Wed, 16 October 2019 15:29 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 83CA8120120 for <quic-issues@ietfa.amsl.com>; Wed, 16 Oct 2019 08:29:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Level:
X-Spam-Status: No, score=-7.999 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_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 12bwdCKnRXsH for <quic-issues@ietfa.amsl.com>; Wed, 16 Oct 2019 08:29:42 -0700 (PDT)
Received: from out-18.smtp.github.com (out-18.smtp.github.com [192.30.252.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A7DB12011F for <quic-issues@ietf.org>; Wed, 16 Oct 2019 08:29:42 -0700 (PDT)
Date: Wed, 16 Oct 2019 08:29:41 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1571239781; bh=AlSTBB7MIJb8Cp6t7z1MyWvgbdLjEWawfR0cTOoGJ68=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ZWAU8NWE1Tem6T6+MvFm0EBoAESj9C8+kK+DoR0Wi2WnAjU6+K3AY5u36OLDul4gI tHmBMeaI53pIVJj6vGzXjQz3N3gQ4qQeUygKr4X8h+s9huKcPdMf6mosyQnY1RaP2X ks0YStzT2xntKpsMVECsQfE4o9e+7cNWFVwespG0=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5V3JBHPGSDOKZUTQV3WR37LEVBNHHB4QFASQ@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/302670225@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_5da7376587994_3dc13fa7918cd96c29038e"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/-vcIncPTgfxKsWB3k7MM3XJRg2Y>
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: Wed, 16 Oct 2019 15:29:46 -0000

martinthomson commented on this pull request.

I think that the most interesting behaviour to specify is at the endpoint that requests retirement.  "Endpoints that request that peers retire connection IDs SHOULD be prepared to receive packets that contain connection IDs that they have requested be retired for a period of approximately three times the PTO."

> @@ -1032,10 +1032,11 @@ longer plans to use that address.
 
 An endpoint can request that its peer retire connection IDs by sending a
 NEW_CONNECTION_ID frame with an increased Retire Prior To field.  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 peer MUST retire the corresponding connection IDs and send corresponding
+RETIRE_CONNECTION_ID frames.  Failing to retire the connection IDs within one
+PTO can cause packets to be delayed, lost, or cause the original endpoint to

Maybe we could even say "approximately", and add "Endpoints that request that peers retire connection IDs SHOULD be prepared to receive packets that contain connection IDs that they have requested be retired for a period of approximately three times the PTO."

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