Perhaps it’s just me and my laser focus (pun intended) but there seems to be a never-ending supply of reasons to deploy Carrier Ethernet, led by the most obvious of all the reasons: there’s just more IP traffic moving around all over the world.

Content is like politics; it’s global in its significance but bound by its local roots (or in the case of networks, routes).

As an example of a global application that becomes local, Verizon this week said it would be expanding its Partner Port Program to content companies worldwide giving them “the option to connect directly with Verizon’s global IP network at various key sites around the world.” That network, Verizon said, touches more than 150 countries.

The avowed goal is to get content providers hooked into Verizon’s hard-wired links. If achieved, this would create an incredible spike in traffic caused by a massive group of content innovators jumping onto Verizon’s IP networks and delivering their content globally.

While the program addresses the holistic whole—the Verizon global IP network—it does not address the end points where all this content will converge on local networks. Verizon said it “encourages direct connections between the content servers and the Verizon network … to avoid long, multicarrier hops around the various networks from servers to customers.”

Great. Now I would encourage the use of Carrier Ethernet loops within the regional and metro areas to move that traffic efficiently and inexpensively to its end destination.

Pushing that IP traffic onto the global network is wonderful; jumping off that global network onto the local loop is problematic. Carrier Ethernet fills the gap, allowing service providers to continue offering the same quality of service, efficiency and, most importantly, bandwidth on that local loop Carrier Ethernet. This is especially true when you get to the final part of the Verizon proposal.

“We’ll offer our customers access to up to 3.4 million FiOS Internet customers who are among the 9.2 million broadband customers Verizon services and 91.2 million wireless customers all at a time when quality has become a watchword and high definition video streaming has mushroomed,” the company said in a news release.

How exactly do you do that? How about starting with a metro loop and proceeding to put some Ethernet across it?

Perhaps it’s just me and my laser focus (pun intended) but there seems to be a never-ending supply of reasons to deploy Carrier Ethernet, led by the most obvious of all the reasons: there’s just more IP traffic moving around all over the world.

Content is like politics; it’s global in its significance but bound by its local roots (or in the case of networks, routes).

As an example of a global application that becomes local, Verizon this week said it would be expanding its Partner Port Program to content companies worldwide giving them “the option to connect directly with Verizon’s global IP network at various key sites around the world.” That network, Verizon said, touches more than 150 countries.

The avowed goal is to get content providers hooked into Verizon’s hard-wired links. If achieved, this would create an incredible spike in traffic caused by a massive group of content innovators jumping onto Verizon’s IP networks and delivering their content globally.

While the program addresses the holistic whole—the Verizon global IP network—it does not address the end points where all this content will converge on local networks. Verizon said it “encourages direct connections between the content servers and the Verizon network … to avoid long, multicarrier hops around the various networks from servers to customers.”

Great. Now I would encourage the use of Carrier Ethernet loops within the regional and metro areas to move that traffic efficiently and inexpensively to its end destination.

Pushing that IP traffic onto the global network is wonderful; jumping off that global network onto the local loop is problematic. Carrier Ethernet fills the gap, allowing service providers to continue offering the same quality of service, efficiency and, most importantly, bandwidth on that local loop Carrier Ethernet. This is especially true when you get to the final part of the Verizon proposal.

“We’ll offer our customers access to up to 3.4 million FiOS Internet customers who are among the 9.2 million broadband customers Verizon services and 91.2 million wireless customers all at a time when quality has become a watchword and high definition video streaming has mushroomed,” the company said in a news release.

How exactly do you do that? How about starting with a metro loop and proceeding to put some Ethernet across it?