There are several things that I did not see in the article. It seems to imply that Voip handsets and Voip servers share the same infrastructure as workstations. This is already recipe for trouble as even a normal business use could seriously affect the phones.
Today, these networks really need to be separate, either physically or through VLANs, as a lot of network architectures cannot readily address both needs: throughput for business application or latency for Voip.
The only application of NAC that I can see useful today is if somebody mistakenly (or not) connects a PC to the Voip network. Using NAC (802.1x actually in this case) would make sure that this device cannot connect at all and that the disruption is limited to that port.
Latest software headlines from Network World:
Kernel developers, Wall Street to come together
Zoho launches e-mail app with offline, mobile access
|
Does Verizon's Voyager stack up to the iPhone? |
|
|
5 IT skills that won't boost your salary
[1,407]
Women 4 times more likely than men to cough up personal info
[589]
Japan's 10 funniest tech-related commercials [Videos]
[407]
Throwing away a promo CD is "unauthorized distribution"?
[1,265]
Adults too quick to dismiss educational video games
[682]
Attack of the iPhone clones [Slideshow]
[578]
10 things IT needs to know about AJAX
[1,258]
This Year's 25 Geekiest 25th Anniversaries [Slideshow]
[409]
|
|