Next Generation Internet NGI

1
Next Generation Internet (NGI)
Michael P. Brig SPAWAR CHN NGI Program
Manager Code 323MB (843)-974-4675 brigm_at_spawar.nav
y.mil
2
Network Centric Warfare
Network Centric Warfare / Information Warfare is
mostly Internet Protocol (IP) based Warfare
3
Virtual Warfare
Virtual Warfare is also based on the Internet
Protocol (IP).
4
NGI the Next Y2K???

• Major networking paradigm shift!
• Costly!
• No drop dead date!
• No killer application!
• Extremely contentious!
• Its happening anyway...

5
Why TCP/IPv6 ???

• Tremendous Internet growth
• International electronic commerce
• Voice, video, and data convergence
• Security
• Reduced support costs
• Mobile communications

6
Internet Hosts (1989-2006)
x1000
7
Internet or InformationAppliances
8
Short History

• 1991 - Concern with B class address exhaustion
  and router table explosion prompt IETF to begin
  investigating an IPv4 replacement. Concurrently,
  IETF began enhancing IPv4.
• December 1993 - RFC 1550 IP Next Generation
  (IPng) White Paper Solicitation.
• 1994 1995 - Prospective IPng shootoff and
  concept development.
• 1995 - IPv6 RFCs begin IETF standards process.
• 1998 - IPv6 implemented in OS sw and Routers,
  6Bone is deployed to over 200 sites worldwide,
  and Internet begins TCP/IPv4 to TCP/IPv6
  migration.
• 2010 - Completely TCP/IPv6 Internet!

9
TCP/IPv6 Enhancements

• bigger addresses and hierarchical addressing.
• flow identification for different qualities of
  service
• automatic configuration (plug-and-play)
• support for strong authentication and privacy
  (IPsec).
• support for host mobility
• more efficient and flexible
• incrementally deployable

10
ISO OSI Model
Internet Protocol version 4 (IPv4)
The current Internet is configured like this.
11
IPv4 Network
12
ISO OSI Model (IPv6)
Internet protocol version 6 IPv6
The NGI will be configured like this.
13
ISO OSI Model (IPv6)
Internet protocol version 6 IPv6
The effects of replacing IPv4 with IPv6 are
throughout the networking stack! At least 58
protocols have been modified to support IPv6.
14
IPv6 Network
15
IPv6 Enabled Routers

• Baynetworks Routers
• Telebit TBC1000 TBC2000 Routers
• PacketEngines PowerRail Routing Switches
• 3COM Netbuilder Routers
• Hitachi NR60 Router
• All other Router vendors have prototypes. It is
  anticipated these products will fully support
  IPv6 within one calendar year.

16
IPv6 Enabled Operating Systems

• IBM AIX 4.3 and OS/390
• FTP Software IPv6 stack for Win95 98.
• Linux 2.2
• SCO UnixWare 7
• All other OS vendors have prototypes. It is
  anticipated these products will fully support
  IPv6 within one calendar year.

17
IPv6 Enabled Application SW

• DNS (BIND 4.9.2 and 8.X)
• Open Source Netscape Navigator (Mossilla)
• Microsoft Research Internet Explorer (IE)
• Microsoft Research RAT and SDR multicast
  applications
• Microsoft Research Fnord web server

18
IPv6 Enabled Test Equipment

• Precision Guesswork LANWatch network protocol
  analyzer.
• Network Instruments Distributed Observer
• EcoSYSTEMS EcoSCOPE
• Shomiti Systems Portable Surveyor release 2.5
• RADCOM RC100-WL

19
Principle DoD IPv6 Issues

• IPv4 is nearly everywhere in DoD C4ISR, Weapons,
  MS, Wargaming, and IT!!!
• 58 Internet protocols modified to migrate to
  IPv6.
• COTS and GOTS software hard coded for IPv4.
• Domain Name Service (DNS)
• IPv6 over ATM.
• Different security paradigm.
• Interoperability and support costs during the
  transition.
• Microsoft Windows 2000 and Windows CE.
• NATO IPV6 testbed, US DoD JTA, and Funding.

20
SPAWAR Charleston IPv6 Plan

• Build a TCP/IPv6 testbed network. Connect the
  testbed to 6BONE, 6REN, or DARPA Supernet.
• Test TCP/IP applications as they port from IPv4
  to IPv6.
• TCP/IPv6 training at SSCC.
• Cost share with industry in the development of
  TCP/IPv6 network models for analysis.
• Host the AFCEA/DoD IPv6 Transitioning to the
  Next Generation Internet conference to discuss
  US military migration strategies for TCP/IPv6.
• Participate in local/regional Internet Societies.

21
MS Community Prepare!

• Educate yourself on the issue.
• Participate in the DoDs NGI architecture
  development.
• Begin to assess programs and SW for IPv4
  dependencies.
• Examine the new commercial security paradigm
  (IPSec).
• Begin to POM for the IPv4 to IPv6 transition.
• Incorporate IPv6 requirements into new programs.
• MS can be utilized to assist the transition for
  IPv4 to IPv6.