General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Michael Welzl <michawe@ifi.uio.no>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] mosh, ecn, and diffserv marking
Date: Thu, 14 Jun 2012 11:08:37 +0200	[thread overview]
Message-ID: <4FD9AA15.9080008@ifi.uio.no> (raw)
In-Reply-To: <1339664098.22704.684.camel@edumazet-glaptop>

On 6/14/12 10:54 AM, Eric Dumazet wrote:
> On Thu, 2012-06-14 at 09:22 +0200, Michael Welzl wrote:
>
>> One ECN-specific concern that was addressed is that it's often in the
>> interest of the receiver, but not the sender, to lie about ECN and
>> simply cheat (reflect "nonono, no congestion at all" back to the
>> sender). This is addressed by RFC3540, which is experimental and not
>> really used.
> Yes, apparently :(
>
I tried to restrain myself from self-promoting, but you asked for it   :-)
http://heim.ifi.uio.no/~michawe/research/projects/spurious/index.html

There is code!  - and there are possible additional benefits from the nonce.

I didn't push for that in the IETF because there is a conflict with 
conex (I think? I lost track of all their plans for bits)  for using the 
bit-combination required by the nonce. And conex is a bigger, better 
plan than my "Nonce++" suggestion.

Cheers,
Michael


      reply	other threads:[~2012-06-14  9:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14  3:02 Dave Taht
2012-06-14  7:22 ` Michael Welzl
2012-06-14  8:54   ` Eric Dumazet
2012-06-14  9:08     ` Michael Welzl [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=4FD9AA15.9080008@ifi.uio.no \
    --to=michawe@ifi.uio.no \
    --cc=bloat@lists.bufferbloat.net \
    --cc=eric.dumazet@gmail.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