From discussions with Sally Floyd, Andrei Gurtov, Tom Henderson, Bill Hicox, 
Tom Henderson, and Jeffrey Hsu.

RFC 3782, The NewReno Modification to TCP's Fast Recovery Algorithm

Reported by: Sally Floyd; floyd@acm.org,
  from an initial report from Bill Hicox
Date: Tue Jun  1 13:59:16 PDT 2004

In Section 8, the third paragraph could use clarification:

   When not in Fast Recovery, the value of the state variable "recover"
   should be pulled along with the value of the state variable for
   acknowledgments (typically, "snd_una") so that, when large amounts of
   data have been sent and acked, the sequence space does not wrap and
   falsely indicate that Fast Recovery should not be entered (Section 3,
   step 1, last paragraph).

It should say:

   When updating the Cumulative Acknowledgement field outside of
   Fast Recovery, the "recover" state variable may also need to be
   updated in order to continue to permit possible entry into Fast
   Recovery (Section 3, step 1).  This issue arises when an update
   of the Cumulative Acknowledgement field results in a sequence
   wraparound that affects the ordering between the Cumulative
   Acknowledgement field and the "recover" state variable.  Entry
   into Fast Recovery is only possible when the Cumulative
   Acknowledgment field covers more than the "recover" state variable.