Re: [quicwg/base-drafts] Timer interval for retire the connection IDs (#3215)
Kazuho Oku <notifications@github.com> Tue, 12 November 2019 17:51 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 7FE0612097F for <quic-issues@ietfa.amsl.com>; Tue, 12 Nov 2019 09:51:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
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: 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 Ga4ax8FtX-r8 for <quic-issues@ietfa.amsl.com>; Tue, 12 Nov 2019 09:51:41 -0800 (PST)
Received: from out-20.smtp.github.com (out-20.smtp.github.com [192.30.252.203]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9DDA120959 for <quic-issues@ietf.org>; Tue, 12 Nov 2019 09:51:41 -0800 (PST)
Received: from github-lowworker-c5134a3.ac4-iad.github.net (github-lowworker-c5134a3.ac4-iad.github.net [10.52.23.55]) by smtp.github.com (Postfix) with ESMTP id AC4E58C11B6 for <quic-issues@ietf.org>; Tue, 12 Nov 2019 09:51:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1573581100; bh=3/jZp+FTaPkxmyBJ13jKZg9gYsRlhH9VgGy/yk1P0Tw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ruJBy7NNpdeJNoSHBMEfxh0r3/R11Wa7RtvXNvQWzcut7cIy8W0apRV2158CGjs9l qdRD61gXk41XjeHFdIZ1XJm8nbVKFA4v4+cMjiwRO9L+zqDh186vtMsyxfapo9XMDD 2ded2M2qFURblV3vdS/Z4fGuTnd0eOG9oG72K4U0=
Date: Tue, 12 Nov 2019 09:51:40 -0800
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYPPUHHWY6O5FP3TUV33AR2ZEVBNHHB6D24WU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3215/553011062@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3215@github.com>
References: <quicwg/base-drafts/issues/3215@github.com>
Subject: Re: [quicwg/base-drafts] Timer interval for retire the connection IDs (#3215)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dcaf12c9e259_b8d3fa2324cd95c478891"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/V6PkcncCbGUqBQ9S_1LfBt9AzJ4>
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, 12 Nov 2019 17:51:43 -0000
I might argue that the 3 PTO suggestion for the issuer makes sense. We need some guidance for the issuer that is easy to implement and also tolerant to reordering. 3 PTO is a good fit for that. The question IMO is if we need something more than that. It might be possible to argue that the current recommendation of 1 PTO is a rough derivation of the 3 PTO rule, but it's confusing. Maybe something like "SHOULD ... in a timely manner, as the issuer of the CIDs might drop the retired CIDs as early as 3 PTO" would be enough. -- 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/3215#issuecomment-553011062
- [quicwg/base-drafts] Timer interval for retire th… Gorry Fairhurst
- Re: [quicwg/base-drafts] Timer interval for retir… Mike Bishop
- Re: [quicwg/base-drafts] Timer interval for retir… Martin Thomson
- Re: [quicwg/base-drafts] Timer interval for retir… Mike Bishop
- Re: [quicwg/base-drafts] Timer interval for retir… Martin Thomson
- Re: [quicwg/base-drafts] Timer interval for retir… Eric Kinnear
- Re: [quicwg/base-drafts] Timer interval for retir… Mike Bishop
- Re: [quicwg/base-drafts] Timer interval for retir… Kazuho Oku
- Re: [quicwg/base-drafts] Timer interval for retir… Lars Eggert
- Re: [quicwg/base-drafts] Timer interval for retir… Kazuho Oku
- Re: [quicwg/base-drafts] Timer interval for retir… Lars Eggert
- Re: [quicwg/base-drafts] Timer interval for retir… Mike Bishop
- Re: [quicwg/base-drafts] Timer interval for retir… Martin Thomson