netdev
[Top] [All Lists]

Re: [PATCH] ieee80211 subsystem

To: Stephen Hemminger <shemminger@xxxxxxxx>, netdev@xxxxxxxxxxx
Subject: Re: [PATCH] ieee80211 subsystem
From: Jean Tourrilhes <jt@xxxxxxxxxx>
Date: Tue, 8 Feb 2005 13:45:39 -0800
Address: HP Labs, 1U-17, 1501 Page Mill road, Palo Alto, CA 94304, USA.
E-mail: jt@xxxxxxxxxx
Organisation: HP Labs Palo Alto
Reply-to: jt@xxxxxxxxxx
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.3.28i
Stephen Hemminger wrote :
> 
> 9. Isn't SNAP generic and not part of just wireless, LLC and other places
>    like ATM have the similar stuff, maybe one set of routines and definitions?
> 

        SNAP is totally generic and IMHO should not be tied to the
wireless stuff. I thought that SNAP was defined in 802.2, but RFC 1042
seems to be the place (which is older than 802.11 or ATM).
        First, if you use true IEEE 802.3 (as oppposed to the usual
Ethernet II), the IP frames will use SNAP encapsulation (because the
802.3 frames don't have a type field). I don't think there is many
networks using 802.3 (mostly admin config error), which is why Linux
doesn't seem to support it.
        More importantly, there is a class of wireless drivers that
would only need SNAP but not the rest of the 802.11 framework, because
they use 802.3 frames natively. A good example is the Orinoco driver,
you will find that the driver has SNAP encapsulation and
decapsulation.
        I can't comment on the ATM stuff...
        I think IEEE has not changed their policy with respect to
802.2, so IMHO we can expect more standard from them requiring SNAP in
the future.
        Have fun...

        Jean

<Prev in Thread] Current Thread [Next in Thread>