Slashdot Mirror


Historic IEEE 802 Group Looks Back and Forward

An anonymous reader writes "The IEEE MAN/LAN Standards Committee — better known as the people who brought us Ethernet, Wi-Fi, and Bluetooth — is celebrating its 30th anniversary next week. This article has interviews with the original committee chairman and other veteran members, and reveals some of the inside situation. It also looks at some of the upcoming 802.x standards including one that sends data by modulating visible light."

17 of 45 comments (clear)

  1. IEEE Bluetooth? by Anonymous Coward · · Score: 3, Insightful

    IEEE did not develop the Bluetooth standard

    1. Re:IEEE Bluetooth? by east+coast · · Score: 4, Insightful

      The IEEE didn't develop any of the mentioned technologies. They just standardized them.

      --
      Dedicated Cthulhu Cultist since 4523 BC.
  2. Upcoming? by silverdr · · Score: 2, Insightful

    Don't we use visible light in optic fibre for some time now? ;-)

    --
    Now, mod me down freely. My karma can't get any worse...
    1. Re:Upcoming? by fan777 · · Score: 3, Funny

      I think the summary is talking about lighthouses.

    2. Re:Upcoming? by peragrin · · Score: 2, Funny

      true but this is for wireless light transmission. You see IEEE has been watching old sci fi series and thought they needed more blinking lights in the real future. So each one of those blinky lights is in reality an active data connection for some device.

      --
      i thought once I was found, but it was only a dream.
  3. MAN/LAN by zlel · · Score: 2, Interesting

    This is really nostalgic I almost forgot what MAN meant!

  4. Re:Ethernet was fine by TheLink · · Score: 3, Interesting

    In case people don't get it, with the current WiFi standards you cannot have an easy way for a Cafe/Hotel/Conference to provide encrypted wireless connections to guests in a way where they cannot snoop on each other's connections. if you use preshared key users can decrypt each other's traffic. If you use username and password, it's far more inconvenient for the user and the service provider.

    --
  5. Re:Ethernet was fine by Bearhouse · · Score: 2

    Agree. Wireless security was really broken from the start, and has got only slightly better, slowly...
    Interoperability between devices from different vendors is not so bad now.
    On the other hand, if you travel around the world you can actually enjoy the convenience of wirelessly connecting to the internet almost anywhere.
    (The other day I did a free conf call, via Wifi in some airport terminal, with three people in three different continents, using my bluetooth headset on a cheap laptop...could you imagine that 20 years ago?)
    So, better an imperfect solution that works, than no solution. Well done IEEE!

  6. Also coming up this year... by dtmos · · Score: 3, Informative

    ... is the 20th Anniversary of the 802.11 Working Group itself. The Working Group held its first meeting September 10-14, 1990, in Oshawa, Ontario, Canada.

    1. Re:Also coming up this year... by Mikkeles · · Score: 2, Funny

      So, in this case, one can actually Blame Canada, eh?

      --
      Great minds think alike; fools seldom differ.
  7. Maybe they can change IEEE's pro-swpat stance by H4x0r+Jim+Duggan · · Score: 2, Interesting

    In the Bilski case, IEEE filed a brief pushing *for* software patents. Maybe specific groups in IEEE, like the 802 group, should push for a change in this position. Having the whole wifi industry paying a tax to CSIRO for a wifi patent must make this group a little more clued in about the harm caused.

  8. Get the configuration right by thoughtspace · · Score: 4, Interesting

    I am staggered how complicated it is to setup WiFi a lay-person. Far too much jargon (SSID, WPA, WPA2, WEP, TKIP, AES+TKIP, channels ...), and stupid ideas like multiple WEP keys. Let alone connecting via ethernet, change the subnet, browse to an IP address, etc etc etc just to get it going. What an awful decade of design.

    Look ... from day 1 we just wanted a secret password.

    Public networks are different and need to be publicly identified - don't shoe-horn it into the same user interface.

    Start thinking like a user and stop this engineers crap.

  9. Re:Ethernet was fine by TheRaven64 · · Score: 4, Informative

    In case people don't get it, with the current wired Ethernet standards, you cannot have an easy way for a Cafe/Hotel/Conference to provide encrypted wired connections to guests in a way where they cannot snoop on each other's connections either. If you want security, you should be using end-to-end encryption.

    --
    I am TheRaven on Soylent News
  10. Re:So let me just get this straight by Tomsk70 · · Score: 3, Informative

    Man, how ungratefull can you get. Why dont you go out and develop you own "standard" wireless protocol and see how long it takes you!

    Err...no, that's what they were supposed to be doing. Or do you think an eight-year lead time is acceptable? And your answer is stupid anyway - you don't say 'well write your own OS' when someone complains about Windows.

    The only hardware I've ever had an auto-negotiate issue with is Cisco switches, on many occasions with completely different clients over many years. Everyone else seems to play nice, but Cisco was well known for implementing their own "standard" early.

    Which tells me exactly how much networking hardware you've actually worked with, so let me fill you in - ISCSI not working? Set all adaptors to 1000/Full. Backup Exec not working? Set all adaptors to 1000/Full. Network generally slow? Set all adaptors to 1000/Full. I could list around 20 more off the top of my head...and then there's stuff such as - Vista network auto-tuning buggering up your system? That's because there's *no standard*.

    So yes, after wasting my time for *years* with non-compatible Wireless, Bluetooth and Ethernet 'standards', I think I've earnt the right to be ungrateful, thank you very much :-)

  11. Wonderful... by elFarto+the+2nd · · Score: 2, Insightful

    ...prehaps they could get around to increasing MTU from 1500.

  12. Ah, the ol' 802.3 gang... by BubbaDave · · Score: 3, Insightful

    Cool. I've worked with Paul Nikolich (when ADC broadband bought bought the CMTS company he was at), and have run into some of this cast of characters during the 802.3ah Ethernet in the First Mile meetings. Interesting folks.

    I think it was Geoff (I could be wrong, this was a while ago) that said we would not need high-speed uplink from the home because 'there just isn't that much relevant content out there'. That was a pretty good chuckler.

    I'm sure Michael Coden of Codenoll feels snubbed, he always claimed to me he was the co-inventor of ethernet.Never believed him.
    He did pioneer one interesting product- a distributed ethernet switch that would operate over a unidirectional fiber ring- worked pretty well after I fixed the gaping hole in his protocol.

    Dave

  13. Small correction by dtmos · · Score: 2, Insightful

    The official name of 802 is the IEEE 802 "LAN/MAN Standards Committee," not the other way around.