From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: "cheshire@apple.com" <cheshire@apple.com>,
"iccrg@irtf.org" <iccrg@irtf.org>,
"Bob Briscoe (bob.briscoe@bt.com)" <bob.briscoe@bt.com>,
"Ingemar Johansson S" <ingemar.s.johansson@ericsson.com>,
"Mirja Kühlewind" <mirja.kuehlewind@tik.ee.ethz.ch>,
"bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>,
"ietf@trammell.ch" <ietf@trammell.ch>
Subject: Re: [Bloat] ECN issues
Date: Fri, 26 Jun 2015 13:05:39 +0200 [thread overview]
Message-ID: <87fv5eafwc.wl-jch@pps.univ-paris-diderot.fr> (raw)
In-Reply-To: <40204878-C1F4-4AFE-8FD8-72D0B83144FE@gmail.com>
> The conventional wisdom certainly is that ECN should be left off simple
> 1-RTT request-response protocols,
Just to avoid any misunderstandings:
- Babel does not use ECN; the marking is due to Dave's local hack;
- Babel is an asynchronous protocol that runs (mostly) over multicast,
not a request-response protocol, so there's no obvious way to carry
an echo bit in it;
- Babel is designed to work well over extremely lossy links (with the
standard implementation working reasonably well at 85% pre-ARQ loss).
[Shouldn't we be dropping people from the CC?]
-- Juliusz
next prev parent reply other threads:[~2015-06-26 11:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 11:34 Ingemar Johansson S
2015-06-24 11:48 ` Hagen Paul Pfeifer
[not found] ` <04ED8D23-53C3-4F12-9647-3A07FFB43352@tik.ee.ethz.ch>
2015-06-25 17:49 ` Dave Taht
2015-06-25 18:15 ` Jonathan Morton
2015-06-25 18:52 ` David Lang
2015-06-26 11:05 ` Juliusz Chroboczek [this message]
2015-06-25 19:02 ` Ingemar Johansson S
2015-06-25 22:07 ` Jonathan Morton
[not found] ` <6D65AC6E-4AA1-4F8C-B758-D63EEC59A0E2@tik.ee.ethz.ch>
2015-07-19 8:21 ` [Bloat] [iccrg] " Scheffenegger, Richard
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=87fv5eafwc.wl-jch@pps.univ-paris-diderot.fr \
--to=jch@pps.univ-paris-diderot.fr \
--cc=bloat@lists.bufferbloat.net \
--cc=bob.briscoe@bt.com \
--cc=cheshire@apple.com \
--cc=chromatix99@gmail.com \
--cc=iccrg@irtf.org \
--cc=ietf@trammell.ch \
--cc=ingemar.s.johansson@ericsson.com \
--cc=mirja.kuehlewind@tik.ee.ethz.ch \
/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