From: Josh Lehan <linux@krellan.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Cc: Josh Lehan <linux@krellan.com>, netdev <netdev@vger.kernel.org>
Subject: Re: Skipping past TCP lost packet in userspace
Date: Sun, 05 Jun 2011 23:30:17 -0700 [thread overview]
Message-ID: <4DEC73F9.2040907@krellan.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1106031428280.17529@wel-95.cs.helsinki.fi>
On 06/03/2011 04:51 AM, Ilpo Järvinen wrote:
> And you'd send a cumulative ACK without the actual data segment...?
> ...That's gonna break many middleboxes which would want to see that
> data segment too ...And there goes your "viability" (though with luck it
> will _sometimes_ work as rexmit of the data segment is already in flight).
No, there would be no wire-visible change. This idea was explored at
first, and then rejected. As you mentioned, this would break many
middleboxes. It would rightfully be considered an "optimistic ACK attack".
The late data segment would have to eventually arrive. It would either
be dropped, if the userspace application had already skipped beyond that
point, or better yet, it could be re-inserted into the data stream (if
too late for live playback, then it could at least be saved into the
rewind buffer, or saved to disk if the user is doing that).
> In addition, such a non-legimite cumulative ACK probably violates number
> of TCP RFCs or at least assumptions made in them... e.g., for starters,
> please explain which timestamp you would be putting there into that
> particular cumulative ACK?
It wouldn't change anything on the wire. As you mentioned, timestamps
remain a good defense for guarding against optimistic ACK attacks.
Josh Lehan
prev parent reply other threads:[~2011-06-06 6:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 1:19 Skipping past TCP lost packet in userspace Josh Lehan
2011-05-31 3:30 ` Marcus D. Leech
2011-05-31 4:12 ` Josh Lehan
2011-05-31 4:05 ` Mikael Abrahamsson
2011-05-31 11:12 ` Neil Horman
2011-05-31 17:23 ` Yuchung Cheng
2011-06-01 8:10 ` Josh Lehan
2011-06-01 16:57 ` Bill Sommerfeld
2011-06-01 17:35 ` Rick Jones
2011-06-24 14:58 ` Janardhan Iyengar
2011-06-30 8:38 ` Josh Lehan
2011-06-30 14:36 ` Neil Horman
2011-07-01 8:39 ` Josh Lehan
2011-07-01 13:37 ` Neil Horman
2011-06-01 19:36 ` juice
2011-06-03 11:51 ` Ilpo Järvinen
2011-06-06 6:30 ` Josh Lehan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DEC73F9.2040907@krellan.com \
--to=linux@krellan.com \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).