Download Airborne Networks TIM Why IPv6

Communications Technology Division
Glenn Research Center
Satellite Networks & Architectures Branch
Airborne Networks TIM
Why IPv6 ?
Will Ivancic
[email protected]
216-433-3494
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
1
Introductions
Communications Technology Division
Glenn Research Center
Satellite Networks & Architectures Branch
• Who am I and what have I done with IPv6?
• Who are you?
– Have you deployed ANY IPv6 networks?
– What do you know about:
• Networking?
• Internet Protocols (v4 or v6)?
• Network Security?
Informal and Interactive
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
2
Are this your interest?
Glenn Research Center
Communications Technology Division
Satellite Networks & Architectures Branch
• Questions
– Why use IPv6 vs IPv4?
– How mature is IPv6?
– Mobile Networks and Ad Hoc Networks?
• IPv6 and Network Centric Operations
– What are the advantages for military networks?
– What are the advantages for airborne networks?
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
3
Communications Technology Division
Glenn Research Center
Satellite Networks & Architectures Branch
Why use IPv6 vs IPv4?
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
4
IPv6 vs IPv4
Communications Technology Division
Glenn Research Center
Satellite Networks & Architectures Branch
• Addressing
–
–
–
–
–
Larger Address space
Autoconfiguration
Link Local Addressing
Unique Local IPv6 Unicast Addressing (private addresses)
Location Management
• Potentially more secure
– IPsec capability mandated
– Larger address space
•
•
•
•
No need for Network Address Translation (NAT)
Peer-to-Peer networking
Potentially better Quality of Service (QOS)
Nearly everything new is IPv6
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
5
SYZYGY Engineering
Communications Technology Division
Glenn Research Center
Satellite Networks & Architectures Branch
Internet Protocol version 6
and Network Centric Operations
Key Concepts
Will Ivancic
SYZYGY Engineering
[email protected]
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
6
© 2004 Syzygy Engineering – Will Ivancic
Network Design Triangle
Communications Technology Division
Glenn Research Center
Maturity
Policy
SYZYGY Engineering
Satellite Networks & Architectures Branch
$$$ Cost $$$
Protocols
Architecture
Scalability
Mobility
Security
QoS
Bandwidth
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
7
© 2004 Syzygy Engineering – Will Ivancic
Policy
Communications Technology Division
Glenn Research Center
SYZYGY Engineering
Satellite Networks & Architectures Branch
Just because you can do
something doesn’t mean
you are permitted to do
something.
Source: http://minhdo.bitterjerksociety.org/gallery/page_03.htm
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
8
© 2004 Syzygy Engineering – Will Ivancic
IPv6 Functional Capabilities
Glenn Research Center
Communications Technology Division
• Expanded Addressing and
Routing
• Simplified Header Format
• Extension Headers and Options
– Options are placed in
separate headers after the
core routing information
– Options do not necessarily
have to be processed in
core network (speed)
• Authentication and Encryption
Support
– Required in ALL
implementations of IPv6!
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
SYZYGY Engineering
Satellite Networks & Architectures Branch
• Autoconfiguration
• Source Routing Support
– Ad Hoc Network
– Route Optimization for
Mobility
• Simple and Flexible Transition
– Incremental Upgrade
– Incremental Deployment
– Easy Addressing (
– Low Startup Costs
• Quality of Service Capabilities
– Real-Time Traffic
– Traffic Class
– Flow labels
9
© 2004 Syzygy Engineering – Will Ivancic
IPv4 & IPv6 QoS Fields
Communications Technology Division
Glenn Research Center
IPv4 Header 20 bytes
Version
IHL
Type of Service
Satellite Networks & Architectures Branch
IPv6 Header, 40 bytes fixed
Total Length
Version
Identification
Flags
Traffic Class
Fragment
Offset
Payload Length
Time to Live
Protocol
SYZYGY Engineering
Flow Label
Next
Header
Hop Limit
Header Checksum
Source Address
Source Address
Destination Address
Legend
Options
Padding
field’s name kept from IPv4 to IPv6
Destination Address
fields not kept in IPv6
Name & position changed in IPv6
New field in IPv6
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
10
© 2003 Cisco Systems, Inc. All rights reserved – Steve Pollock
Currently Defined Headers (RFC2460)
Communications Technology Division
Glenn Research Center
•
•
The IPV4 options field was
replaced by the modular
extension header.
There is no set limit on the
number of these headers you
can have.
•
TCP Header + Data
IPv6
MH
IPv6
HBH
RH
FH
IPv6
MH
AH
ESP
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
DO
AH
Satellite Networks & Architectures Branch
HopByHop, Routing Header,
Fragment Header, Destination
Options, Mobility Header,
Authentication Header,
Encrypted Security Payload.
Hop-By-Hop must follow IPv6
Header, Otherwise no set
order
ESP
TCP Header + Data
UDP Header + Data
11
© 2003 Cisco Systems, Inc. All rights reserved – Steve Pollock
Addressing Architecture
Communications Technology Division
Glenn Research Center
SYZYGY Engineering
Satellite Networks & Architectures Branch
• Unicast
– Unspecified 0::0
– Loopback 0::1
– User Local Addresses
• Link Local prefix 1111111010
• Site Local prefix 1111111011
Deprecated
• Unique Local IPv6 Unicast prefix FC00::/7
– Analogous to IPv4 Private Address Space
– provides for 2.2 trillion addresses
• Anycast
• Multicast
Nice Explaination of Anycast for IPv4 at
http://www.net.cmu.edu/pres/anycast/Deploying%20IP%20Anycast.ppt
prefix 11111111
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
12
© 2004 Syzygy Engineering – Will Ivancic
Address Allocation Policy
Communications Technology Division
Glenn Research Center
/23
2001
/32
/48
SYZYGY Engineering
Satellite Networks & Architectures Branch
/64
0410
Interface ID
Registry
interface
identifier
(64 bits)
ISP prefix
Site prefix
LAN prefix
•
128-bit addresses:
– 340,282,366,920,938,463,463,374,607,431,768,211,456 (340 duodecillion)
– Over a million addresses for every person on the planet!,
– But not really due to inefficiency of address allocations
•
•
Administered by IANA to Regional Registries: ARIN, APNIC, RIPE, LACNIC
The allocation process is under reviewed by the Registries:
–IANA allocates 2001::/16 to registries
–Each registry gets a /23 prefix from IANA
–Formerly, all ISP were getting a /35
–With the new policy, Registry allocates a /32 prefix to an IPv6 ISP
–Then the ISP allocates a /48 prefix to each customer (or potentially /64)
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
13
© 2003 Cisco Systems, Inc. All rights reserved – Steve Pollock
Transition and Operations Costs
Communications Technology Division
Glenn Research Center
Transition Cost
Cost Difference
Between IPv4 / IPv6
Operations
Source: PC of Japan
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
14
SYZYGY Engineering
Satellite Networks & Architectures Branch
IPv4 Address Pool
Glenn Research Center
Communications Technology Division
Projections are based on
history so all bets are off
once the run-on-the-bank
starts.
The only sure thing that
can be said is that the
exhaustion event will
occur before the end of
this decade.
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
15
Satellite Networks & Architectures Branch
IP Address Status in China
Communications Technology Division
Glenn Research Center
SYZYGY Engineering
Satellite Networks & Architectures Branch
(unit 1 million)
Total IPv4 address (unit 1)
41,456,128
1300
29,002,240
21,534,208
13,269,504
7,555,584
5,409,280
3,746,304
0
41
1997 1998 1999 2000 2001 2002 2003
Total IPv4 address Chinese Population
“IPv6 is good for China and China is good for IPv6. China
brings the scale needed for IPv6. IPv6 killer application will
occur in China firstly" - Latif Ladid--IPv6 Forum President
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
16
Data source: CNNIC, Dec.2003
Key Technology Enablers
Glenn Research Center
Communications Technology Division
SYZYGY Engineering
Satellite Networks & Architectures Branch
• PKI, IKE and Key and
Policy Management and
Applications
• Zero Configuration in rapidly
deployed and mobile
networks
– DNS, DHCP and KEY Servers
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
17
© 2004 Syzygy Engineering – Will Ivancic
Peer-to-Peer Networking
Glenn Research Center
Communications Technology Division
Satellite Networks & Architectures Branch
Client/Server Model
Peer-to-Peer Communication
• Voice, Video and Data
• Issues:
Typical IPv4
Peer-to-Peer
Communications
– Security (particularly in DoD and
Corporate Networks)
– Control
Peer-to-Peer
Service
(IM, KaZa, etc)
1
2
Internet
3
• End-to-End relative to Peer-toPeer
Firewall and
router w/NAT
Firewall and
router w/NAT
– End-to-End allows direct
communication once peer’s
address is known
– Typical IPv4 with NAT requires
Peer-to-Peer server and may
require application software (IM,
KAZA, etc)
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
SYZYGY Engineering
Peer-to-Peer Server is
not required
Peer-to-Peer
Service
(IM, KaZa, etc)
Internet
18
Firewall and
router
No NAT
Firewall and
router
No NAT
© 2004 Syzygy Engineering – Will Ivancic
Flow Label
Communications Technology Division
Glenn Research Center
SYZYGY Engineering
Satellite Networks & Architectures Branch
• Used by host to request special handling for certain packets
• Unique flow is identified by source address and non-zero flow label
– Expected use is per-flow end-to-end QoS
• RSVP, Video, Gaming, VOIP
– Without the flow label the classifier must use transport next
header value and port numbers
• Less efficient (need to parse the option headers)
• May be impossible (due to fragmentation or IPsec ESP)
• Layer violation may hinder introduction of new transport
protocols
• IPv6 nodes not providing flow-specific treatment MUST ignore the
field when receiving or forwarding a packet
• Immature Technology – Research Area
The Flow Label field is useless, unless it is actually used!
Airborne
TIM at LMCO,
© 2004Network
Syzygy Engineering
– WillChantilly
Ivancic VA Nov 7,2007
19
Flow Label
Security Considerations
Glenn Research Center
Communications Technology Division
SYZYGY Engineering
Satellite Networks & Architectures Branch
• The IPsec protocol, as defined in [IPSec, AH, ESP], does not include
the IPv6 header's Flow Label in any of its cryptographic calculations
– In the case of tunnel mode, it is the outer IPv6 header's Flow
Label that is not included
• Modification of the Flow Label by a network node has no effect on
IPsec end-to-end security
– It cannot cause any IPsec integrity check to fail.
– As a consequence, IPsec does not provide any defense against
an adversary's modification of the Flow Label (i.e., a man-in-themiddle attack).
Airborne
TIM at LMCO,
© 2004Network
Syzygy Engineering
– WillChantilly
Ivancic VA Nov 7,2007
20
Communications Technology Division
Glenn Research Center
Satellite Networks & Architectures Branch
How mature is IPv6?
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
21
Maturity
Glenn Research Center
Communications Technology Division
Satellite Networks & Architectures Branch
• IPv6 Forum has created the “IPv6 Ready” Logo
Program
– Phase I (Core)
– Phase II
• IPv6 Core Protocols (Now Available!)
• IPsec (Now Available!)
• MIPv6 (Now Available!)
• NEMO (Now Available!)
• MLD (Under Developing)
• Transition (Under Developing)
• IKE (Experimental)
• China Olympics
– China made a comprehensive national commitment to IPv6 way
back in 2000
– "The Chinese are trying to build the number-one rated information
infrastructure in the world, and want to announce in 2008 - at the
time of the Beijing Olympics - that they are thus an economic
superpower,"
• Cisco router in Low Earth Orbit (CLEO)
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
22
Monitoring
Points
Globalstar
IPv4 Mobile LAN
IPv6
Mobile
Router
IPv6 Mobile
Networking
Demonstration
2004
Z
T-Mobile
4-to-6 Tunnel
6-to-4 (DOOR)
IPv6 Mobile LAN
6-to-4 (DOOR)
IPv4
Public
Internet
Corresponding
Public Node
CNS
IPv6
Intranet
IPv6
Network
Z
GRC Open Network (DMZ)
IPv6 Web
Server
IPv6 Web
Server
Remote
Controlled
Webcam
Glenn Research
Center
Eurocontrol
IPv6
Intranet
IPv6 Web
Server
NASA NREN
IPv6
Intranet
IPv6
Home
Agent
6-to-4
(DOG)
The Cisco router in low Earth orbit (CLEO)
Glenn Research Center
Communications Technology Division
• Put a COTS Cisco router in
space
• Determine if the router could
withstand the effects of launch
and radiation in a low Earth orbit
and still operate in the way that
its terrestrial counterparts did.
• Ensure that the router was
routing properly
• Implement mobile network and
demonstrate its usefulness for
space-based applications.
– Since the UK–DMC is an operational
system, a major constraint placed on
the network design was that any
network changes could not impact the
current operational network
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
24
Satellite Networks & Architectures Branch
CLEO
Communications Technology Division
Glenn Research Center
Satellite Networks & Architectures Branch
• Thursday, 29 March 2007, NASA Glenn
Research Center, Cisco Systems and Surrey
Satellite Technology Ltd (SSTL) performed
the first configuration and demonstration of
IPsec and IPv6 on a satellite in low Earth
orbit.
• Applications / Functions
–
–
–
–
Static IPv6 and IPv4 routing
IPv6 over IPv4 mobile routing
IPv6 over IPsec for IPv4
IPv6 Applications
• Secure Shell, Telnet and Web browsing to the
router.
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
25
GRC/SSTL/CLEO IPv6/IPv4 Tunnels
Communications Technology Division
Glenn Research Center
Satellite Networks & Architectures Branch
8.1Mbps from satellite
9600bps to satellite
frame relay DLCI 17 – unencrypted ‘clear’ link
IPv6 in 6-over-4 tunnel in Mobile IPv4 tunnel to Home Agent
Mobile IPv4
native IPv4
6-over-4 tunnel for non-mobile IP traffic
native IPv6 between routers
2621
router
PIX
firewall
Secure VPN tunnel
secured IPv6 in 6-over-4 tunnel over IPv4 IPsec
Cisco MAR
3251 on
UK-DMC
PIX
firewall
Internet
IPv6 in 6-over-4 tunnel in Mobile IP as above, if IPsec link is preferred and used instead
IPv4
IPv4
IPv6
IPv4 IPsec encryption between routers
frame relay DLCI 18 – encrypted link
SSTL ground station LAN,
carrying IPv4 and IPv6 over Ethernet
NASA
Glenn
Home
Agent
IPv4 IPsec
Mobile IPv4 tunnel
Private 192.x addressing
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
Private 192.x addressing
26
Public addressing
Communications Technology Division
Glenn Research Center
Satellite Networks & Architectures Branch
IPv6
Live Demonstrations
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
27
Issues
Glenn Research Center
Communications Technology Division
• Site Multihoming
• Poorly written applications
– Written without consideration for IPv6
• Legacy Systems
• Dual Stack and Security
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
28
Satellite Networks & Architectures Branch
Glenn Research Center
Communications Technology Division
Satellite Networks & Architectures Branch
What are the advantages for
military networks?
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
29
IPv6 Addressing Architecture
Communications Technology Division
Glenn Research Center
Satellite Networks & Architectures Branch
• The IPv6 addressing architecture utilizes scoped
addresses, including scoped multicast addresses.
– Example: IPv6 has all-routers addresses in every subnet, which
allow a node to find or communicate with routers without knowing
their unicast addresses ahead of time.
• IP address resolution
– IPv4 uses the ARP and IPv6 uses Neighbor Discover (ND)
• ARP operates directly on top of the link layer
• ND operates using ICMPv6, on top of IPv6, on top of the link
layer.
• IPv6’s ND is highly extensible through IP and ICMPv6 options
which can be used for:
– Security (authentication of network elements and resolution protocol
messages),
– Automatic prefix and interface identifier configuration
– Advertisement of link MTU.
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
30
Routing
Glenn Research Center
Communications Technology Division
• IPv6 Dynamic Routing works.
• IPv4 Dynamic routing DOES NOT?
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
31
Satellite Networks & Architectures Branch
Applications
Glenn Research Center
Communications Technology Division
• Sensorwebs
• Mobile Ad Hoc Networks (MANETs)
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
32
Satellite Networks & Architectures Branch
Sensors
Glenn Research Center
• IPv6 Myths
Communications Technology Division
Satellite Networks & Architectures Branch
– Headers are too big
• Stateless header compression
– Code size
• IP stacks available in 3-6K range
• Initial indications are MAC, AODV and IP stack under 20K
– RAM
• 1.5 to 2K are current estimates
6LowPan Hardware
• Why IPv6
– Common Infrastructure
• Hybrid networks
– Larger address space
– No need for configuration servers
• No DHCP server
– No need for NAT
– Header more easily compressed
• Stateless Header Compression
– Header can be compressed to just 4 bytes on-net and 12 bytes off-net
– Assumes network will not be a transit network
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
33
Source: Geoff Mulligan, Invensys Controls
UNCLASSIFIED
Global Information Grid
Glenn Research Center
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
Communications Technology Division
34
SYZYGY Engineering
Satellite Networks & Architectures Branch
UNCLASSIFIED
UNCLASSIFIED
The “Tactical Internet”
Communications Technology Division
Glenn Research Center
SYZYGY Engineering
Satellite Networks & Architectures Branch
Military & Commercial
SATCOM
TOCs
Radio
Net
“OPEN SYSTEMS”
ROUTING
Radio
Net
Radio
Net
ROUTERS
Radio
Net
Tactical
Internet
Radio
Net
Radio
Net
OPEN
INTERFACES
OPEN
INTERFACES
Dismounted
Soldiers
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
35
UNCLASSIFIED
UNCLASSIFIED
Relationships between the DoD NICs, RIRs and IANA
Communications Technology Division
Glenn Research Center
SYZYGY Engineering
Satellite Networks & Architectures Branch
IANA
LACNIC
AFRNIC
ARIN
RIPE
APNIC
MIL
AF
/22
•
•
•
ARMY
/22
NAVY
USMC
Other DoD
NICS (if any)
/23
/23
/22
The MIL NIC has, to date, acquired four IPv6 address blocks from ARIN.
– 2600:: /22, 2604:: /22, 2608:: /22, and 260C:: /22
4 /22 prefixes are not contiguous
– There are 255 /22 prefixes between each allocation.
– No stated policy by ARIN, but, a reasonable assumption that the unassigned 1020 /22 prefixes
within the 260:: /22 prefix would be used for DoD’s future address acquisitions.
Additional blocks outside of 2600::/12 may be reassigned from ARIN to DoD when this block is fully
consumed
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
36
UNCLASSIFIED
UNCLASSIFIED
Enclave Mapping
SYZYGY Engineering
Communications Technology Division
Glenn Research Center
Satellite Networks & Architectures Branch
Enclave Name
Address Block per Platform
Black Core
/48
UNCLAS
/48
SECRET
/48
TOP SECRET
/48
SCI
/48
Allied
/48
Coalition #1
/48
Coalition #2
/48
Coalition #3
/48
Coalition #4
/48
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
37
UNCLASSIFIED
Communications Technology Division
Glenn Research Center
Satellite Networks & Architectures Branch
What are the advantages for
airborne networks?
This section is taken from a presentation by Terry
Davis of Boeing
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
38
Glenn Research Center
V6 QoS & Traffic Management
Architecture Example
Communications Technology Division
Satellite Networks & Architectures Branch
v6 systems can join multiple networks
Implications:
• Architecture could assign networks for specific uses
• Traffic could be segregated by network
– High QoS can be assigned to “a” network
• Voice on one, video on one, etc.
– Special comm priority networks could be created
• ATC, FANS, ACARS, etc
• Link capacity could be managed by “network priority” not just
“packet priority”
• System capability growth could be managed over time
– Older less capable systems assigned to specific networks
– Newer capabilities to other networks
Source: Terry L Davis, Boeing
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
39
Network Partitioning by Service
Architecture Example
Communications Technology Division
Glenn Research Center
Satellite Networks & Architectures Branch
QoS & Security
Service Levels for:
NSPs/Airlines/Framers/Suppliers/etc
• Network Control
• Voice over IP
• High Priority
Security Perimeter
• Special Projects
• General Purpose
Security Mgt
PIES
Net-Mgt
& Routing
VOIP
Many logical networks
share a common physical
infrastructure.
Network Infra.
AOC
ATC
PIES
Data Center
Source: Terry L Davis, Boeing
Networks are logically
partitioned.
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
40
QoS can be managed by
both network & flow
Glenn Research Center
Security – Architecture Example
Communications Technology Division
Satellite Networks & Architectures Branch
IP-v6 Networks could:
• Require authentication to join
– Have different authentications (ATC/AOC/PIES)
– Have different security levels and encryption
• Utilize Transponder codes
– For authentication
– For encryption keying
Individual systems with a single interface could:
• Join multiple secure networks simultaneously
– With different security levels (MLS) per network
– With different encryption per network
– With different QoS
Source: Terry L Davis, Boeing
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
41
IP-v6 Network Overlay Concept
Architecture Example
Communications Technology Division
Glenn Research Center
Australian
US Division
NSP
Europe
European
HomeNSP
Office
Satellite Networks & Architectures Branch
Asian
AsianPartner
NSP
Common Application Network
Common Voice Network
Priority Command Network
Legacy Networks
Airport Networks
Airline Fleet Network
Concept: Enable unified communications
without impacting existing legacy services
Source: Terry L Davis, Boeing
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
42
Glenn Research Center
Communications Technology Division
Satellite Networks & Architectures Branch
Conceptual v6 Strategic Architecture
Summary
• IP-v6 could provide a seamless NSP control handoffs
• Traffic segregation by network could provide better comm link
mgmt and QoS than IP-v4 (+matches Domain model).
• GPS based v6 addressing could potentially allow significant
control and data routing improvements.
• Layering of v6 networks could allow segregation of networks with
similar capabilities and security levels.
• Security in a v6 architecture could be "network" based.
• “capability/compatibility" layers could allow change/evolution
without updates of products, or fleets.
Source: Terry L Davis, Boeing
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
43
Glenn Research Center
Communications Technology Division
Satellite Networks & Architectures Branch
Conceptual v6 Aviation Strategy
Full conversion is evolutionary over more than 25 years
•
Platforms will requires IP-v6 interoperability before end-of-life
•
Specific customers will require support for v6
•
Timeline to implement is in years from the first start
•
Leverage aviation assets and expertise globally
•
Grow the base of v6 compatible equipment
•
Grow the base of v6 staff skills through industry sponsored training
•
Conversions are based on requirements or business case
•
Regulatory changes will be needed to both allow and support IP-v6
Source: Terry L Davis, Boeing
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
44
References / Useful Links
Communications Technology Division
Glenn Research Center
•
Wesley Eddy, William Ivancic, Joseph Ishac: “Analysis of IPv6 Features
and Usability” Version 1.0 9/6/06
–
•
http://www.ipv6ready.org/logo_db/approved_list.php
The Latest Approved Application List of Phase-2
–
•
https://disronline.disa.mil/a/DISR/docs/secure/DoD_IPv6_Transition_Plan_v2_Final.pdf
IPv6 Ready Logo Phase-1
–
•
https://disronline.disa.mil/a/DISR/docs/secure/DoD-IPv6_Transition_Plan_v1_0_3-24-05_update1.pdf
DoD_IPv6_Transition_Plan_v2_Final
–
•
http://www.nav6tf.org/documents/nav6tf.analysis_ipv6_features_and_usability.pdf
IPv6_Transition_Plan_v1_0_3-24-05
–
•
Satellite Networks & Architectures Branch
http://www.ipv6ready.org/logo_db/approved_list_p2.php
Geoff Mulligan, “IP and 802.15.4 – To V6 or not to V6” (IPv6 for Sensors)
–
http://roland.grc.nasa.gov/~ivancic/hidden/shared/v6%20Seminar.ppt
Airborne Network TIM at LMCO, Chantilly VA Nov 7,2007
45