Beta

×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

IEEE Approves 802.11n Wi-Fi Standard

Soulskill posted more than 4 years ago | from the lightning-fast dept.

Wireless Networking 115

alphadogg writes "The IEEE has finally approved the 802.11n high-throughput wireless LAN standard. Bruce Kraemer, the long-time chairman of the 802.11n Task Group (part of the 802.11 Working Group, which oversees the WLAN standards), has sent out a notification to a listserv for task group members, which includes a wide range of Wi-Fi chip makers, software developers, and equipment vendors. A press release is available now as well. This process began in 2002."

cancel ×

115 comments

Sorry! There are no comments related to the filter you selected.

First post... (0, Funny)

Anonymous Coward | more than 4 years ago | (#29394609)

but on 802.11g network... FAIL

Re:First post... (0)

Anonymous Coward | more than 4 years ago | (#29396953)

why funny?

Umm... ok, thanks. (5, Insightful)

NitroWolf (72977) | more than 4 years ago | (#29394613)

Gee thanks. Appreciate the timely response, Bruce. I'm glad the 802.11n Task Group was so on this project that they got the 802.11n standard finally approved years after all vendors have already been making products. Yeah, thanks.

Next time... I don't know... maybe define the standard in a reasonable time frame, not 5 years after the fact.

Re:Umm... ok, thanks. (2, Insightful)

Brian Gordon (987471) | more than 4 years ago | (#29394639)

It's the vendors that built products early not the IEEE that defined the standard late.

Still, it would be nice to know what's been delaying the final approval for so long.

Re:Umm... ok, thanks. (4, Insightful)

NitroWolf (72977) | more than 4 years ago | (#29394677)

They built the products early because the IEEE was dragging their feet on the final approval. The IEEE defined the standard exceptionally late - that's WHY the vendors built early. You've got the cause and effect totally reversed.

Re:Umm... ok, thanks. (4, Informative)

More_Cowbell (957742) | more than 4 years ago | (#29394821)

Totally agree with you, but for me, here is the important part (emphasis mine):

...--will enable rollout of significantly more scalable WLANs that deliver 10-fold-greater data rates than previously defined while ensuring co-existence with legacy systems and security implementations.

So, cool. Don't know which I'll be replacing first, my laptop with 11.n or my wireless router - but it's nice to know that any new device will work with the old. (The extra throughput would not benefit me as my cable internet is the current weak link...)

Re:Umm... ok, thanks. (3, Informative)

Supergibbs (786716) | more than 4 years ago | (#29394855)

It's great for LAN file transfers. I used to use ethernet cables to transfer large files between my laptop and desktop. Now (until HD throughput increases) I don't need to.

Re:Umm... ok, thanks. (1, Informative)

Anonymous Coward | more than 4 years ago | (#29396765)

Actual hard disk throughput is generally about 800 Mbps. Fastest 11n throughput I've seen (and I've seen many!) was about 85 Mbps. Currently the only way to even approach the rate what a SINGLE hard disk can output is to use gigabit wired ethernet.

Re:Umm... ok, thanks. (3, Informative)

Trongy (64652) | more than 4 years ago | (#29394961)

Co-existence means more than that. It means that your neighbour's new .11n equipment shouldn't clobber your existing .11g network. That's important to those in densely packed urban areas

Re:Umm... ok, thanks. (1)

Lord Ender (156273) | more than 4 years ago | (#29396325)

Screw your cable link. I found N to be a great benefit when streaming HD video from my file server to my media server.

vendors are part of IEEE (5, Informative)

Anonymous Coward | more than 4 years ago | (#29394997)

They built the products early because the IEEE was dragging their feet on the final approval. The IEEE defined the standard exceptionally late - that's WHY the vendors built early. You've got the cause and effect totally reversed.

And it's not like the vendors had anything to do with the delay. They certainly worked together in a harmonious fashion without trying to push their own technological agenda into the working group. /sarcasm

Who do you think was in the IEEE effort? It was the vendors themselves. Just look at the 802.11 member list:

http://www.ieee802.org/11/Voters/votingmembers.htm

It was the members themselves that couldn't decide between the competing technologies (TGn Sync and WWiSE):

http://www.wi-fiplanet.com/news/article.php/3490926
http://www.networkworld.com/net.worker/news/2005/020705netleadside.html

The IEEE is not some ivory tower institution sending down standards from the clouds like Zeus and his lightning bolts. It is made up of members, and those members are sponsored by their employers to work on these standards (and there may even be a few "independents" as well).

The IEEE took a long time to come to a consensus because the vendors (through their paid employees) took a long time to come to a consensus.

Re:vendors are part of IEEE (1)

PC and Sony Fanboy (1248258) | more than 4 years ago | (#29395501)

I was under the impression that the australians were blocking 802.11n due to some absurd claims of privacy, hackability, or spectrum laws.

Re:vendors are part of IEEE (2, Informative)

nirjhari (1039166) | more than 4 years ago | (#29395563)

If my memory serves right (it's kind of fading these days; it's been a long time....) it was the result of patent claims from some state-funded institution in Australia: http://en.wikipedia.org/wiki/IEEE_802.11n [wikipedia.org]

Re:vendors are part of IEEE (5, Funny)

Citizen of Earth (569446) | more than 4 years ago | (#29396381)

The IEEE is not some ivory tower institution sending down standards from the clouds like Zeus and his lightning bolts.

So it's not like ISO.

Re:Umm... ok, thanks. (1)

commodore64_love (1445365) | more than 4 years ago | (#29394783)

>>>It's the vendors that built products early not the IEEE that defined the standard late.

That happened during the 90s as well. Companies got tired of waiting for the IEEE, so they just ran-off and created their own 19.2k, 28.8k, 33.6k and 56k modems using proprietary designs. They made these modems flash-based so users could later upgrade the modems to be compliant with the late-released spec. Technology moves faster than the specification groups can keep up.

Re:Umm... ok, thanks. (4, Informative)

squiggleslash (241428) | more than 4 years ago | (#29395131)

You meant the ITU, right? IEEE is an entirely different organization.

The other thing was the context was a market where there already were a lot of non-ITU standards. V.32 came about as an effort to get modem manufacturers to unify on a common standard after virtually everyone did their own (entirely different, unrelated to any ITU effort) thing to get to 9600bps. Some modified V.29 to make it kinda full duplex, others did OFDM, others came up with even more exotic systems.

V.32 was finally released, and quickly followed by V.32bis. At this point:

- Some companies just stretched V.32 a little bit more and came up with V.32terbo. Nobody did this in anticipation of an ITU standard though, obviously, they'd have been happy if it had been supported.

- Hayes and USR, on opposite sides, came up with V.FC and 56KFlex, neither directly in anticipation of a specific ITU standard but hoping their technology would form the basis of "the next" ITU standard, whatever that was.

This is different to the pre-N (and before that pre-G) stuff. In the latter cases, the IEEE actually published a draft standard, and the manufacturers decided to go ahead and implement it. The "draft N" routers weren't proprietary technologies designed to compete with other "much better than IEEE standards" systems from rival manufacturers, they were actual implementations of a standard everyone was kinda sorta unified around but which hadn't had the official seal of approval for a variety of reasons.

So the context is very different. The ITU wasn't wearing running shoes, but it at least put its walking boots on every time the industry called. The IEEE, on the other hand, seems to be content to prance around in very uncomfortable 3" high heels.

(You were expecting a car analogy?)

Re:Umm... ok, thanks. (1)

PC and Sony Fanboy (1248258) | more than 4 years ago | (#29395507)

So the context is very different. The ITU wasn't wearing running shoes, but it at least put its walking boots on every time the industry called. The IEEE, on the other hand, seems to be content to prance around in very uncomfortable 3" high heels.

I ... don't ... understand.
Perhaps you could draw on the automotive sector for an analogy?

Re:Umm... ok, thanks. (1)

DJRumpy (1345787) | more than 4 years ago | (#29397397)

It would be like the Government trying to define Tire standards, when the Automobile Industry is building hovercrafts...

Re:Umm... ok, thanks. (1)

ceoyoyo (59147) | more than 4 years ago | (#29395021)

Since a bunch of vendors all managed to build compatible products years before the standard was ratified, the standard seems to have been ratified late.

Do my N devices even need a firmware update to be fully compatible? I doubt it. It seems everyone knew what the standard was going to say long before the IEEE did.

Re:Umm... ok, thanks. (1)

jeffstar (134407) | more than 4 years ago | (#29395633)

are they compatible at N speeds or G speeds though?

Re:Umm... ok, thanks. (1)

ceoyoyo (59147) | more than 4 years ago | (#29395693)

They're compatible with each other at N speeds. And G speeds. And B speeds, for that matter.

Re:Umm... ok, thanks. (1)

shentino (1139071) | more than 4 years ago | (#29396463)

In other words, it was a de facto standard before it was an official standard.

Re:Umm... ok, thanks. (2, Insightful)

Anonymous Coward | more than 4 years ago | (#29394705)

These task groups are run by individuals from the same companies that manufacturer the products. They all just didn't agree on one standard whether for technical reasons or corporate politics.

Not completely their fault (5, Informative)

SuperBanana (662181) | more than 4 years ago | (#29394711)

http://www.theregister.co.uk/2007/09/21/802_11n_patent_threat/ [theregister.co.uk]

I'm assuming that if it had been as simple as "take their legos and play elsewhere" (ie replace CSIRO patented technology), they would have done so. The article was written before CSIRO refused to sign the agreements, and before they secretly negotiated what amounted to licensing agreements with a number of top manufacturers.

Interestingly, someone just revised the Wikipedia article by wholesale-deleting any references to patent issues, CSIRO, or their licensing "settlements" [wikipedia.org] .

What is annoying is that I had to give up trying to find information on WHAT the infringements were. Nobody seems to know, or want to say.

Re:Not completely their fault (5, Informative)

X0563511 (793323) | more than 4 years ago | (#29394837)

The talk page... [wikipedia.org]

I encourage other wiki users to look at this diff [wikipedia.org] and help determine if this edit is unfounded or not.

Re:Not completely their fault (1)

Cryptimus (243846) | more than 4 years ago | (#29397093)

The infringement was pretty much wireless networking, which the CSIRO invented and was granted a patent for in the mid-90's.

Basically, a raft of companies have been infringing on that patent for a decade or so and tried to use the US legal system to avoid paying the piper.

Re:Umm... ok, thanks. (0)

Anonymous Coward | more than 4 years ago | (#29394799)

Yeah, who cares if it's a good standard, Let's just get it done as quick as possible. It doesn't matter if it's correct. Clearly the vendors' products should define the standard since they couldn't possibly have cut corners and overlooked problems. I think we'd all like to avoid something akin to WEP all over again.

Maybe you just don't understand what a standard is supposed to accomplish.

Finally (1)

John Pliskin (769478) | more than 4 years ago | (#29394619)

How much changes hardware wise?

Long time... (1)

imamac (1083405) | more than 4 years ago | (#29394621)

Is it really supposed to take that long? I've been using "n" for a long while now.

Re:Long time... (1)

KillerBob (217953) | more than 4 years ago | (#29395295)

The issue being that with different manufacturers pushing their own versions of N, there's no guarantee that all N-branded hardware will work with each other. I have a PCI 802.11n card that has exactly that problem: it doesn't work with the rest of the stuff on my network. It's sure to work when you push it back to 802.11g compatibility, as that standard is well defined, and backwards compatibility is one of the few things that the different factions deciding on N could agree on, but I can't use that system in N mode.

It did take them a long time to decide on a standard, but hopefully having done so, they'll be able to get rid of problems like the one I have with that equipment.

Standard finalized but... (5, Funny)

Anonymous Coward | more than 4 years ago | (#29394627)

now how long will it be before anyone actually supports the standard.

Re:Standard finalized but... (1)

MozeeToby (1163751) | more than 4 years ago | (#29394701)

Ok, in all seriousness (as someone who hasn't been paying attention) how well do existing draft-n devices conform to the standard?

Re:Standard finalized but... (3, Funny)

93 Escort Wagon (326346) | more than 4 years ago | (#29394851)

Ok, in all seriousness (as someone who hasn't been paying attention) how well do existing draft-n devices conform to the standard?

I believe they all do - none of the relevant portions of the draft were changed in the final standard.

Re:Standard finalized but... (2, Informative)

Hungus (585181) | more than 4 years ago | (#29395019)

Note: I originally posted the AC and the reason it is even vaguely humorous is because it will only take minor flash updates to the current chipsets to make them fully compliant, while they are effectively compliant now.

Re:Standard finalized but... (1)

CarpetShark (865376) | more than 4 years ago | (#29394715)

now how long will it be before anyone actually supports the standard.

Don't worry, your car radio will be picking up 802.11n any minute now.

Re:Standard finalized but... (1)

xOneca (1271886) | more than 4 years ago | (#29394925)

Not much until they change the "802.11 draft-N" label to "802.11n standard", I suppose...

Yipee? (5, Insightful)

flipper9 (109877) | more than 4 years ago | (#29394629)

So what? There have been Wireless-N products out now for quite a long time. Who gives a flippin' **** about the official approval of the format? It's not like the manufacturers will go back and update the firmware on the older devices. They'll just put out new products, brand them as "Official Wireless-N", and drop support for older equipment which may or not work as well.

Re:Yipee? (2, Informative)

commodore64_love (1445365) | more than 4 years ago | (#29394825)

You mean the wireless modems don't come with Flash ROM that can be updated by the user? That's whack. The old USR Robotics modems were upgrdeable from 19.2 to 28.8 to 56k as each new standard was released.

Re:Yipee? (0)

Anonymous Coward | more than 4 years ago | (#29394853)

USR Robotics

(-1, Redundant)

Re:Yipee? (1)

commodore64_love (1445365) | more than 4 years ago | (#29394987)

(-1, Only Anal People Nitpick Typos)

Re:Yipee? (0)

Anonymous Coward | more than 4 years ago | (#29395105)

Details Matter!

Re:Yipee? (1)

PC and Sony Fanboy (1248258) | more than 4 years ago | (#29395517)

Details Matter!

So do UIDs!

Re:Yipee? (1)

drinkypoo (153816) | more than 4 years ago | (#29397475)

Those modems also cost four times what a nonupgradable modem would cost, and saved no one any money on that basis. Anyone who saved money going with USR did so on the basis of lack of headaches; they were about the only people back then capable of making a modem that didn't suck. Hayes could almost do it, but they cost almost as much as USR with none of the benefits.

Anyone who spent the big money on a really expensive Draft-N card has a chance to get a firmware update. Anything el cheapo will probably not get one.

Re:Yipee? (1)

Barny (103770) | more than 4 years ago | (#29394883)

Actually I remember early ASUS routers had a guarantee that when the draft was finally ratified that if their devices were not compatible with the final standard they would replace or patch existing units.

Not sure what their current stand is however.

Re:Yipee? (5, Interesting)

jdion (664108) | more than 4 years ago | (#29394901)

So what? There have been Wireless-N products out now for quite a long time. Who gives a flippin' **** about the official approval of the format? It's not like the manufacturers will go back and update the firmware on the older devices. They'll just put out new products, brand them as "Official Wireless-N", and drop support for older equipment which may or not work as well.

One of the requirements to have a pre-n modem branded as 'pre-n' since 2007 is that the firmware would be upgradable to the official N standard when drafted. If anything, this will allow a vendor to release the final firmware upgrade for older devices branded on or around 2007, and get on with life.

We should see at least one more update for older devices.

Re:Yipee? (4, Insightful)

CastrTroy (595695) | more than 4 years ago | (#29395391)

Just because something is upgradeable doesn't mean that the vendor will actually release an upgrade in a timely fashion, or at all.

Blow off some steam, fellas... (5, Interesting)

swanzilla (1458281) | more than 4 years ago | (#29394635)

From the notification:

I expect to extend the celebration of the success , (while we continue work on the other amendments in process ) when we convene in Hawaii two weeks from now.

It only took seven years to get this far...may as well go relax.

I'm very jealous of that time table.

Twitarded (1)

Itninja (937614) | more than 4 years ago | (#29394641)

So the Signal2Noise article seemed pretty concise and accurate. They I see this had this stuffed into the midst of the text:

Editor's note: We'll be celebrating next week with another Tweepstakes giving away a laptop of the FUTURE! Stay tuned!

So they score a double-hit combo of shallowness by simultaneously promoting a laptop giveaway contest AND making a Twitter reference.

Re:Twitarded (1)

dangitman (862676) | more than 4 years ago | (#29395979)

So they score a double-hit combo of shallowness by simultaneously promoting a laptop giveaway contest AND making a Twitter reference.

3. ???
4. Profit!

This process began in 2002. (5, Funny)

Threni (635302) | more than 4 years ago | (#29394649)

LOL - sounds like where I work. What about these new fangled 3.5 inch disks - are they ready to replace low density 5.25 inchers? You can't rush these things, otherwise there'll be too much choice.

Re:This process began in 2002. (1)

commodore64_love (1445365) | more than 4 years ago | (#29394859)

Well the 5 1/4" disks are more reliable. My old Commodore 64 games on 5 1/4 still work, while the higher density 3.5" disks have essentially erased themselves. I say stick with the lower density but higher reliability 5 and a quarter format.

Re:This process began in 2002. (0)

Anonymous Coward | more than 4 years ago | (#29396439)

My old Commodore 64 games on 5 1/4 still work

But can you play them on your iPod?

Re:This process began in 2002. (1)

Barny (103770) | more than 4 years ago | (#29394897)

Whoa slow down tiger, we are still working on getting 720KB disks certified and then we plan to begin on the absolute final ratification of RS-232C

Re:This process began in 2002. (1)

Bill, Shooter of Bul (629286) | more than 4 years ago | (#29396437)

I think the entire move to 5 1/4 is a bit premature, we're already up to 1.2 mb with the 8 inch models.

Standards need to be free. (0)

Anonymous Coward | more than 4 years ago | (#29394655)

Standards need to be free. A standard that is inaccessible is irrelevant.

Re:Standards need to be free. (2, Insightful)

The_Wilschon (782534) | more than 4 years ago | (#29395189)

Agree. For a good example, see this blurb that has appeared in every version of the Scheme language standard:

We intend this report to belong to the entire Scheme community, and so we grant permission to copy it in whole or in part without fee. In particular, we encourage implementors of Scheme to use this report as a starting point for manuals and other documentation, modifying it as necessary.

That's how a standard should be.

Awesome news! (5, Funny)

Tanman (90298) | more than 4 years ago | (#29394687)

Now they can finally optimize Duke Nukem Forever's network code to utilize this new standard at LAN parties!

Re:Awesome news! (1)

game kid (805301) | more than 4 years ago | (#29394719)

Not until they approve that 100 Mbps Ethernet I've been waiting on!

In Other News (1)

sexconker (1179573) | more than 4 years ago | (#29394751)

Hell has frozen over.

Another standard approved today (4, Funny)

NetRanger (5584) | more than 4 years ago | (#29394781)

In related news, the same body has approved a special security packet encapsulator consisting of pigmented lipids that bond the rolled packet together, with a special imprinted signature to establish non-deniability of the transmitter and ensure the packet has not been intercepted and examined by third parties.

The standard was submitted for approval in '02.

That is, 0002.

Re:Another standard approved today (1)

Rasta_the_far_Ian (872140) | more than 4 years ago | (#29395383)

In related news, the same body has approved a special security packet encapsulator consisting of pigmented lipids that bond the rolled packet together, with a special imprinted signature to establish non-deniability of the transmitter and ensure the packet has not been intercepted and examined by third parties. The standard was submitted for approval in '02. That is, 0002.

Amazing! This was modded as informative!

The writer of this comment was clearly referring to wax seals - i.e., like those that were put on the back of envelopes in ancient times.

Should have been modded funny ..

Re:Another standard approved today (3, Funny)

Antique Geekmeister (740220) | more than 4 years ago | (#29395585)

He was waxing eloquent.

Re:Another standard approved today (1)

Bananenrepublik (49759) | more than 4 years ago | (#29396971)

Heads up everybody, these packet encapsulators, previously known as Envelope Attribution Logos shall henceforth be known as Standardized Envelope Attribution Logos, colloquially seals.

Re:Another standard approved today (1)

Dragonslicer (991472) | more than 4 years ago | (#29397355)

In related news, the same body has approved a special security packet encapsulator consisting of pigmented lipids that bond the rolled packet together, with a special imprinted signature to establish non-deniability of the transmitter and ensure the packet has not been intercepted and examined by third parties.

But does it support the Evil Bit?

glad i waited (2, Interesting)

satsuke (263225) | more than 4 years ago | (#29394815)

call me risk adverse .. but i was actually waiting for the final publication and n devices.

it's only recently that the n devices were cost competitive with the g devices.

now to push cisco/linksys to release an n equivelent to the wrt54gl device

Re:glad i waited (2, Informative)

debile (812761) | more than 4 years ago | (#29395049)

WRT160NL with a bonus USB port for your external hard drive (who said cheap media server?)

http://gizmodo.com/5301321/linksys-wrt160nl-is-fully-linux-powered-80211n-and-acts-as-media-server [gizmodo.com]

Re:glad i waited (1)

Gorphrim (11654) | more than 4 years ago | (#29395793)

if only the WRT160NL had gigabit for wired ports

Re:glad i waited (0)

Anonymous Coward | more than 4 years ago | (#29398077)

Risk AVERSE.

AWESOME! (0)

Anonymous Coward | more than 4 years ago | (#29394831)

Now I can play Duke Nukem Forever on the wireless network. . .

Yes, it's compatible with Draft N (2, Informative)

owlstead (636356) | more than 4 years ago | (#29394857)

For those who haven't read until the end of the boring article, let me just put in the last sentence:

"According to the Alliance, users can expect future Wi-Fi products to be fully compatible with todayâ(TM)s products."

Well, that's at least a relieve. Hopefully they did not have to drop a lot of features to get that result. The other good thing is having an official test suite, so products don't have to be tested 1:N where N is all the other products out there. Although I presume there are also Draft N test suites available already.

IEEE Stinks (1)

clampolo (1159617) | more than 4 years ago | (#29394861)

While I'm glad they came up with this new standard, I wish they wouldn't use the IEEE for this stuff. Now if someone wants to look at the standard they will be charged an outrageous price like $250. $250 for something that will be at most 50 pages, in other words they charge $5 per page.

Re:IEEE Stinks (1)

androvsky (974733) | more than 4 years ago | (#29394941)

While I'm glad they came up with this new standard, I wish they wouldn't use the IEEE for this stuff. Now if someone wants to look at the standard they will be charged an outrageous price like $250. $250 for something that will be at most 50 pages, in other words they charge $5 per page.

Well, to be fair, it took them about 2 weeks to write each page.

Re:IEEE Stinks (5, Informative)

Anonymous Coward | more than 4 years ago | (#29395055)

All IEEE 802 standards are available for free:

                http://standards.ieee.org/getieee802/
                http://standards.ieee.org/getieee802/portfolio.html

Besides, what's wrong with them charging for it? Even a non-profit has bills to pay.

(And 802.11-2007 is 1184 pages.)

Re:IEEE Stinks (1)

owlstead (636356) | more than 4 years ago | (#29398325)

It's a major pain if the standard gets charged for, I'll name a few reasons:
- Difficult/expensive to get at for individuals (want to do anything as a not-well paid worker in India? Well, fork over 50 euro for the standard first)
- Hard to tell which standards you really need. I've forked over 50 euro just to get a few pages (20 pages of meta-information and 3 pages of actual info sometimes) with information readily found on the internet.
- Having to fork over the same amount for each *update* of the standard. Never mind that they don't even make clear which changes those are and if they are relevant to you.
- A freaking nuisance to manage them. Who to make the standard available to? Can you give it to an outside consultancy firm? Can employees take them home? What happens if they get published on the internet? We now hire a company to get us updates for ISO standards, costs us thousands of euro's each year.
- DRM, mostly in Adobe, illegal to copy things from a freakin' standard
- Not readily available when you need them. I cannot work for my company from here since I cannot even look in the darn standards.
- A large amount of the money goes into administration and overhead anyway.
And that's just out of the top of my head.

Most of the time the industry involved wants to be involved with a standard. If they are not involved they tend to miss the first few years of development. Let the companies involved spend some money so they've get the competitive edge. That should be reward enough in itself.

Re:IEEE Stinks (1)

jeffstar (134407) | more than 4 years ago | (#29395645)

if you somehow managed to retain an account at your educational institution you may find that they have a subscription to the IEEE and all you have to do is ssh tunnel through your alma matter!

ok, /. won't let me post. does it take ages for everyone else to go from preview to submit?

ok, still waiting to use this resource... cmdrtaco you guys should have this sorted out by now it's only been like ... 13 years?

WHAT! ALREADY! (2, Funny)

clinko (232501) | more than 4 years ago | (#29394881)

I'm still deciding if I should go X2 or K56Flex and now you drop this on me!?

Speaking as a member of the IEEE (3, Interesting)

loose electron (699583) | more than 4 years ago | (#29394969)

Folks - sad to say, but there is little bit of a disconnect between the IEEE and industry.

The organization is largely dominated by academics, and students. Industry participation is a bit mixed, to say the least.

The Special Interest Groups (SIG) are more effective at getting things done (WiFI alliance, WiMax, ZigBee, Bluetooth, etc)

What happens and gets adopted inside the SIG generally is what happens in the real world. The blessing of the IEEE standard is generally after the fact.
If the SIG blesses it, HW and SW move ahead, and you get a timely product development where everyone's stuff plugs and plays together.

Even inside a SIG, the politics and bickering is a tug of war, but the members are motivated to get it done because their companies want to ship products.

As for the IEEE, due to the academic orientation, there is a lack of impetus to produce standards quickly, and practical information is often not welcome in IEEE journal publications. As a reviewer for 2 IEEE journals, I want the practical, but my reviews go against 3-5 others, and its a consensus decision. Often other reviewers want the math analysis pretty, and don't care much that the publication has nothing for real world application or validity.

Go figure -

Oh, and yeah, I truly am a member of the IEEE, Senior Grade, Chapter chair for several societies, and journal reviewer as well. However my efforts are generally swimming against the flow. Because of that, when I publish, I do it in the electronics trade magazines where real world issues are a lot more welcome.

Re:Speaking as a member of the IEEE (1)

ceoyoyo (59147) | more than 4 years ago | (#29395041)

Hey, it probably saves you time. The last paper I had accepted to an IEEE journal was literally under review for two years. TMI took six months to decide NOT to review it.

Re:Speaking as a member of the IEEE (2, Insightful)

RiotingPacifist (1228016) | more than 4 years ago | (#29395203)

Whats the rush? people can put out products on an interoperable standard they agree on through wifi allainace, WiMax or whatever. When IEEE standardises something I want that to mean, the shit run for sure, I would rather wait let vendors implement draft-n for 2 years than have another FUBAR in the standard like WEP in 802.11.

Re:Speaking as a member of the IEEE (1, Interesting)

Anonymous Coward | more than 4 years ago | (#29396111)

The delay is not really due to academics. Standard making is a bit of a tug-of-war between various industry players, or specifically between "IP owners" and device makers. The goal of IP owners is to get their patented technology in the standard. If they succeed, and in particular if they can make their technology a mandatory part of the standard, then they can extract big royalties from the device manufacturers. And, no, I am not speaking about CSIRO here.

That actually played a big role in the beginning of the IEEE 802.11n standardization. IP shops aggregated around two big camps, led by Intel and Broadcom respectively. But then, Intel and Broadcom, who are fierce competitors in the market, realized that they were being taken for a ride, and switched strategy. They got together, and with other big manufacturers like Atheros or Marvell, defined a subset of the various proposals that they could quickly implement and that required minimal licensing. This is very much what ended up as 802.11n.

Of course, IP owners cried bloody murder, and attempted to use the IEEE voting procedures to delay the standard, hoping to get their pound of flesh in the final draft. They were helped by telcos, notably AT&T. You see, telcos have payed big money for wireless licenses, to enable 3G and then LTE and 4G. At some degree, Wi-Fi competes with that. If 11n provides 100Mbps or 200 Mbps, the 3G network does not look so good. Guess who filed more than 2000 comments to delay the standard? AT&T!

But as soon as "interim" products were on the market, and were interoperating, the delaying game became worthless. Sure, you can still go in the committee and try to make provision for your preferred patented improvement, but it cannot break the established base of millions of products, so it can at best be optional. Checkmate.

Excellent... (1)

mysidia (191772) | more than 4 years ago | (#29395085)

Now, can I have my Atari 2700 now? And get the Cairo OS installed on my PC with an object-oriented file system.

Need this ASAP so I can finally get to playing Duke nukem forever...

its about time.... (1)

dogfolife69 (1005455) | more than 4 years ago | (#29395099)

its about time.... there is to much confusion with everyone having N, N+ and all the other versions... now there can be one version that is standardized

IPV6? (4, Interesting)

sadler121 (735320) | more than 4 years ago | (#29395125)

Are there any non-apple routers that support IPv6 out of the box? Upgrading from 802.11b/g/a to n would be the perfect opportunity to make sure the consumer router market is ready for IPv6.

Re:IPV6? (0)

Anonymous Coward | more than 4 years ago | (#29395215)

Are there any non-apple routers that support IPv6 out of the box?

Yes. That's a dumb question.

Upgrading from 802.11b/g/a to n would be the perfect opportunity to make sure the consumer router market is ready for IPv6.

Average consumer doesn't care about a/b/g/n. Many of them are probably running draft-N and again, don't care. Others will happily continue using g or even b, again, without caring.

Re:IPV6? (1)

Hymer (856453) | more than 4 years ago | (#29396531)

"Are there any non-apple routers that support IPv6 out of the box?"
If you need IPv6 routers why don't you just buy them from Apple ?

Awesome! (0, Redundant)

duffbeer703 (177751) | more than 4 years ago | (#29395133)

Nice, now when's Duke Nukem Forever going to be released?

Good news (4, Funny)

stokessd (89903) | more than 4 years ago | (#29395153)

I just went down and told my router, it blinked it's little lights in approval.

Sheldon

This FP 7or GNAA (-1, Troll)

Anonymous Coward | more than 4 years ago | (#29395155)

they are Com3 ones in software

But the question is.. (2, Interesting)

EmagGeek (574360) | more than 4 years ago | (#29395275)

.. did they make a change at the last minute that is small, but nevertheless renders all of the current "pre-n" hardware and software obsolete?

Crowded spectrum (2, Insightful)

xmff (1489321) | more than 4 years ago | (#29395291)

Hopefully the 5GHz band does not become clogged up now that all the new shiny 11n gear hits the market :-/

Many 802.11n devices already jam the 2.4GHz range and render near 11g devices unusable with their multi channel stuff...

Re:Crowded spectrum (1)

Guppy (12314) | more than 4 years ago | (#29395647)

Hopefully the 5GHz band does not become clogged up now that all the new shiny 11n gear hits the market :-/

Isn't a lot of the cheaper 802.11n gear 2.4GHz only? I seemed to recall only certain 11n units with "dual band" operation models will offer 5GHz.

Re:Crowded spectrum (1)

teg (97890) | more than 4 years ago | (#29396543)

Isn't a lot of the cheaper 802.11n gear 2.4GHz only? I seemed to recall only certain 11n units with "dual band" operation models will offer 5GHz.

Many of them will let you choose 2.4 GHz or 5 GHz. If you use 5 GHz, no b/g for you... Personally, I hope dual band doesn't catch on as I love mine. 2.4 GHz is very, very crowded here... while I'm the only one on 5 GHz. 10x the speed.

Re:Crowded spectrum (1)

Piranhaa (672441) | more than 4 years ago | (#29396477)

At least the 5GHz channels are totally isolated from one another so the chances that EACH person in your neighbourhood is saturating EVERY channel simultaneously is pretty slim. The same cannot be said about the wireless 2.4GHz channels 1-12.

Breaking Products (0, Flamebait)

Nom du Keyboard (633989) | more than 4 years ago | (#29395417)

And just how many pre-standard "n" products will this now break?

Re:Breaking Products (4, Insightful)

owlstead (636356) | more than 4 years ago | (#29398359)

FROM THE FUCKING ARTICLE AND A POST ABOVE.

For those who haven't read until the end of the boring article, let me just put in the last sentence:

"According to the Alliance, users can expect future Wi-Fi products to be fully compatible with todays products."

Moderators, wake up and read the actual article before modding anything up.

Nom du Keyboard indeed. Lire le Screen?

DD-WRT? (1)

XB-70 (812342) | more than 4 years ago | (#29395747)

Where and when do we find DD-WRT 802.11N and for what router?

Re:DD-WRT? (0)

Anonymous Coward | more than 4 years ago | (#29396705)

Um, what?

I'm happily running dd-wrt on a couple of netgear 802.11n-draft boxes now. What do you think would need changed to make it work?

Hooray.. (1)

Skythe (921438) | more than 4 years ago | (#29396015)

I'll finally consider purchasing some that's not based on a draft standard.

bonus news! (1)

ILuvRamen (1026668) | more than 4 years ago | (#29396261)

from TFA: "In a rare double whammy decision, they've also finished and released Duke Nukem forever, which fully supports Wireless-N." Don't think too hard about how much sense that makes lol.
Load More Comments
Slashdot Login

Need an Account?

Forgot your password?
or Connect with...

Don't worry, we never post anything without your permission.

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>