Re: [quicwg/base-drafts] Editorial recovery fixes (#1551)

ianswett <notifications@github.com> Sat, 14 July 2018 19:33 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 BB41D130DF4 for <quic-issues@ietfa.amsl.com>; Sat, 14 Jul 2018 12:33:22 -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 zgucFA8rJVOj for <quic-issues@ietfa.amsl.com>; Sat, 14 Jul 2018 12:33:21 -0700 (PDT)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6318130DDC for <quic-issues@ietf.org>; Sat, 14 Jul 2018 12:33:20 -0700 (PDT)
Date: Sat, 14 Jul 2018 12:33:20 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1531596800; bh=VhB0Wsv8gCvFx2HZDOgMsxHgO2M2Owqgk/vG2pvG8as=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=VYf65KhZqgub46iUry8IBsPCC6JhiJLmk1PaYn1MDuGPScEjL0sB9rPu5DOo9h33v PrkQaKjuxz+qBMz8BNEgnx4/IsoLf1aSyKeRe2YbxaVyqkDHqqZKgXICNggwEuDqoE JfRlgV51JiN1Wpo/1raV9w0mkaA3VUZdd2VM0PFQ=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abbd3a5fa3b3049d5cc2f10fdab39dbfe2379fa73d92cf000000011762120092a169ce144b173f@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/1551/review/137246822@github.com>
In-Reply-To: <quicwg/base-drafts/pull/1551@github.com>
References: <quicwg/base-drafts/pull/1551@github.com>
Subject: Re: [quicwg/base-drafts] Editorial recovery fixes (#1551)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b4a500035171_4e5b3fc380cf2f78292518"; 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/7FbR6AUSSrr_u9g5QjgjVK-LnSI>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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: Sat, 14 Jul 2018 19:33:23 -0000

ianswett commented on this pull request.



> -reordering of packets in the network.
-
-The RECOMMENDED initial value for kReorderingThreshold is 3.
-
-We derive this recommendation from TCP loss recovery {{?RFC5681}}
-{{?RFC6675}}. It is possible for networks to exhibit higher degrees of
-reordering, causing a sender to detect spurious losses. Detecting spurious
-losses leads to unnecessary retransmissions and may result in degraded
+and/or a threshold amount of time after the unacknowledged packet. Receipt of the
+ack indicates that a later packet was received, the reordering threshold
+provides some tolerance for reordering of packets in the network.
+
+The RECOMMENDED initial value for kReorderingThreshold is 3, based on 
+TCP loss recovery {{?RFC5681}} {{?RFC6675}}. Some networks may exhibit higher
+degrees of reordering, causing a sender to detect spurious losses. Detecting
+spurious losses leads to unnecessary retransmissions and may result in degraded

Agreed, its either confusing or wrong, depending on your perspective.

How about spuriously detecting losses?

-- 
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/1551#discussion_r202523506