Bug 2875 – NextSegment should not use Rule3 of RFC 6675 when SACK is not enabled

Bug 2875 - NextSegment should not use Rule3 of RFC 6675 when SACK is not enabled


Summary:	NextSegment should not use Rule3 of RFC 6675 when SACK is not enabled

Status:	RESOLVED FIXED

Product:	ns-3
Classification:	Unclassified
Component:	tcp
Version:	ns-3-dev
Hardware:	All All

Importance:	P3 normal
Assigned To:	natale.patriciello

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2018-02-16 10:27 UTC by natale.patriciello
Modified:	2018-02-25 05:40 UTC (History)
CC List:	1 user (show)

See Also:

Attachments
Fixing the bug (960 bytes, patch) 2018-02-16 10:27 UTC, natale.patriciello	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description natale.patriciello 2018-02-16 10:27:14 UTC

Created attachment 3042 [details]
Fixing the bug

As the summary says, till now we used the Rule3 of RFC6675 even when SACK is not enabled. This produces a lot of spurious retransmission, that are problematic for a non-SACK receiver.

Comment 1 natale.patriciello 2018-02-25 05:40:01 UTC

Fixed in 13326:6cd38034e96f