From: jamal <hadi@cyberus.ca>
To: Simon Oosthoek <wmc_simon@fastmail.fm>
Cc: herman.elfrink@ti-wmc.nl, Stephen Hemminger <shemminger@osdl.org>,
netdev@vger.kernel.org
Subject: Re: [ANNOUNCE] FLAME: external kernel module for L2.5 meshing
Date: Thu, 25 May 2006 11:38:30 -0400 [thread overview]
Message-ID: <1148571510.5283.33.camel@jzny2> (raw)
In-Reply-To: <44758CA8.2030502@fastmail.fm>
On Thu, 2006-25-05 at 12:53 +0200, Simon Oosthoek wrote:
>
> I agree with your analysis, and recently I read an interesting interview
> with her (I think it was linked from slashdot, an interview with the
> "mother of the Internet ;-) I'm not sure her work (I don't exactly
> recall the specifics) is applicable to our problem though.
>
Look at her effort ion rbridges, i think youll find theres a lot in
common.
> Regarding the scalability, I think it rather depends on the number of
> hops how usable FLAME is. I don't think it would scale well to a campus
> or city wide network, but in the case of a few mobile nodes, it has very
> little overhead both in bandwidth and delay.
You should mention this limitation in the paper.
BTW, something else: You ability to create loops of broadcast storms is
highly probable. Eventually you may have to go to L3 (TTL is of value
there) ;->
cheers,
jamal
next prev parent reply other threads:[~2006-05-25 15:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 14:07 [ANNOUNCE] FLAME: external kernel module for L2.5 meshing Herman Elfrink
2006-05-23 14:38 ` Stephen Hemminger
2006-05-23 14:51 ` Simon Oosthoek
2006-05-23 15:09 ` Steven Rostedt
2006-05-23 15:20 ` Alan Cox
2006-05-23 14:48 ` Alan Cox
2006-05-23 14:41 ` Simon Oosthoek
2006-05-23 14:55 ` Erik Mouw
2006-05-23 15:00 ` Simon Oosthoek
2006-05-23 15:14 ` Alan Cox
2006-05-30 6:42 ` Herman Elfrink
2006-05-30 8:43 ` Herman Elfrink
2006-05-23 16:43 ` Stephen Hemminger
2006-05-23 17:43 ` Simon Oosthoek
2006-05-24 18:43 ` jamal
2006-05-25 10:53 ` Simon Oosthoek
2006-05-25 15:38 ` jamal [this message]
2006-05-30 7:01 ` Herman Elfrink
2006-05-24 20:50 ` Pavel Machek
2006-05-25 9:36 ` Simon Oosthoek
2006-05-30 8:29 ` Herman Elfrink
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1148571510.5283.33.camel@jzny2 \
--to=hadi@cyberus.ca \
--cc=herman.elfrink@ti-wmc.nl \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.org \
--cc=wmc_simon@fastmail.fm \
/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