Return-Path: 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 4F91A120AF8 for ; Mon, 11 Nov 2019 09:49:52 -0800 (PST) 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 38gQxAWA0kWo for ; Mon, 11 Nov 2019 09:49:50 -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 78F94120AEC for ; Mon, 11 Nov 2019 09:49:50 -0800 (PST) Date: Mon, 11 Nov 2019 09:49:49 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1573494589; bh=V12orEMRskDryVtiHXCKHJeWozr8lUkJYkOsIwPbawk=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=aPafePoku/da3j4E3VAHEqoR5sOiwC4f20te5VuwzE33zsHnN6rpr/yinSjMnq7w4 6JebiP0akLOK32ftITMazPvGeEZXtmNJTS0Wvm7uyYTej4c3Za0ctQvg6PYpUeyLTF SRUX39RnHbgfFJMhv+FixUhaGj7BP2KXepJzKINI= From: Gorry Fairhurst Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: Subject: [quicwg/base-drafts] Timer interval for retire the connection IDs (#3215) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5dc99f3da39d7_10d43f86c96cd95c67382"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gorryfair X-GitHub-Recipient: quic-issues X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: quic-issues@ietf.org Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.29 List-Id: Notification list for GitHub issues related to the QUIC WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Nov 2019 17:49:52 -0000 ----==_mimepart_5dc99f3da39d7_10d43f86c96cd95c67382 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable This could be linked to #2130?=0D =0D /Failing to=0D retire the connection IDs within approximately one PTO can cause=0D packets to be delayed, lost, or cause the original endpoint to send a=0D= stateless reset in response to a connection ID it can no longer route=0D= correctly./ =0D - I am unsure what was intended : I=E2=80=99ll argue this is the wrong pe= riod and that one PTO interval seems like it could be small to me. To me,= the PTO is an estimate of the likely response time of the remote endpoin= t - that=E2=80=99s an effective period to commence a retransmission or st= imulate a probe/refresh. Sending a stateless reset is not a minor event, = and as such be tolerant to MSL or at least what in TCP is the RTO. In add= ition, I don=E2=80=99t have a precise understanding of =E2=80=9Croute=E2= =80=9D in this context, and expected something about the path rather than= these words?=0D =0D =0D -- =0D You are receiving this because you are subscribed to this thread.=0D Reply to this email directly or view it on GitHub:=0D https://github.com/quicwg/base-drafts/issues/3215= ----==_mimepart_5dc99f3da39d7_10d43f86c96cd95c67382 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

This could be linked to #2130?

=0D

/Failing to
=0D retire the connection IDs within approximately one PTO can cause
=0D packets to be delayed, lost, or cause the original endpoint to send a
= =0D stateless reset in response to a connection ID it can no longer route
= =0D correctly./

=0D
    =0D
  • I am unsure what was intended : I=E2=80=99ll argue this is the wrong = period and that one PTO interval seems like it could be small to me. To m= e, the PTO is an estimate of the likely response time of the remote endpo= int - that=E2=80=99s an effective period to commence a retransmission or = stimulate a probe/refresh. Sending a stateless reset is not a minor event= , and as such be tolerant to MSL or at least what in TCP is the RTO. In a= ddition, I don=E2=80=99t have a precise understanding of =E2=80=9Croute=E2= =80=9D in this context, and expected something about the path rather than= these words?
    • =0D
=0D =0D

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub, or unsubscribe.3D=

=0D = ----==_mimepart_5dc99f3da39d7_10d43f86c96cd95c67382--