Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: jp@nexedi.com
Cc: babel-users@lists.alioth.debian.org, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [Babel-users] Lookingfor
Date: Sun, 17 Mar 2013 09:35:49 -0700	[thread overview]
Message-ID: <CAA93jw6hYc=7Am2KEAj5QhA7HqyNEP2RD9b=Qyw1tg0=nQdD8g@mail.gmail.com> (raw)
In-Reply-To: <20130313223423.7567EBF0037@mail2.tiolive.com>

On Wed, Mar 13, 2013 at 3:34 PM,  <jp@nexedi.com> wrote:
> Hi,
>
>> > There is a budget available in a public institution to sponsor a PhD
>> > student who would work on babel.
>>
>> Do you have a topic in mind?  Who would be the supervisor?  What's the
>> deadline?
>
> Everything can be discussed as long as it helps re6st or SlapOS to achieve further resiliency on enterprise applications.
>
> Supervisor would be at ENST.
>
> Current ideas:
> - scalability of babel (1,000,000 nodes network with no backbone)
> - ability for public babel network to survive attacks
> - new metrics
>
> Regards,
>
> JPS.

Scaling dv to a million is something of a challenge.

I would dearly like someone to work with on attempting to implement
new metrics in babel.

Juliusz has described multiple possibilities that seemed promising
that neither he nor I have had time to work on in isolation.

Also fred baker has outlined some interesting ideas for SRC/DST
routing  and address assignment that were just demoed in the ietf
homenet's ospf implementation last week. I think many of the same
ideas and tlvs can be carried over into babel.

Now that I am wrapping up the bufferbloat work

(see cablemodem results at:
http://www.ietf.org/proceedings/86/slides/slides-86-iccrg-3.pdf )

I can also conceive possibilities for wifi congestion and link quality
aware metrics that haven't been tried before...

I hinted at some of them at the MIT talk, "what's wrong with wireless"
http://www.youtube.com/watch?v=Wksh2DPHCDI&feature=youtu.be




>
>
>>
>> -- Juliusz
>>
>>
>> _______________________________________________
>> Babel-users mailing list
>> Babel-users@lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users
>>
>
> _______________________________________________
> Babel-users mailing list
> Babel-users@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/babel-users



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

       reply	other threads:[~2013-03-17 16:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87r4jjkvld.wl%jch@pps.univ-paris-diderot.fr>
     [not found] ` <20130313223423.7567EBF0037@mail2.tiolive.com>
2013-03-17 16:35   ` Dave Taht [this message]
2013-03-17 18:45     ` Benjamin Henrion
2013-03-19 20:28       ` Juliusz Chroboczek
2013-03-19 10:20     ` Toke Høiland-Jørgensen
2013-03-19 12:20       ` jp
2013-03-19 20:13     ` Juliusz Chroboczek

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

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

  git send-email \
    --in-reply-to='CAA93jw6hYc=7Am2KEAj5QhA7HqyNEP2RD9b=Qyw1tg0=nQdD8g@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=babel-users@lists.alioth.debian.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=jp@nexedi.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