IPv6 Status in U'S Department of Defense DoD

1
IPv6 Status in U.S Department of
Defense (DoD)

• HyoungJun KIM
• ETRI

2
Purpose

• To let industry know DoDs commitment to IPv6
• To provide state of DoDs efforts to date

3
Background

• IPv4 has been in use for almost 30 years
• Cannot support for address space, mobility and
  security in peer-to-peer networking
• IPv6 is equipped with significant enhancements
  that will provide better internetworking
  capabilities
• DoD sets plan for move to IPv6

4
DoDs Need for IPv6

• Why is IPv6 needed?
• Future combat systems demand
• Network ubiquity ( IP centric)
• Mobility and ad-hoc Networking (dynamic
  addressing)
• Security (embedded IPsec)
• Much larger address space
• Improved routing
• Route aggregation reduces the size of routing
  tables
• Simplified header reduces router processing loads
  
• Enhanced security and QoS
• Mandatory IPsec support all fully IPv6 compliant
  devices
• Improved support for mobile IP and mobile
  computing devices
• Reduced Administration
• IPv4 Cannot support future required capabilities

5
DoDs Need for IPv6

• Net-Centric Operations
• - The New Killer Operations

The Global Information Grid (IPv6 based Network)
?
A roadmap of key Net-Centric Initiatives
6
DoD IPv6 Strategy Announcements

• IPv6 Policy released, June 9, 2003
• Stenbit (DoD CIO) signed a policy memorandum that
  outlines DoDs transition to the new Protocol by
  2008
• DoD goal is to complete the transition to IPv6
  for all inter and intra networking across the DoD
  by FY 2008
• SIPRNET or NIPRNET might be one of the programs
  switched over to IPv6
• A draft DoD IPv6 transition plan will be released
  by early September
• IPv6 Policy released, Sep 29, 2003
• Provide interim guidance to support the
  requirement to begin to procure/acquire IPv6
  capable GIG assets on 1 Oct 2003.

John P.Stenbit DoD Chief Information officer
7
Draft DoD IPv6 Policy

• DoD Components are encouraged to coordinate,
  undertake, and participate in IPv6
  demonstrations/testbeds and share the results
• DoD activities acquiring new or upgrading
  existing IP-based technologies or services must
  recognize IPv6 readiness/compatibility as a
  likely future need
• DISA will continue to manage DoD IP address
  allocation, registration and control on an
  enterprise basis to promote interoperability and
  security
• DoD users will only acquire IP address space
  originating from DISA
• Finally, DISA is tasked to lead (with the support
  for the Joint Staff (JS), DoD Chief Information
  Officer (CIO) and Services) the effort to develop
  and initial implementation plan within six months
  from the date of this memo.

8
DoD IPv6 Policy Plan

• To prepare for eventual IPv6 migration and
  coexistence
• Effective Oct 03, all GIG assets acquired,
  procured and developed shall be IPv6 capable and
  maintain interoperability with IPv4
• DoD CIO identify pilots, demonstrations, and
  test beds
• GIG transition from FY 05 to FY 07
• DISA to acquire , manage, allocate, and control
  necessary IPv6 address space for DoD

9
DoD IPv6 Timeline
10
The DISA Plan
11
Phase Plan for DoD
2002 2004 2005
2007 2008
Initialization Phase
Core Implementation Phase
Core-Existence Phase
IPv6 Native Phase
Test Analysis Phase
-Develop master plan -Develop DoD transition
- Extend IPv6 Test Bed Translate or tunnel IPv6
through core networks - Develop DoD IPv6 Core
implementation policy
-Migrate core to dual stack -Continue edge
migration -Introduce IPv6 native in the
edge -Introduce IPv6 native applications -Develop
DoD IPv6 co-existence policy
- Finalize core dual stack - Finalize edge dual
stack - Implement advanced IPv6 functionality -
Complete dual stack application conversions -
Develop DoD IPv6 native Policy - Develop DoD
legacy IPv6 Policy
- Finalize native IPv6 applications - Finalize
native IPv6 Network devices - Migrate edge
network and device to native IPv6 - Migrate core
networks to native IPv6 - De-integrate IPv4 (if
Necessary)
12
The Approach

• Establish / participate in an IP distributed test
  network
• Realistic implementation / architecture
• Make interoperability the guiding principle
• What will interoperate now and how
• Encourage vendor participation
• Interoperability with other IPv6 Systems
• Interoperability with IPv6 using standard
  applications
• Demonstrate ability to use various transition
  mechanisms
• New features of IPv6 beneficial to military
  application

13
The Approach

• Assist in the development of test criteria
• Certified products on JITC list of certifications
• Phased implementation process
• Test and analysis phases
• Initialization phase
• Core Implementation phase

14
Exercise Participation

• DICE 03
• MoonV6
• DICE 04

15
Moonv6 Participation

• What is Moonv6?
• Largest multi-vendor test and demonstration of
  next generation Internet protocol
• Collaborative effort between U.S. DoD , UNH-IOL ,
  NAv6TF and Internet2
• Phase I The interoperability event and initial
  deployment, 6th17th ,Oct 2003 (2 weeks)
• Phase II IPv6 Service and testing additional
  security, mobility and application scenarios, Jan
  2004
• More than 30 organizations participated(
  S-NET,ETRI DSTM)
• Router Hardware vendors Alcatel, Cisco,
  Hitachi, NEC, Fujitsu, Extreme, Foundary, Hexago,
  IP Infusion, Juniper, NEC, Nokia
• Host Hardware vendors Agilent, Compaq, Elmic,
  EMC, HP, IBM, Sun, Windriver

16
Moonv6 Participants

• Moonv6 created a network reaching more than 3,000
  miles from Durham, N.H. to San Diego, C.A.

17
MoonV6 Results

• Moonv6 provides strong validation for IPv6 and
  demonstrates the technologys effectiveness under
  operational conditions
• Phase I involved approximately 80 servers,
  switches and routers configured in dual stack
  mode, with IPv4 and IPv6 running simultaneously
• UNH-IOL will publish a whitepaper about testing
  results
• Proved IPv6 is stable and ready for integration
  with todays Internet !!

18
Conclusion

• European and Asia High-up officials within
  Government have made formal statements regarding
  the importance of IPv6
• U.S DoD is to complete the transition to IPv6 for
  networking across the DoD by 2008
• All major vendors have to support IPv6 Products
• Market requirements in DoD are emerging
• IPv6 Deployment will bring business and
  operational benefits to ..

19
Thank you
Contact Information
Hyoung-Jun KIM Protocol Engineering Center
Electronics and Telecommunications Research
Institute E-mail khj_at_etri.re.krTel 82 42 860
6576, Fax [phone] http//www.etri.re.kr