| Navy IPv6 Transition
by Mark
Evans and the Navy IPv6 Transition Project Office
COMSPAWARSYSCOM
Office of the Chief Engineer
The advent of FORCEnet (Fn), along with the Global Information Grid (GIG)
architecture and Network Centric Warfare (NCW) concepts of operations,
demonstrates a definitive push to an enhanced Internet Protocol (IP) based
network capability. As part of the IT-21 and FORCEnet initiative, the
Navy began moving to an IP based network in the mid-'90s as the primary
method to connect the fleet with the ashore DoD infrastructure, basically
extending the evolving NIPRNET, SIPRNET and JWICS capabilities out to
the fleet.
IPv6 is an enabling technology that supports network-centric operations
and warfare, which will include mobile platforms, networked sensors, unmanned
systems, unmanned aerial vehicles, space systems and reach-back to logistics
bases, facilities, people and information.
The Naval Transformation Roadmap (Note 1) describes
a transformational process that focuses on accelerating the speed and
accuracy of information gathering and sharing, assessment, decision and
action at every level of command. The Roadmap also identifies FORCEnet
as the integral Naval component of Global Information Grid (GIG). FORCEnet
(Fn) is the operational construct and architectural framework for Naval
Warfare in the Information Age which integrates warriors, sensors, networks,
command and control, platforms and weapons into a networked, distributed
combat force, scalable across the spectrum of conflict from seabed to
space and sea to land. (Note 2)
Navy IPv6 Transition
In a series of official policy memoranda, the Assistant Secretary of Defense
for Network and Information Integration (ASD NII) established the goal
of transitioning DoD enterprise-wide networks from Internet Protocol Version
4 (IPv4) to IPv6. The memorandum dated as of 01 October 2003, requires
all GIG assets being developed, procured, or acquired shall be IPv6 capable
and able to maintain interoperability with IPv4 systems/capabilities.
(Note 3)
The Navy’s C4I (FORCEnet) Chief Engineer, at Space and Naval Warfare
Systems Command, San Diego, was designated the Navy IPv6 transition technical
lead by the Navy Information Officer (IO) and Chief of Naval Operations
(OPNAV) sponsors.
The Navy’s IPv6 Transition Project Office (NITPO) Team at the Space
and Naval Warfare Systems Command (SPAWARSYSCOM) coordinated development,
reviewed and received approval of the Navy’s IPv6 Transition Plan.
In addition, under the direction of the Department of Navy (DON) Chief
Information Office (CIO) and sponsorship of Chief of Naval Operations
(CNO) N71, SPAWARSYSCOM’s NITPO established the Navy IPv6 Steering
Group (NISG) as a consensus-based team for development, review and endorsement
of the Navy IPv6 Technical Transition Strategy document, which is currently
in draft for release by OPNAV. The NISG is chartered by the Fn/C4I Virtual
Systems Command (VS) with a team agreement (6 Jan 05) and is comprised
of 13 key Navy organizations that are responsible in various roles for
transition to IPv6: (1) ASN RDA CHENG; (2) DON CIO; (3) DRPM NMCI; (4)
NAVAIR; (5) NAVSEA; (6) NAVSUP; (7) NETWARCOM; (8) OPNAV N71; (9) PEO
C4I and Space; (10) PEO IT; (11) PEO IWS; (12) PEO Space Systems; and
(13) SPAWAR.
Navy IPv6 Technical Transition Strategy
The transition to IPv6 impacts a wide array of computer and network infrastructure.
To field an IPv6 capability while supporting the requirements of a legacy
IPv4 infrastructure is the challenge that the Navy faces in pursuit of
deployment. To face this challenge the Navy’s IPv6 Transition Project
Office (NITPO) Team at the Space and Naval Warfare Systems Command (SPAWARSYSCOM)
developed the Navy Internet Protocol Version 6 (IPv6) Technical Transition
Strategy Version 1.0. The Navy’s IPv6 Technical Transition Strategy
aligns with the Department of Defense guidance provided to Component Services
by DoD’s IPv6 Transition Office in the DoD IPv6 Transition Plan
Version 1.0 (24 Mar 05).
This strategy will establish the Navy’s IPv6 program baseline,
identify the critical infrastructure and define the path for transition
of capabilities. It aligns IPv6 transition with FORCEnet transformation
along with architecture, standards processes, implementation and planning
guidelines. The Strategy also provides information to Navy program managers
on accurate budget submissions, risk reduction and IPv6 capable products.
Overview of the Navy IPv6 Technical Transition Strategy:
- Strategy — a summary of transition strategy principles,
transition approach, including key Navy programs/systems with identified
critical infrastructure as early adopters for transition to IPv6, dual-stack
network use, addressing plan, deployment product list, evaluation and
certification, intermediate transition, other necessary intermediate
transition mechanisms and final transition.
- Architecture — a high level description of architecture
for transition to IPv6 within context of enterprise IT, implementation
of the GIG, and Fn, focus on technical architectures and standards for
IPv6 transition at network layer, IP addressing plans as applicable
to development and implementation phases, and identification of Navy
critical infrastructure for early adoption of IPv6.
- Transition Mechanisms — guidelines on selection of a
limited subset of IPv6 transition mechanisms (Dual-Stack and tunneling)
to reduce cost, time and risk for migration from IPv4 with recommended
actions for managing these risks.
- Deployment — guidance on specific steps to deploy IPv6,
deployment product list and pointers to organizations with preferred
product lists and certification, core-to-edge deployment of the core
critical infrastructure in advance of edge applications, training and
other operational deployment impacts to warfighter, test, evaluation
and certification guidance as applicable to IPv6 deployment.
- Transition Roadmap — guidelines on technical alignment
of IPv6 capability milestones, incorporation of applicable IPv6 transition
timelines for Navy key programs/systems within existing and emerging
technical roadmaps for GIG, Fn, and other Joint capability-based plans,
i.e. Joint C4I Campaign Plan, with emphasis on transition roadmap integrated
within tech refresh cycle/funding.
- List of Key Navy Programs and Critical Infrastructure —
Summary of the Key Programs identified and a definition list for critical
infrastructure (inclusive of a mapping of the critical infrastructure
to the key programs).
- Architecture and Addressing — Summary of components and
IA considerations, DNS issues with IPv6, and summary of near-term addressing
plan for Navy implementation of IPv6 with emphasis on test and evaluation
addresses.
- Information Assurance and Security Guidance — Summary
of the currently available IA/Security guidance for transition to IPv6.
- Risk Management — Summary of recommendations from each
section of Navy IPv6 TTS.
- Risk Reduction Experiments — Summary of experiments to
reduce risks identified for transition to IPv6 as presented in sections
within Navy IPv6 TTS.
- Contract Language — Technical guidelines for incorporation
of contract language for transition to IPv6.
The Navy has developed a transition strategy that will continue to evolve
as the Navy moves closer to implementation. Navy's transition approach
to IPv6 will occur in progressive stages: initial, intermediate and final
transition. This approach is chosen to reduce the cost, risk, technical
and scheduling impacts associated with migrating from IPv4 to IPv6 over
an extended period of time. Also, this approach facilitates a disciplined
system engineering processes, which are aligned with programmatic funding
cycles that allow budgets for IPv6 technical refresh to occur over an
extended period. The goal is to have a significant portion of the Navy's
networking infrastructure to accommodate both emergent IPv6 and legacy
IPv4 traffic.
Footnotes:
1. United States Department of the Navy. Naval Transformation
Roadmap, July 2002
2. CNO’s Strategic Study Group - XXI definition
from 22 July 02 CNO Briefing
3. DoD CIO Memorandum “Internet Protocol Version
6 (IPv6) Interim Transition Guidance,” 29 Sep2003
|
