| > This patch consolidates initial-window code common to TCP and CCID-2:
| > * TCP uses RFC 3390 in a packet-oriented manner (tcp_input.c) and
| > * CCID-2 uses RFC 3390 in packet-oriented manner (RFC 4341).
...
| > +static inline u32 rfc3390_bytes_to_packets(const u32 smss)
| > +{
| > + return smss <= 1095 ? 4 : (smss > 1460 ? 2 : 3);
| > +}
| > +
...
|
| What is spelled out in tcp_select_initial_window might also need to follow
| the same logic?
|
Thank you for paying attention, can you please have a look at the subsequent
patch. I went through this yesterday and found that in 4 different places
there are 4 different interpretations of what RFC 3390 means.
Having asked someone more familiar with IETF issues, it seems that the RFC 5681
interpretation of RFC 3390 is now the 'official' one.
+------------+--------------------+--------------------+--------------------+--------------------+
| Condition | RFC 2414 | Linux | Linux | RFC 5681 |
| | RFC 3390 | tcp_input | tcp_output | |
+------------+--------------------+--------------------+--------------------+--------------------+
| 2 segments | 2190 < MSS | 1460 < MSS | 4380 < MSS | 2190 < MSS |
| 3 segments | 1095 < MSS <= 1460 | 1095 < MSS <= 1460 | 1460 < MSS <= 4380 | 1095 < MSS <= 2190 |
| 4 segments | MSS <= 1095 | MSS <= 1095 | MSS <= 1460 | MSS <= 1095 |
+------------+--------------------+--------------------+--------------------+--------------------+
--
To unsubscribe from this list: send the line "unsubscribe dccp" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
