From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Bufferbloat Mainlinglist <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] No ECN marking in IPv6 linux
Date: Fri, 6 May 2011 13:42:24 -0600 [thread overview]
Message-ID: <BANLkTik=1o9eM1bPrqsRF9W90qwM_PT72w@mail.gmail.com> (raw)
In-Reply-To: <5D1A6041-9ACA-450A-BE9B-F9415F697C65@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 870 bytes --]
On Fri, May 6, 2011 at 12:18 PM, Jonathan Morton <chromatix99@gmail.com>wrote:
>
> On 6 May, 2011, at 9:14 pm, Dave Taht wrote:
>
> > I am curious as to what the correct behavior here should be for
> encapsulated (6in4, 6to4, teredo) packets, and if this functionality was
> also borked. I was under the impression that for encapsulated packets the
> tos field was copied from the encapsulated packet to the ipv4 header.
>
> Intuitively, these protocols are at the same level as IP in the stack, so
> they should preserve ECN information as much as possible. Copying the TOS
> field should be sufficient...
>
>
My concern here is that a AQM-aware (ECN) qdisc such as SFB on the external
interface will not recognize a flow for what it is, when encapsulated...
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
[-- Attachment #2: Type: text/html, Size: 1305 bytes --]
next prev parent reply other threads:[~2011-05-06 19:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 4:44 [Bloat] ECN blocking router found Dave Taht
2011-04-14 14:43 ` Brian Clapper
2011-04-15 17:40 ` Rui Paulo
2011-04-23 7:43 ` Richard Scheffenegger
2011-04-18 16:43 ` [Bloat] tcp_ecn=2 (server-mode ECN) Henrique de Moraes Holschuh
2011-05-06 15:27 ` [Bloat] No ECN marking in IPv6 linux Eric Dumazet
2011-05-06 18:14 ` Dave Taht
2011-05-06 18:18 ` Jonathan Morton
2011-05-06 19:42 ` Dave Taht [this message]
2011-05-09 3:28 ` Dave Taht
2011-05-09 12:11 ` Lars Eggert
2011-05-16 15:09 ` Juliusz Chroboczek
2011-05-06 18:40 ` Matthew Ford
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='BANLkTik=1o9eM1bPrqsRF9W90qwM_PT72w@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@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