Show 36 – IPv6 Ready

Guests

Tom Hollingsworth http://networkingnerd.wordpress.com | Twitter: @NetworkingNerd

John McManus http://etherealmind.com/author/mcmanusj/ | Twitter: @_johnmcmanus_

Greg Ferro http://etherealmind.com| Twitter @etherealmind

Topic 1 – iPad 2

Apparently none of us are going to buy one, because we’ve already got one.

Topic 2 – What is Cloud Computing

Although we tire of talking about Cloud Computing, it’s seem that there is more to say. Talking about what building you own cloud is about including accounting/budgeting problems and server/networking operation problems. We also talk about the lack of bandwidth and a wide range of other topics.

Topic 3 – Catalyst 6500 Services module strategy

What’s the future of Cisco Cat6500 services modules strategy since the current modules are obviously not scaling to the future. Is the Nexus 7000 suitable for use in the Campus ?

Somehow we deviated into a discussion about the relevance of the ASR 1K/9K routers and their fit into a network design.

Topic 4 – IPv6 Ready program

A look at the http://www.ipv6ready.org/ program which led into a discussion around how to deploy IPv6 into an enterprise (hint: it’s doesn’t involve deploying IPv6).

Topic 5 Tech Field Day Wireless

I’ll be in San Jose for the http://gestaltit.com/field-day/2011-wireless/ Gestalt IT Tech Field Day. Tom Hollngswoth and Mat Norwood (regular guests on the show) are also

 

Feedback

Follow the Packet Pushers on Twitter (@packetpushers | Greg @etherealmind | Tom Hollingsworth), and send your queries & comments about the show to [email protected].  We want to hear from you!

Subscribe in iTunes and RSS

You can subscribe to Packet Pushers in iTunes by clicking on the logo here.

Media Player and MP3 Download

You can subscribe to the RSS feed or head over to the Packet Pushers website to download the MP3 file directly from the blog post for that episode.

 

Greg Ferro
Greg Ferro is a Network Engineer/Architect, mostly focussed on Data Centre, Security Infrastructure, and recently Virtualization. He has over 20 years in IT, in wide range of employers working as a freelance consultant including Finance, Service Providers and Online Companies. He is CCIE#6920 and has a few ideas about the world, but not enough to really count. He is a host on the Packet Pushers Podcast, blogger at EtherealMind.com and on Twitter @etherealmind and Google Plus.
Greg Ferro
Greg Ferro
Greg Ferro

Latest posts by Greg Ferro (see all)

  • http://twitter.tjevans.net TJ

    Disclaimer: I am a bit biased in favor of IPv6 … almost like it's what I do :).

    Having said that, and while admitting that IPv6 is not the panacea that some had hoped it would be (or think it is), I can comfortably say that IPv6 will be in more people's environments than currently expect it. ISPs are moving forward aggressively, and I have even worked with a few large enterprises recently who are moving forward. Specifically, I expect that we'll see IPv6 break into the "whole percent of traffic" range before mid-summer, and doubling (or more) soon thereafter. The recent IPv4 exhaustion @ IANA has raised a lot of awareness, and the USG requirements are pushing things forward as well.

    ISATAP should not be the first at-bat attempt for an environment doing IPv6; tunneled traffic is harder to filter, harder to apply QoS to, etc. I'd rather deploy IPv6 to the desktops than need to troubleshoot widespread automatic tunnels! Deploying native IPv6 can actually be a mitigation to OS'es doing automatic tunnels … In fact, I'd almost rather encourage the aforementioned (on the show) IPv4-IPv6 proxies, or even NAT64, vs widespread ISATAP. The downside to either is you will be breaking many sorts of non-HTTP traffic. Ask T-Mobile about the IPv6-only(!) handsets they are deploying today.

    The v6Ready program has been around for quite some time now, but is mostly being pushed out by the USGv6/NIST and UCCO+DISR/DoD work …

    Also note that your traffic, once you have any sort of IPv6 connectivity, does make a large shift all at once. A dual-stack host doing name resolution for a dual stack destination will use IPv6 for all of the user-land traffic … if an environment isn't ready for that sort of big-cutover there can be pain.

    The largest remaining pain points for IPv6, that I have seen, are: IPS/IDS, Load Balancers and VPNs. The majority of the rest of the core capabilities (naturally depending on scale needed, and how the platforms manage IPv4 +/- IPv6) are defined/developed.

    Keep up the great work!
    /TJ