IETF Logo Mail Archive

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

"Arvid E. Picciani" <notifications@github.com> Thu, 06 September 2018 16:08 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 36167130E99 for <quic-issues@ietfa.amsl.com>; Thu, 6 Sep 2018 09:08:35 -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 4ZFNmVSFqEDr for <quic-issues@ietfa.amsl.com>; Thu, 6 Sep 2018 09:08:33 -0700 (PDT)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6ED42130DE4 for <quic-issues@ietf.org>; Thu, 6 Sep 2018 09:08:33 -0700 (PDT)
Date: Thu, 06 Sep 2018 09:08:32 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1536250112; bh=Dk99V/BloL5Bl48OTONuIjQraysAIyKVHDodG2QOCwE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=NzE7YjJrtdXgzEOt5dv975NI6P+7Bv3csqZ1TvarHUuElWrexDqdnISxFcqVz62b2 9HrynI7oX9z+HX/GkO6andijciYy/pl4ZX3AF+e7nx1VNQCHr1iSRlgkXiHhlHZEwg /MnTuzxPO5a5qRfZJt7TSszKOaIeUyKfuK4kRzGY=
From: "Arvid E. Picciani" <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abc0a265c7418727fa3a96fd15717328b4f8be49e192cf0000000117a9130092a169ce153af807@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/419151515@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_5b915100524e4_29c33f9b140d45b416393b"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: aep
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/zksHHiK6hRo9YfNIGwjNV7L6gSY>
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 16:08:35 -0000

thanks for clarification.  I'm using a separate timer on idle now that only extends on incomming ack.

It would really help to describe best practices here a little further. But i'm unsure if its needed for other implementors who just follow quic-transport after implementing recovery. 



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

v2.31.3 | Report a Bug | By Email | System Status