Date: Fri, 23 Feb 2018 22:26:58 +0000 From: "Scheffenegger, Richard" <Richard.Scheffenegger@netapp.com> To: "freebsd-transport@freebsd.org" <freebsd-transport@freebsd.org> Subject: RFC6675 RescueReTx Message-ID: <CY4PR0601MB373128739C59BB16304CFF4886CC0@CY4PR0601MB3731.namprd06.prod.outlook.com>
next in thread | raw e-mail | index | archive | help
Hi, I've been afk for quite some time, thus I still have to do a bit of catchin= g up.=20 When looking into recent advances in the freebsd tcp stack, I found that so= me work was done to make the SACK code RFC6675 compliant. Before unpacking packetdrill or running a code inspection - can someone tel= l me, if this means that not only the bug fixes / clarifications of 6675 ov= er 3517 have been implemented, but also the rescue retransmission (section = 4, nextseg, clause 4)? Would still love to get that lost retransmission patch discussed and done p= roperly (cc reaction on each iteration is missing; that patch preceeds the = modular_cc work though) one of these days though. https://lists.freebsd.org/pipermail/freebsd-net/2010-April/025061.html Thanks a lot,=20 Richard Scheffenegger
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CY4PR0601MB373128739C59BB16304CFF4886CC0>