Re: [quicwg/base-drafts] recovery: clarification on TLP when sender is outpacing the timer (#1718)

ianswett <notifications@github.com> Thu, 06 September 2018 15:50 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 2C923130EA2 for <quic-issues@ietfa.amsl.com>; Thu, 6 Sep 2018 08:50:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Level:
X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 vd28FBiMJl8n for <quic-issues@ietfa.amsl.com>; Thu, 6 Sep 2018 08:50:43 -0700 (PDT)
Received: from out-11.smtp.github.com (out-11.smtp.github.com [192.30.254.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1EE16130E92 for <quic-issues@ietf.org>; Thu, 6 Sep 2018 08:50:43 -0700 (PDT)
Date: Thu, 06 Sep 2018 08:50:42 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1536249042; bh=7TwuWsk60aMk5cbXFPE90DExUzwPQBOXZPpJKvq5FVg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=WGExfKUCjuVz4OT10ekiBgwSjU0J7DvyrZ5i/fQUj6FmgzO7HxVanvTbM3OaVo0Io v52hQxoIeHCkS0GDoxqFleFn1LxnWtbC/0SeD7YeM3LUY+XzxN1iK3jC3D3P3Ftj5+ YBgkPiupk1Mqkwa+CFtpwsJ64yT1/Rjwi0y9Y6ps=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abbe255ad67d9a5c8385599b8b1ac6cdd9290134df92cf0000000117a90ed292a169ce153af807@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1718/419145274@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1718@github.com>
References: <quicwg/base-drafts/issues/1718@github.com>
Subject: Re: [quicwg/base-drafts] recovery: clarification on TLP when sender is outpacing the timer (#1718)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b914cd2527b7_65463ff842ed45c0630c7"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/O52sctqGd5zS5wPJzgGW8wwdvw8>
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: Thu, 06 Sep 2018 15:50:47 -0000

To address your first question, PR #1652 adds some more clarity to transport on the idle timeout and makes it clear that if you're sending into a void without receiving any ACKs, you should not keep extending your idle timeout.  The recovery doc doesn't describe anything relating to the idle timer, FWIW.

The intent is for the RTO timer to only go off after TLP.  There is text about setting the TLP to the min(TLP timeout, RTO timeout) in 4.3.2(https://tools.ietf.org/html/draft-ietf-quic-recovery-14#section-4.3.2).  If you want to discuss whether that should be what this document tries to specify, please open a separate issue about whether RTO should ever fire before any TLPs are sent?

Dead peer detection(#1638) is an entirely different problem, and there's no effort to describe that in the recovery draft at the moment.  It would be nice to talk about that somewhere, but I'm not sure it's known what best practices are?

-- 
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/1718#issuecomment-419145274