General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Eggert\, Lars" <lars@netapp.com>
Cc: "Akhtar, Shahid \(Shahid\)" <shahid.akhtar@alcatel-lucent.com>,
	"iccrg@irtf.org" <iccrg@irtf.org>, "aqm@ietf.org" <aqm@ietf.org>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [iccrg] [aqm] AQM deployment status?
Date: Fri, 11 Oct 2013 23:18:05 -0400	[thread overview]
Message-ID: <12845.1381547885@sandelman.ca> (raw)
In-Reply-To: <FB9F71A5-C19E-405D-A598-BC704C38B3AA@netapp.com>

[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]


Eggert, Lars <lars@netapp.com> wrote:
    > I've heard that statement [that RED is supported] from many different
    > people. I wonder if it is
    > actually true. Is there any hard data on this?

The issue I've had is that while RED is supported on a routing device,
and I can enable it on a per-VLAN basis, that does me little good, because
there are bottlenecks in layer-2 devices (ethernet, but also DSL,GPON, etc.)
which are out of my control.

What I would like is a standard layer-3 way to measure bandwidth across
my layer-3 hop, and autoconfigure RED (or CoDel) to the measured bandwidth.
My understanding is that some equipment can use 802.1ad CCP and/or Loopback
frames to measure bandwidth across bridged layer-2 ethernet networks.

I'm unclear if this is a feature of that equipment, or a part of the
standard.  My understanding is that the math involved is pretty
straightforward, but getting it right in code can involve dealing with a
number of numerical issues which makes it slightly non-trivial to
implement. (And you need good low-latency time stamping of packets)

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works



[-- Attachment #2: Type: application/pgp-signature, Size: 307 bytes --]

      parent reply	other threads:[~2013-10-12  3:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24 17:21 [Bloat] " Naeem Khademi
2013-09-24 17:24 ` [Bloat] [aqm] " LOCHIN Emmanuel
2013-09-25 14:20 ` Akhtar, Shahid (Shahid)
2013-09-25 14:31   ` [Bloat] [iccrg] " Eggert, Lars
2013-09-25 14:35     ` Steinar H. Gunderson
2013-09-25 18:51       ` Akhtar, Shahid (Shahid)
2013-09-25 19:19         ` [Bloat] [aqm] [iccrg] " Naeem Khademi
2013-09-27 16:49           ` Akhtar, Shahid (Shahid)
2013-09-25 19:24         ` Mikael Abrahamsson
2013-09-26  9:39           ` [Bloat] [iccrg] [aqm] " Scheffenegger, Richard
2013-09-27  2:59             ` Mikael Abrahamsson
2013-09-27  9:06               ` Eggert, Lars
2013-09-28  7:01                 ` Mikael Abrahamsson
2013-09-28  7:04                   ` Eggert, Lars
2013-09-29  1:16                     ` [Bloat] [aqm] [iccrg] " Bob Briscoe
2013-09-29  9:37                       ` Mikael Abrahamsson
2013-09-27 13:53               ` [Bloat] [iccrg] [aqm] " Scheffenegger, Richard
2013-09-28  6:59                 ` Mikael Abrahamsson
2013-11-13 17:50           ` [Bloat] [aqm] [iccrg] " Fred Baker (fred)
2013-10-12  3:18     ` Michael Richardson [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

  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=12845.1381547885@sandelman.ca \
    --to=mcr+ietf@sandelman.ca \
    --cc=aqm@ietf.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=iccrg@irtf.org \
    --cc=lars@netapp.com \
    --cc=shahid.akhtar@alcatel-lucent.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