RFC6675 RescueReTx

hiren panchasara hiren at strugglingcoder.info
Mon Feb 26 02:41:35 UTC 2018

On 02/23/18 at 10:26P, Scheffenegger, Richard wrote:
> Hi,

Hi Richard!
> I've been afk for quite some time, thus I still have to do a bit of catching up. 
> When looking into recent advances in the freebsd tcp stack, I found that some work was done to make the SACK code RFC6675 compliant.
> Before unpacking packetdrill or running a code inspection - can someone tell me, if this means that not only the bug fixes / clarifications of 6675 over 3517 have been implemented, but also the rescue retransmission (section 4, nextseg, clause 4)?

iirc, no. 
> Would still love to get that lost retransmission patch discussed and done properly (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

This part of code can use some love. But, Randall has done quite a rework of
our stack at Netflix which is not yet upstreamed. I am not entirely sure
if this part got needed help but I'd encourage you to check with him
before putting anymore work into it. :-)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 603 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-transport/attachments/20180225/a85d1b1c/attachment.sig>

More information about the freebsd-transport mailing list