From: Simon Oosthoek <wmc_simon@fastmail.fm>
To: hadi@cyberus.ca
Cc: netdev@vger.kernel.org, Stephen Hemminger <shemminger@osdl.org>,
herman.elfrink@ti-wmc.nl
Subject: Re: [ANNOUNCE] FLAME: external kernel module for L2.5 meshing
Date: Thu, 25 May 2006 12:53:28 +0200 [thread overview]
Message-ID: <44758CA8.2030502@fastmail.fm> (raw)
In-Reply-To: <1148496189.5325.33.camel@jzny2>
jamal wrote:
> Essentially you are extending the broadcast domain i.e a bridge within
> on top of a bridge. I would question the scalability of such a beast
> in the presence of many nodes. Also take a look at some of the work
> Radia Perlman (who invented bridging really) is up to these days.
>
>
Hi Jamal
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.
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.
Cheers
Simon
next prev parent reply other threads:[~2006-05-25 10:53 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 [this message]
2006-05-25 15:38 ` jamal
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=44758CA8.2030502@fastmail.fm \
--to=wmc_simon@fastmail.fm \
--cc=hadi@cyberus.ca \
--cc=herman.elfrink@ti-wmc.nl \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.