Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Ingemar Johansson S <ingemar.s.johansson@ericsson.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] [aqm] ECN support for UDP (was RE: [rmcat] [rtcweb] Catching up on diffserv markings)
Date: Fri, 23 Oct 2015 16:31:55 +0300	[thread overview]
Message-ID: <B590EA62-2C01-46CE-BFF0-661FE7EE73DB@gmail.com> (raw)
In-Reply-To: <81564C0D7D4D2A4B9A86C8C7404A13DA34C0AE3A@ESESSMB205.ericsson.se>


> On 23 Oct, 2015, at 11:40, Ingemar Johansson S <ingemar.s.johansson@ericsson.com> wrote:
> 
> Network wise, I guess the support for ECN for UDP is a matter of configuration, but if one look from strict radio (LTE) perspective it does not really matter if it is UDP or TCP over IP, it is treated the same, thus the strategy for ECN marking should be the same and should preferably follow the guidelines in RFC7567.

All the Linux qdiscs I’m aware of that support ECN are agnostic to the transport layer in this respect.  If ECN capability is advertised in a packet’s IP header, it’s eligible for ECN CE marking.

 - Jonathan Morton


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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23  8:40 [Cake] " Ingemar Johansson S
2015-10-23 13:31 ` Jonathan Morton [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/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=B590EA62-2C01-46CE-BFF0-661FE7EE73DB@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=aqm@ietf.org \
    --cc=cake@lists.bufferbloat.net \
    --cc=csp@csperkins.org \
    --cc=ingemar.s.johansson@ericsson.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