I have to agree...this does sound a lot like marketing...but its definitely intriguing at the same time.
I'm especially interested in the COS/QOS capabilities...mapping our QOS queues to carriers can be problematic...having a uniform COS structure across all connections would be great...and I certainly wouldn't complain about a 10-100 Mb/s connection to every one of our sites either...
mark.
Latest LAN/WAN headlines from Network World:
Online ad targeting progresses in UK, lags in US
Streamcore bolsters WAN visibility features
How CIOs can align themselves with the business
|
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]
|
|
We Are Using Ethernet Everywhere in the US
We have recently deployed WAN Ethernet for connectivity to Verizon's PIP (MPLS) service. Each site receives a DS-3 that Verizon converts to Ethernet for us. So our handoff is Ethernet; all protocol conversion is done by Verizon. This gives us scalability, simplicity, and lower cost (Ethernet interfaces are MUCH cheaper than T-1/3/SONET). The backbone is Layer-3 MPLS (2547bis) so we get the benefits of any-to-any and QoS.
The Ethernet service has been stable, although provisioning is slow. I would strongly recommend it to customers that can wait 60-days for service delivery.