802.11i is the security enhancement that replaces WEP. WPA is a partial
implementation of it.
802.11e, which is is Quality of Service, should also be coming along in
2004.
Way down the road, maybe 2006, 802.11n is aiming at "real" throughputs in
excess of 100mbps ("real" meaning payload throughput, after subtracting for
framing and protocol overhead.
802.11i should just be a firmware upgrade, especially if you bought 802.11g
equipment with newer chipsets. 802.11e may also be just an upgrade.
You won't need 802.11e unless you plan on using VOIP or interactive
multimedia. You may never need 802.11n.
See
http://www.wi-fiplanet.com/tutorials...le.php/3103461.
See also
http://www.wi-fiplanet.com/tutorials...le.php/1439551
for an overview, although it's a little out of date.
"Walter Roberson" <(E-Mail Removed)> wrote in message
news:bs33qj$btc$(E-Mail Removed)...
> In article <UO4Fb.622$(E-Mail Removed)>,
> Arun Hallan <(E-Mail Removed)> wrote:
> :Im thinking of getting a wireless router and just wanted to know:
>
> :1. Is it worth getting one now or is there going to be a new standard etc
> :soon?
>
> There's a new standard every few weeks. Most standards are irrelevant
> to most people.
>
> The next major wireless standard in line is, as far as I know, 802.11i,
> which has to do with Transmitted Power Control (TPC), and with
> automatic selection of frequency (FS??) in cases of interference. These
> two features are requirements for 802.11a in Europe, but vendors
> developing these features seem to be putting them in to 802.11g and b/g
> combinations. I read just a few days ago that in practice there has
> been a migration in Europe towards 802.11b/g to avoid TPC... but that
> could be because there hasn't been a standard for it in the marketplace
> yet. Cisco's Aironet 1100 and 1200 impliment the draft 802.11i
> standards, as do a few other models by other vendors.
>
> Which standard is up after that, I don't know. 802.11k perhaps.
> Or perhaps the three manufacturers doing 108 Mbps over two 802.11g
> channels will get together and iron out a common approach.
> --
> We don't need no side effect-ing
> We don't need no scope control
> No global variables for execution
> Hey! Did you leave those args alone? --
decvax!utzoo!utcsrgv!roderick