Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Justin Uberti <juberti@google.com>
Cc: "Pal Martinsen \(palmarti\)" <palmarti@cisco.com>,
	"aqm@ietf.org" <aqm@ietf.org>,
	"cake@lists.bufferbloat.net" <cake@lists.bufferbloat.net>,
	"rmcat@ietf.org" <rmcat@ietf.org>,
	"rtcweb@ietf.org" <rtcweb@ietf.org>,
	Colin Perkins <csp@csperkins.org>
Subject: Re: [Cake] [rmcat] [rtcweb] Catching up on diffserv markings
Date: Fri, 23 Oct 2015 16:29:28 +0300	[thread overview]
Message-ID: <DD2B1AA2-4F92-401C-91F1-8E0731CBE63E@gmail.com> (raw)
In-Reply-To: <CAOJ7v-1RJbhe3i+_newDBObtJfJM6pWZUyRb4GZ8BHRDdDyKDg@mail.gmail.com>


> On 22 Oct, 2015, at 22:54, Justin Uberti <juberti@google.com> wrote:
> 
> At present I'm not aware of any widely-deployed OS where an app can read the received ECN markings. 

I have personally verified that this is possible (for UDP) on Linux - we were investigating the feasibility of adding ECN to uTP (ie. BitTorrent).  The code looks horrid, but what raw sockets code doesn’t?

 - Jonathan Morton


  reply	other threads:[~2015-10-23 13:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 15:51 [Cake] " Dave Taht
2015-10-21 16:10 ` [Cake] [rtcweb] " Harald Alvestrand
2015-10-22  7:48   ` Pal Martinsen (palmarti)
2015-10-22  9:13     ` Colin Perkins
2015-10-22 19:54       ` [Cake] [rmcat] " Justin Uberti
2015-10-23 13:29         ` Jonathan Morton [this message]
2015-10-23 13:31         ` Loganaden Velvindron
2015-10-27  8:06         ` Sebastian Moeller
2015-10-27 16:16           ` Justin Uberti
2015-10-27 17:04             ` Sebastian Moeller
2015-10-29 15:25         ` Piers O'Hanlon
2015-10-22 20:02       ` [Cake] [aqm] " Christian Huitema

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/cake.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=DD2B1AA2-4F92-401C-91F1-8E0731CBE63E@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=aqm@ietf.org \
    --cc=cake@lists.bufferbloat.net \
    --cc=csp@csperkins.org \
    --cc=juberti@google.com \
    --cc=palmarti@cisco.com \
    --cc=rmcat@ietf.org \
    --cc=rtcweb@ietf.org \
    /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