…th those for MPTCP and for regular TCP, such as SACK (selective acknowledgment) RFC2018 ) on a single packet. Therefore, an implementation may choose to send duplicate ACKs containing the additional signaling information. This changes the semantics of a duplicate ACK; these are u…

… to implement them is using the Selective Acknowledgment (SACK) option of TCP [ RFC2018 ]. This requires enabling SACK processing at the mobile host. The Snoop agent sends a TCP SACK, when it detects a hole in the transmission sequence from the mobile host or when it has not rece…

… to implement them is using the Selective Acknowledgment (SACK) option of TCP [ RFC2018 ]. This requires enabling SACK processing at the mobile host. The Snoop agent sends a TCP SACK, when it detects a hole in the transmission sequence from the mobile host or when it has not rece…

…re ACK frame. This is unlike reneging for TCP Selective Acknowledgments (SACKs) RFC2018 Packets from different packet number spaces can be identified using the same numeric value. An acknowledgment for a packet needs to indicate both a packet number and a packet number space. Thi…

…ding, which could consume another 2 bytes at most). o SACK permitted (2 bytes) [RFC2018][RFC3517] o Timestamps (10 bytes) [RFC1323] o Window scale (3 bytes) [RFC1323] It should say: TCP's 4-bit data offset requires that the options end 60 bytes (15 32-bit words) after the header …

…ding, which could consume another 2 bytes at most). o SACK permitted (2 bytes) [RFC2018][RFC3517] o Timestamps (10 bytes) [RFC1323] o Window scale (3 bytes) [RFC1323] It should say: TCP's 4-bit data offset requires that the options end 60 bytes (15 32-bit words) after the header …