From: David Miller <davem@davemloft.net>
To: rick.jones2@hp.com
Cc: johnwheffner@gmail.com, netdev@vger.kernel.org
Subject: Re: A SACK block to the left of the ACK? (with ptr to raw trace)
Date: Fri, 09 May 2014 15:18:03 -0400 (EDT) [thread overview]
Message-ID: <20140509.151803.557587813948439688.davem@davemloft.net> (raw)
In-Reply-To: <536D1D87.3060706@hp.com>
From: Rick Jones <rick.jones2@hp.com>
Date: Fri, 09 May 2014 11:25:11 -0700
> On 05/09/2014 11:21 AM, John Heffner wrote:
>> I didn't actually look at the trace, but offhand this sounds like
>> D-SACK. (http://www.ietf.org/rfc/rfc2883.txt)
>
> Thanks for the gentle tap with the clue-bat :)
Indeed, it's probably a D-SACK and can be used to let the sender
know when a retransmit turned out to be spurious.
prev parent reply other threads:[~2014-05-09 19:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 17:34 A SACK block to the left of the ACK? (with ptr to raw trace) Rick Jones
2014-05-09 18:21 ` John Heffner
2014-05-09 18:25 ` Rick Jones
2014-05-09 19:18 ` David Miller [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=20140509.151803.557587813948439688.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=johnwheffner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
/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).