From 07f4e5d98de646a3edff7d09572282e7b576a888 Mon Sep 17 00:00:00 2001
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Tue, 11 Dec 2018 16:49:53 -0800
Subject: [PATCH] Add FACK reference

---
 draft-ietf-quic-recovery.md | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/draft-ietf-quic-recovery.md b/draft-ietf-quic-recovery.md
index 77272264ec..e0930aaea7 100644
--- a/draft-ietf-quic-recovery.md
+++ b/draft-ietf-quic-recovery.md
@@ -44,6 +44,15 @@ normative:
         org: Mozilla
         role: editor
 
+informative:
+
+  FACK:
+    title: "Forward Acknowledgement: Refining TCP Congestion Control"
+    author:
+      - ins: M. Mathis
+      - ins: J. Mahdavi
+    date: 1996-08
+    seriesinfo: ACM SIGCOMM
 
 --- abstract
 
@@ -325,7 +334,8 @@ smaller initial reordering thresholds to minimize recovery latency.
 ### Packet Threshold
 
 The RECOMMENDED initial value for the packet reordering threshold
-(kPacketThreshold) is 3, based on TCP loss detection {{?RFC5681}} {{?RFC6675}}.
+(kPacketThreshold) is 3, based on best practices for TCP loss detection
+{{?RFC5681}} {{?RFC6675}} {{FACK}}.
 
 Some networks may exhibit higher degrees of reordering, causing a sender to
 detect spurious losses.  Implementers MAY use algorithms developed for TCP, such