Aw Dan - less volume in wires? Well for a number of applications yes, especially in Data Center and Enterprise. However, i can think of certain white wires that we all seem to be looking for at meetings to charge our phones and other electronic gadgets. So next week, when i hold one up at you and smile... remember this blog :)
While i would love to see Ethernet target the consumer application space, that wasn't the point of this blog. As i noted Ethernet technology is being leveraged in the automotive environment, and the port count it will bring is significant. I personally believe that too many people are equating Ethernet to the RJ45 interconnect and 100m UTP. Perhaps you are doing this with your square peg round hole analogy? There are numerous other signaling technologies that have been developed as part of Ethernet that in theory could be applied to other application spaces. We need to look for those opportunities Consumer applications are just an easy example to point to and say "Where's my Ethernet?"
Yes, I have to agree with Dan. At first, I thought people were questioning whether Ethernet would survive. Of course, it will. No need to reiterate the type of equipment that depends on Ethernet and would not do nearly as well with wireless.
But if the intent of the article was to make Ethernet somehow a prime choice for handheld gadgets, which is what everyone is talking about when they mention huge volumes, then I have to question why? Isn't it a bit like trying to fit a square peg in a round hole?
From the point of view of someone who doesn't have a dog in this race, I would say that one should choose the correct tool for each job.
I think the big challenge is to recognize that Ethernet volumes are not the only indicator of Ethernet success any more.
The volume of data center connections, while substantially smaller than PC connections, is imperative to bringing PC/tablet/phone connectivity to fruition.
Visualize Ethernet as the pillar of a bridge that connects everything together. Having a lot of pillars is great. Having pillars that can hold up a huge bridge that connects billions of users is also important. 10G Ethernet will be doing that, and soon it will be 40G and rapidly 100G.
Connectivity via wires is becoming a smaller piece of the volume, but those wires will do what must be done, hold up the massive bridge that connects us all together.
John, I agree with you.
The "old" days of IEEE 802.x focusing on 10x speed jumps might help a few, but not the billions.
1) How about a 10x power reduction focus; wired, wireless, whatever.
2) Or a 10x technology driven cost reduction focus (1 or 2 pair Gig on twisted pair is an ok goal...but Ethernet needs a 10x focus.
3) If the above mean Ethernet needs to revisit and fill in the present 10x speeds, go for it.
Agree, John, that a smaller connector option for Ethernet might give it some additional roles. Don't think the IEEE should make such an upate a non-starter. After all, other interface standards, like USB, have done this sort of thing, no? Although for small handheld devices, seems to me the attraction of wireless would always be hard to beat.
I guess my point is that the future of Ethernet is hardly in jeopardy either way. The faster speeds are going to be in demand not significantly because anyone needs 100G Ethernet to their PC or tablet anytime real soon, but because the major carriers are leaving isochronous legacy protocols behind. SONET being the most recent of these. And these guys do need faster speeds real soon. So do the ISPs. The IEEE hardly finishes one new Ethernet speed update before it gets deployed in the real world. These applications are certainly not migrating to 802.11, is my point.
Speaking as the author, Bert :), the actual intended point of the story is that there are a wealth of technologies developed in association and in support of Ethernet that have yet to be fully exploited for other markets. You want my personal opinion on this - the RJ45 connector has been as much a hindrance as a benefit to Ethernet. In my previous life whenever i asked about a new smaller form factor Ethernet connector - the RJ45 and Ethernet's 100m would come up as reasons as why nothing else should be done. I think this was extremely short-sighted, and probably played a very significant role in the rise of other technologies. Seriously, how many of us have these mobile devices where we may have a simple 1m cable? I would say that is a pretty big market!
The Ethernet community is awesome at developing awesome technologies - now we need people to step up and apply them!
Yes, but only "sort of."
We only call Ethernet those LAN technologies that use the Ethernet frame format. And even more to the point, the original "carrier sense and collision detection" protocol has been obsolete for many years now, as the actual protocol used throughout any LAN. (If it's used at all, it only a lowest common denominator default protocol for *one* device talking to *one* switch port. Hardly its intended mission in life!)
The point made in this article was that with all the hype going to handheld toys, which use WiFi instead of Ethernet as their link to the Internet, isn't Ethernet becoming passe?
Of course not. That's a little bit like asking whether the concrete driveway up to your front door renders freeways obsolete. Sort of a silly point, isn't it? One has nothing to do with the other. Ethernet does a lot more than just attach an end device to this magic "cloud." Ethernet is also ubiquitous *in* that cloud. That's the point.
And as the cloud keeps gaining in speed, about an order of magnitude every 6 or 7 years, you're clearly going to need faster and faster Ethernet as time marches on.
As Bob Metcalfe pointed out in an interview last year, we tend to call the next generation of all networking technologies Ethernet even though they may be very different from the old collision sense multiple access technology he defined.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.