From: Ing-Jyh Tsang <ing-jyh.tsang@alcatel-lucent.com>
To: Michael Richardson <mcr@sandelman.ca>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] other people's VLAN congestion
Date: Fri, 22 Mar 2013 08:11:02 +0100 [thread overview]
Message-ID: <514C0406.3070601@alcatel-lucent.com> (raw)
In-Reply-To: <14148.1363884839@sandelman.ca>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
On 21/03/2013 17:53, Michael Richardson wrote:
> You'd think that, and the operator I know of is happy to sell an SLA
> for more money. But, the "best effort" service had the property that
> packets were never dropped, but were regularly late, even though my
> edge CPE equipment was prioriziting the way I wanted.
Rigth, in case of BE, not much is done, but mechanism are there. What
are the incentives for the operators (you get what you pay for...)?
However, as higher and higher access BW is offered/sold, this becomes
more visible and operators I know does something about it, all the way
to the CPE. I think the main question is can we improve beyond /RFC
2697/ <http://www.ietf.org/rfc/rfc2697.txt> or /RFC 2698/
<https://tools.ietf.org/rfc/rfc2698.txt>? Specially with adaptive
systems. On the other hand, many hesitated on the "adaptive", more
"intelligence" systems siding/claiming control and stability... Due to
lack of knowledge, mind frame, or ...
[-- Attachment #2: Type: text/html, Size: 1936 bytes --]
prev parent reply other threads:[~2013-03-22 7:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 14:53 Michael Richardson
2013-03-21 15:25 ` Ing-Jyh Tsang
2013-03-21 16:53 ` Michael Richardson
2013-03-22 7:11 ` Ing-Jyh Tsang [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=514C0406.3070601@alcatel-lucent.com \
--to=ing-jyh.tsang@alcatel-lucent.com \
--cc=bloat@lists.bufferbloat.net \
--cc=mcr@sandelman.ca \
/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