[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [task #14128] Appropriate byte counting/stretch ACK support

From: Joel Cunningham
Subject: [lwip-devel] [task #14128] Appropriate byte counting/stretch ACK support
Date: Wed, 15 Mar 2017 10:40:48 -0400 (EDT)
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/602.4.8 (KHTML, like Gecko) Version/10.0.3 Safari/602.4.8

Follow-up Comment #17, task #14128 (project lwip):


Thanks for catching L=1*SMSS following a RTO.  I'll account for this in an
updated patch.  I think we can appropriately detect this scenario by checking
the unsent queue for segments where the sequence number is less than
pcb->snd_nxt.  This would only happen after an RTO and all unacked segments
have been moved back to the unsent queue

In terms of TCP_ABC_LIMIT.  I was thinking of leaving it as an option in order
to allow for a port to use L of 1 in cases where they want ABC to protect
against ACK division, but not deviate from RFC 5681 (which recommends cwnd +=
min(acked, 1*SMSS).  Leaving L as configurable also would allow a port to
account for a larger number (> 2*SMSS) of stretch ACKs if there is a scenario
where this is desirable/valid


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]