Re: [quicwg/base-drafts] confusing Fast Retransmit modes (#1212)

Praveen Balasubramanian <notifications@github.com> Sun, 18 March 2018 07:01 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 9FB791205D3 for <quic-issues@ietfa.amsl.com>; Sun, 18 Mar 2018 00:01:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.606
X-Spam-Level:
X-Spam-Status: No, score=-0.606 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no 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 sBhcQKMM1kaO for <quic-issues@ietfa.amsl.com>; Sun, 18 Mar 2018 00:01:34 -0700 (PDT)
Received: from o3.sgmail.github.com (o3.sgmail.github.com [192.254.112.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF5AE1201F2 for <quic-issues@ietf.org>; Sun, 18 Mar 2018 00:01:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=/GHLFxojVibfw3fjdE2JSIWb9DI=; b=ZYvyHtfLkC4BKTpw bcriT6Fk2nOEUd+mLYLjb5VH0wKhKa8Noobz02kfhzqpDwa5NJawf2nj0KScnSrR zjgDih8i78CPzEV0MVmzXfrIbkZUJG5ciDqAi440ymk2xwmjThX1CuZzpPnwH759 9cZxY611Egsfma77rWCK45wf72k=
Received: by filter0572p1las1.sendgrid.net with SMTP id filter0572p1las1-29549-5AAE0ECE-3 2018-03-18 07:01:34.104605476 +0000 UTC
Received: from smtp.github.com (out-3.smtp.github.com [192.30.252.194]) by ismtpd0029p1mdw1.sendgrid.net (SG) with ESMTP id Blg7onKTSw-xtt6pcnoDTg for <quic-issues@ietf.org>; Sun, 18 Mar 2018 07:01:33.970 +0000 (UTC)
Date: Sun, 18 Mar 2018 07:01:34 +0000
From: Praveen Balasubramanian <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab78aa2ff9dcb6eaeacc1f4d10f424df754b70f29092cf0000000116c5d0cd92a169ce12379e73@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1212/373977171@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1212@github.com>
References: <quicwg/base-drafts/issues/1212@github.com>
Subject: Re: [quicwg/base-drafts] confusing Fast Retransmit modes (#1212)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5aae0ecdb73cb_197e3f8beea00f2826659d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: pravb
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2OrvKD4Z50KZhjrwDZGF5NKFB/+y85voFWd2 BveMdw7VoCG9xLXa80x7MqI3n7ID6IAxbxZVo54i0zZVzX+ovkwwTdbLnEfMoLcRthJZsW5WVnxZ3+ AL/nEyKd1nxV2a1OFGaPCjEoiwm1IxNfFBlMSca8taYyfkdJsJlVVSW8EZ7hQicHoSiNPou+fSd97A Woony8PqXP8JHeRVsyFgj+
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/92vJNlNwpBwbFM53FXV_ay9lrzs>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 18 Mar 2018 07:01:36 -0000

I don't think these are mutually exclusive modes. With TCP today we do both, if the SACK information suggests lost packets or RACK kicks in and marks packets lost. Time based detection cannot work for low latency connections due to lack of fine grained timers so you always need to augment with packet based detection. IMO an implementation should do both.

-- 
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/1212#issuecomment-373977171