Mark Evans Office of the Chief Engineer Space and Naval Warfare Systems Command San Diego, CA

1
Mark EvansOffice of the Chief EngineerSpace and
Naval Warfare Systems CommandSan Diego, CA
Approved for public release distribution is
unlimited (20 OCTOBER 2005)
2
Agenda

• IPv6 Policy
• Introduction to FORCEnet
• FORCEnet and IPv6
• Navy IPv6 Transition
• Innovation
• Tactical Edge Networks

3
IPv6 Policy

• DoD has established the goal of transitioning all
  DoD networking to the next generation of Internet
  Protocol, IPv6, by Fiscal Year (FY) 2008.
• Products and systems that are procured, acquired
  or in development after 1 October 2003 are
  capable of operating in IPv6 networks (as well as
  maintaining a capability to operate in todays
  IPv4 world).

Reference DoD CIO Memorandum Internet Protocol
Version 6 (IPv6) Interim Transition Guidance,
September 29, 2003.
4
What is FORCEnet?
Network Centric Warfare is the theory. Net-Centri
c Operations is the concept. FORCEnet is the
process of making the theory and concept a
reality. FORCEnet 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.
CNOs Strategic Study Group - XXI definition
from 22 July 02 CNO Briefing
5
FORCEnet and IPv6
IP Based Transformational Communications
6
IPv6 Impact

• Immense number of addresses
• Formerly private networks now available on the
  grid
• HME
• Navigation
• Weapons
• Sensors
• BUT..
• Standards still emerging
• Commercial products only now being built

Estimate
7
Navy IPv6 Transition

• OPNAV designated SPAWAR 05 as lead for Navy
• Establish a strategy for migrating Navy IT
  systems and networks to IPv6 capability
• Navy IPv6 Transition Plan (v1.2 13Aug2004)
• Navy IPv6 Test Guidance (v1.0 30Sep2004)
• Navy IPv6 Technical Transition Strategy (v1.0
  30Jun2005)
• Provide engineering support and Navy
  representation to DoD Enterprise IPTs/WGs,
  ensuring DON IPv6 requirements are presented and
  addressed
• FORCEnet C4I Virtual Systems Command team
  agreement for Navy IPv6 Steering Group (3Jan05)

NAVY INTERNET PROTOCOL VERSION 6 (IPv6) TEST
GUIDANCE
Version 1.0 30 September 2004
8
Navy IPv6 Transition Plan

• Introduction/Overview of IPv6
• Transition Strategy
• Managing/resourcing the transition
• Maintaining interoperability and security
• Governance
• Policy
• Roles and responsibilities
• Acquisition and procurement guidance
• Processes
• Tasks and milestones
• Approach to defining
• Timeline and roadmap

9
Navy IPv6 Test Guidance

• Describes initial approach of Navy to testing for
  transition to IPv6
• Includes procedures with objectives for IPv6
  compliance in testing activities
• Describes a testing strategy in context of
  architecture and standards
• Presents a testing strategy to include
• Information Assurance
• Interoperability goals
• Risk and configuration management
• Enterprise resources
• Knowledge sharing

10
Navy IPv6 Technical Transition Strategy

• Purpose of strategy
• Document Navy program baseline
• Identify critical infrastructure
• Define path for transition of capabilities
• Align IPv6 transition with Fn transformation
• Architecture/standards/processes
• Implementation planning/timelines
• Context of strategy for programs
• Accurate POM submissions
• Guidance to program managers
• Procurement of IPv6 capable products
• Contribute to risk reduction

11
Navy IPv6 FY06

• Supported Product List
• Refresh focused
• Critical Infrastructure Programs
• Secondary Programs/Applications
• Standards Development
• New Acquisition Focused
• Router
• Work Station
• IA issues
• Protocols for Assessment
• Classification Guidance
• Deployment Issues
• Timing
• Rate of refresh
• Dependencies

With Contract Language
12
Innovation Efforts

• Engage acquisition and laboratory activities in
  discussions to further innovation within IPv6
• CNO N7 directed activity
• Designed to support future Navy networks
• Coordinate across services through liaisons
• Collaborate with coalition and allied partners
• Champion demonstrations and experiments
• Work to acquire funding for originating activity
• Ensure coordination across services to avoid
  duplicity
• Provide a supporting role for pilots and early
  adopter programs
• Assist with roadmap and interoperability issues
  across services and within the DON CIO and OPNAV
  domains
• Continue Navy IPv6 education and communication
  strategy

13
IPv6 Future Navy

• Remote monitoring capability and/or control
• Available on demand, real-time,
• from anywhere on the ship
• Wireless video/communications
• Self forming networks
• Secure VoIP
• MANET
• not inclusive list

14
Global Information Grid Tactical Edge Networks
(TEN)
15
Background

• OSD recognized a shortfall in current GIG
  architecture
• Need to expand GIG Tactical Edge Network (TEN)
  services
• Requested a cross service working group
• Navy requested to lead in execution of vision
• Define the approach
• Joint group will have adjunct duty with OPNAV N71
  providing initial planning and act as the lead
• OPNAV N71 established a TEN lead and supporting
  systems engineering working group
• Refine program plans
• Engage surface and air platforms to ensure
  synchronization and interoperability
• Team with other services, have technical
  agreements on capabilities and standards
• Spiral development
• Focus on tactical edge first, then build out

16
Objective

• Current efforts
• Provide a concept to explore how Navy (and other
  services) can use/re-use current communication
  programs, systems and new technologies to support
  the core back network connectivity
• Identify applications and services to support
  multi-mission warfare requirements (JCAS, ASUW,
  etc)
• Align with GIG working groups
• Provide Net Centric Implementation Document
  (NCID) input
• Future development of spirals
• Currently 8 TEN spirals have been identified

17
Benefits

• Expanding the GIG Tactical Edge Network (TEN)
  services efforts would improve the Joint
  connectivity in the battlefield
• Expected operational impacts of Joint TEN
• Shorten the kill chain
• Improve the Common Operational and Tactical
  Picture (COTP)
• Improve platform survivability
• Enhance decision making speed and quality

APPROVAL
ENGAGE
ASSESS
FIX
TARGET
FIND
TRACK
18
Proposed Network Types

• TEN-A
• Very stable, low (tens of Kbps), medium (hundreds
  of Kpbs) and high data rate (up to hundreds of
  Mbps) RF links based on very long duration
  (weeks, months) communications relays, including
  tactical intra-theater SATCOM
• TEN-B (backbone)
• Stable, medium and high data rate RF links based
  on medium duration (hours, days) communications
  relays, including LOS relays involving manned and
  unmanned aerial platforms
• TEN-M (MANET)
• Rapidly changing low, medium, and high data rate
  RF links based on direct platform-to-platform
  communications, where both the physical proximity
  and composition of platforms in the network
  varies over time scales of minutes.

19
Anti-Surface Warfare Example (ASuW)
E2
BSN-M
BSN-M

F-18
BSN-M
BSN-M
F-18
TARGET
CVN
20
Questions
NavyIPv6_at_navy.mil