General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: jb <justin@dslr.net>
Cc: "Livingood, Jason" <Jason_Livingood@comcast.com>,
	bloat <Bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] dslreports bufferbloat tests
Date: Wed, 20 Apr 2016 15:43:23 +0300	[thread overview]
Message-ID: <E84FD6F4-29E9-4F3E-A15C-BC23F9E962C3@gmail.com> (raw)
In-Reply-To: <CAH3Ss96mvcKvSHOTrZ93Y+KNzNbY6GFScKD0cAgzX=NBLrwoHA@mail.gmail.com>


> On 20 Apr, 2016, at 09:06, jb <justin@dslr.net> wrote:
> 
> So this particular snap from the first 200 packets of a download there
> are poor RTTs but it also picked up the IP ecn_capable flag (but not
> the IP ecn congestion flag) and it picked up the TCP ece and cwr flags
> on.

The TCP ECE and CWR flags are always set during ECN negotiation.  If there are no CE marks subsequently, they will not appear again once the data phase begins.  You can therefore distinguish between ECN capability of the host and the network.

For a “download” test, your sender will see ECE flags inbound and generate CWR flags outbound *during the data phase* only if there is an ECN aware AQM on the path at the bottleneck.  It will not see the CE marks themselves, as those are only present between the bottleneck and the receiver.

For an “upload" test, your receiver will see the inbound CE marks from an AQM active on the bottleneck, respond to them with ECE flags, and receive CWR flags in reply.  Again, only during the data phase.

 - Jonathan Morton


  parent reply	other threads:[~2016-04-20 12:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-06  1:04 Dave Taht
2016-04-06  1:33 ` Brandon Applegate
2016-04-06  2:21   ` Dave Taht
2016-04-06  3:19     ` jb
2016-04-06 15:30       ` Dave Taht
2016-04-06 16:08         ` Kelvin Edmison
2016-04-07 18:13           ` Livingood, Jason
2016-04-07 18:23             ` Livingood, Jason
2016-04-20  6:06             ` jb
2016-04-20  6:10               ` Dave Taht
2016-04-20 12:43               ` Jonathan Morton [this message]
2016-04-20 22:53                 ` jb
2016-04-21  2:22                   ` Jonathan Morton
2016-04-07  2:06         ` jb
2016-04-07  2:14           ` Jonathan Morton
2016-04-07 18:16         ` Livingood, Jason

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

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E84FD6F4-29E9-4F3E-A15C-BC23F9E962C3@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=Bloat@lists.bufferbloat.net \
    --cc=Jason_Livingood@comcast.com \
    --cc=justin@dslr.net \
    /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