Slashdot Mirror
IEEE Seeks Data On Ethernet Bandwidth Needs
itwbennett writes "The IEEE has formed a group to assess demand for a faster form of Ethernet, taking the first step toward what could become a Terabit Ethernet standard. 'We all contacted people privately' around 2005 to gauge the need for a faster specification, said John D'Ambrosia, chairman of the new ad hoc group. 'We only got, like, seven data points.' Disagreement about speeds complicated the process of developing the current standard, called 802.3ab. Though carriers and aggregation switch vendors agreed the IEEE should pursue a 100Gbps speed, server vendors said they wouldn't need adapters that fast until years later. They wanted a 40Gbps standard, and it emerged later that there was also some demand for 40Gbps among switch makers, D'Ambrosia said. 'I don't want to get blindsided by not understanding bandwidth trends again.'"
Much of the talk is about operator and hub level, not end-user. As a result, terabit ethernet makes sense with numbers you present - provided specific hub serves enough clients.
Essentially it's a case of making internal ISP networks simpler to build.
depends what you're using it for, doesn't it?
gig-e is still slow. sure it might be fine for a single desktop port, but...
hook it up to a SAN, and before you know it you're running into the limits of a few gig-e ports bound into an etherchannel.
storage requirements are going to continue to grow. HD video / audio is going to continue to become more widespread. if you're dealing with limited numbers of cables to carry data for large (and increasing) numbers of users, there's no escaping the need for more bandwidth.
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
Running the cable is the part that requires the effort, unfortunately. There are things that help(ie. if underground, lay a larger diameter conduit than you think you'll need; because you will end up needing it. Leave a fish line so that you can pull the next bundle through, etc.); but for anything longer than an in-room patch, the cost of getting more cable run can go up quickly. In building, you need to run the stuff so as not to damage any fire barriers(and ideally avoid having to tear up any walls...) Underground, there are the joys of trenching or pulling recalcitrant cables through existing pipes. If running on utility poles, the proximity to high voltage means you'll probably need linesmen, even though fiber is electrically harmless.
When you can, you 'plan for expandability' by pulling as many strands of fiber in a single bundle as they'll let you get away with. The cost of each strand is comparatively small. The cost of pulling a bundle, whether it be two strands or 128 strands, is comparatively huge. You then just leave the ones you don't immediately need dark until you do need them.
For very nasty runs(undersea cables, backbones of large landmasses, etc.) I'm told that there is some emphasis on designing new transmitter/receiver systems that can squeeze more bandwidth out of the strands you already have(when the alternative is laying another fiber bundle across the Pacific Ocean almost arbitrarily expensive endpoint hardware starts to look like a solid plan...) Such matters are well beyond my personal experience, though.