Light Reading Mobile – Telecom News, Analysis, Events, and Research
Series Column  

Intro: Cloud Intelligent Networks

February 05, 2012 |

There's nothing new about IPv6. Network equipment providers and service providers have been preparing to migrate from IPv4 for years. But now that IPv4 address depletion is a reality, enterprises and service providers have to address how they'll migrate themselves and what they can do for their customers. (See LR Live: IPv6 Transition Decisions Loom).

That migration will include supporting both IPv4 and IPv6 traffic simultaneously and, in some cases, using carrier-grade network address translation (NAT) as a migration strategy. As more enterprises move to cloud services, they need to be confident that the services providers they are trusting with their most valuable business have a real plan for their networks.

We've covered several aspects of the move to IPv6 and the concerns involved over the past few months:

Cisco, like other vendors, is looking for validation that it has several of the pieces needed by service providers to proclaim confidently that they have a plan in place for the future of their IP infrastructure. "While the tests performed on the Cisco equipment were done in a lab environment, the results illustrated that performance metrics of commercially available products already support some of the most challenging IPv4/IPv6 interworking scenarios," says Heavy Reading senior analyst Jim Hodges.

Here are the sections for this part of the Cisco Cloud Mega-test, where the emphasis is squarely on showing operators how the network core and data center could scale while moving to IPv6:

Next Page: Stateful NAT64 Performance

Back to the Cisco Test Main Page


Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Network Computing encourages readers to engage in spirited, healthy debate, including taking us to task. However, Network Computing moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Network Computing further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 
Related Content
Most Popular
Read
White Papers SPONSORED CONTENT
Featured
Resource Library SPONSORED CONTENT