From: jamal <hadi@cyberus.ca>
To: Simon Oosthoek <wmc_simon@fastmail.fm>
Cc: netdev@vger.kernel.org, Stephen Hemminger <shemminger@osdl.org>
Subject: Re: [ANNOUNCE] FLAME: external kernel module for L2.5 meshing
Date: Wed, 24 May 2006 14:43:08 -0400 [thread overview]
Message-ID: <1148496189.5325.33.camel@jzny2> (raw)
In-Reply-To: <447349A6.50105@fastmail.fm>
On Tue, 2006-23-05 at 19:43 +0200, Simon Oosthoek wrote:
> Stephen Hemminger wrote:
> > On Tue, 23 May 2006 16:07:47 +0200
> > Herman Elfrink <herman.elfrink@ti-wmc.nl> wrote:
> >
> >>
> >> FLAME stands for "Forwarding Layer for Meshing"
> >>
> >
> > Didn't you just reinvent 802.1d bridging? and/or WDS?
>
> I wouldn't say "reinvent", but the difference is small but significant.
> FLAME could be seen as ad hoc WDS, I think. It doesn't need to know
> about the other "base-stations", which I think WDS does.
>
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.
cheers,
jamal
next prev parent reply other threads:[~2006-05-24 18:43 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 [this message]
2006-05-25 10:53 ` Simon Oosthoek
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=1148496189.5325.33.camel@jzny2 \
--to=hadi@cyberus.ca \
--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