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 9C412120019 for ; Wed, 3 Jul 2019 02:38:47 -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 sGhgTy4xaJND for ; Wed, 3 Jul 2019 02:38:46 -0700 (PDT) Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9AF412002E for ; Wed, 3 Jul 2019 02:38:45 -0700 (PDT) Date: Wed, 03 Jul 2019 02:38:44 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1562146724; bh=2lul2/k4drggbEm+su6DGBE3MzdnXqkcSe5BoOpEaYE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KjGeDs+1lD7uq19ZJIaT/Hb1QHtvO3SBSAEL9bPKLmhqv9s6t3PDz5uQHgvC13Fst GMgzRnQn61+pNVWjFhyNc6uNCWUvGVKk0TX71WDU/KFgkhM3ee2gZzeB5onGInc8NC VK5nj2/mR4XVckH6XsVocHQ3nwkqU86yj+Bw7o2g= From: Marten Seemann Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Merge Crypto timeout and PTO (#2806) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5d1c77a4bd163_29da3fcfa18cd95c4470e8"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: marten-seemann 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: Wed, 03 Jul 2019 09:38:48 -0000 ----==_mimepart_5d1c77a4bd163_29da3fcfa18cd95c4470e8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit marten-seemann commented on this pull request. > @@ -543,49 +544,46 @@ delay sending an acknowledgement. The PTO value MUST be set to at least kGranularity, to avoid the timer expiring immediately. -When a PTO timer expires, the sender probes the network as described in the next -section. The PTO period MUST be set to twice its current value. This exponential -reduction in the sender's rate is important because the PTOs might be caused by -loss of packets or acknowledgements due to severe congestion. +When a PTO timer expires, the PTO period MUST be set to twice its current +value. This exponential reduction in the sender's rate is important because +the PTOs might be caused by loss of packets or acknowledgements due to severe +congestion. I don't remember any change like that. Every peer decides on its idle timeout. So even if a peer decides to have an infinite idle timeout (why would you do that to yourself?), once you reach a PTO duration on the order of what you might consider a typical idle timeout (let's say 30 seconds), exponential backoff should take care of your concern. -- 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/2806#discussion_r299866909 ----==_mimepart_5d1c77a4bd163_29da3fcfa18cd95c4470e8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

@marten-seemann commented on this pull request.

In draft-ietf-quic-recovery.md:

> @@ -543,49 +544,46 @@ delay sending an acknowledgement.
 The PTO value MUST be set to at least kGranularity, to avoid the timer expiring
 immediately.
 
-When a PTO timer expires, the sender probes the network as described in the next
-section. The PTO period MUST be set to twice its current value. This exponential
-reduction in the sender's rate is important because the PTOs might be caused by
-loss of packets or acknowledgements due to severe congestion.
+When a PTO timer expires, the PTO period MUST be set to twice its current
+value. This exponential reduction in the sender's rate is important because
+the PTOs might be caused by loss of packets or acknowledgements due to severe
+congestion.

I don't remember any change like that. Every peer decides on its idle timeout. So even if a peer decides to have an infinite idle timeout (why would you do that to yourself?), once you reach a PTO duration on the order of what you might consider a typical idle timeout (let's say 30 seconds), exponential backoff should take care of your concern.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5d1c77a4bd163_29da3fcfa18cd95c4470e8--