From: Bob Briscoe <bob.briscoe@bt.com>
To: Manuel Stol <ManuelStol@operamail.com>,
Kevin Gross <kevin.gross@avanw.com>
Cc: post@simula.no, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] RITE and Bufferbloat
Date: Mon, 25 Feb 2013 16:40:28 +0000 [thread overview]
Message-ID: <201302251640.r1PGeRrP019299@bagheera.jungle.bt.co.uk> (raw)
In-Reply-To: <1360894300.5636.140661191719889.549E50EE@webmail.messaging engine.com>
Manuel, Kevin,
Yup - considerable overlap.
RITE is a mix of Linux kernel hackers, IETFers and researchers
(academic & industrial).
Jim Gettys is on the Advisory Board
It's a small EU-funded 3yr project started Nov'12.
In scope are a range of approaches from immediate incremental fixes
to more ambitious.
Covers changes to
- e2e L4 transport algos alone,
- buffer algos alone
- interaction betw the two
<http://riteproject.eu/about-2/>
Bob
At 02:11 15/02/2013, Manuel Stol wrote:
>L.S.,
>
>
>To what extent do the RITE and Bufferbloat projects overlap?
>Are the issues that the Bufferbloat project is trying to address, also
>addressed by the RITE project?
>
>
>RITE - [Reducing Internet Transport Latency]
>http://riteproject.eu/
>
>Bufferbloat - [Addressing chaotic and laggy network performance]
>http://www.bufferbloat.net/
>
>
>Kind regards,
>Manuel Stol
>
>--
>http://www.fastmail.fm - The way an email service should be
>
>_______________________________________________
>Bloat mailing list
>Bloat@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/bloat
________________________________________________________________
Bob Briscoe, BT
prev parent reply other threads:[~2013-02-25 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 2:11 Manuel Stol
[not found] ` <1360894300.5636.140661191719889.549E50EE@webmail.messaging engine.com>
2013-02-25 16:40 ` Bob Briscoe [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=201302251640.r1PGeRrP019299@bagheera.jungle.bt.co.uk \
--to=bob.briscoe@bt.com \
--cc=ManuelStol@operamail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=kevin.gross@avanw.com \
--cc=post@simula.no \
/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