GCN Tech Blog

By GCN Staff

Blog archive

An attempt to define 'IPv6-capable'

The IPv6 Summit and Juniper Networks today issued a report that tries to get to the heart of an intriguing question facing agencies that must transition their networks to Internet Protocol version 6 in the coming years.

That question is, "If we're supposed to be buying IPv6-capable networking equipment, what exactly does it mean to be 'IPv6-capable?'"

As the report puts it, "The Office of Management and Budget and the Office of the Secretary of Defense have developed high-level definitions of what IPv6 Capable means; however, it is not clear how these definitions translate into specific requirements or capabilities that government officials can include in their contracting language."

The report, "IPv6 Capable-A Guide for Federal Agencies," spends a bit of time re-hashing IP history (and even answers that other intriguing question, "What ever happened to IPv5?"). And yes, it is prepared in large part by a company that would like no better than to sell you some IPv6 gear.

But the latter half of the report is very detailed, especially in describing the various Requests for Comments that are making their way through The Internet Engineering Task Force. The RFCs become Internet standards and interested government agencies can give feedback during the process to ensure IPv6 capabilities match needs. If nothing else, the report pulls together DOD and OMB IPv6 requirements, plus their "IPv6-capable" definitions, in one place.

It's the position of the writers that there is no single definition of IPv6-capable that fits every agency. And in places it appears industry is as confused about what agencies need in order to meet IPv6 milestones as some agencies surely are. Since there currently is no list of federally approved IPv6-capable products, this is an important conversation to have.

Posted by Brad Grimes

Posted by Brad Grimes, Joab Jackson on May 15, 2006 at 9:39 AM


inside gcn

  • urban air mobility (NASA)

    NASA seeks partners for urban air mobility challenge

Reader Comments

Thu, Jun 29, 2006 Capt Jeremy Duncan AZ

Not true! Not sure why all these organizations (Juniper and IPv6 Summit) continue to report such inaccuracies. The DoD already has a definition for its products. It was championed by the standards group for DISA: the DoD IT Standards Registry (DISR).Just recently on 1 May, their working groups on IPv6 finished the DoD IPv6 Standards Profiles for IPv6 Capable Products. This document contains six distinct IPv6 product classes that all IT products fall into. Those product classes are: (1) Host / Workstation, (2) Network Appliance, (3) Router, (4) Layer 3 Switch, (5) Security Device, and (6) Network Server. These product classes span current IT boundaries of IP voice, video and data. Each IPv6 product class references numerous IETF RFC standards that it must conform. The use of only DISR mandated or emerging RFCs are included in this listing.

Please post your comments here. Comments are moderated, so they may not appear immediately after submitting. We will not post comments that we consider abusive or off-topic.

Please type the letters/numbers you see above

resources

HTML - No Current Item Deck
  • Transforming Constituent Services with Business Process Management
  • Improving Performance in Hybrid Clouds
  • Data Center Consolidation & Energy Efficiency in Federal Facilities

More from 1105 Public Sector Media Group