From: Stephen Hemminger <shemminger@osdl.org>
To: Herman Elfrink <herman.elfrink@ti-wmc.nl>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] FLAME: external kernel module for L2.5 meshing
Date: Tue, 23 May 2006 09:43:24 -0700 [thread overview]
Message-ID: <20060523094324.11926fcc@localhost.localdomain> (raw)
In-Reply-To: <44731733.7000204@ti-wmc.nl>
On Tue, 23 May 2006 16:07:47 +0200
Herman Elfrink <herman.elfrink@ti-wmc.nl> wrote:
>
> FLAME stands for "Forwarding Layer for Meshing"
>
> FLAME provides an intermediate layer between the network layer (e.g.
> IPv4/IPv6) and the link (MAC) layer, providing L2.5 meshing. Both
> network layer and MAC layer can be used unchanged: to the network layer
> FLAME appears as a normal Ethernet-type MAC layer, and the underlying
> `real' MAC layer will see it as just another type of network layer.
>
Didn't you just reinvent 802.1d bridging? and/or WDS?
As far as the Ethernet protocol field. Getting a real assigned number
would have to come out of the IEEE 802.
You would need
http://standards.ieee.org/regauth/ethertype/forms/index.html
It is cheaper (free vs $2500) to get a LLC sap assigned, but then
you would have to change the protocol.
http://standards.ieee.org/regauth/llc/index.html
next prev parent reply other threads:[~2006-05-23 16: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 [this message]
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
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=20060523094324.11926fcc@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=herman.elfrink@ti-wmc.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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.