1. ICAO ACP WG-I – Nov 2009 Industry Activity Update
URN (GEANT) Comments IP Mobility Work Status ICANN Work IPv6 Impact on Aircraft Systems
Terry Davis
Boeing

2. URN (GEANT) Comments
URN – Namespace management is not formalized by standards
Currently done through the publication of Informational RFC’s
Aviation registrar? AEEC, ATA, ICAO, ?
Lots of policy and process to develop.
Impacts of new IDNs?
Globally scalable?
Queries placed to W3C regarding their stand on URN management, awaiting response.

3. IP Mobility Work Status
Informational RFC 5522 published in October. “Network Mobility Route Optimization Requirements for Operational Use in Aeronautics and Space Exploration Mobile Networks”
Thanks to all who contributed and commented especially to Wes Eddy and Will Ivancic

4. IP Mobility Work Status
Work continues in MEXT working group.
Discussions of how to support dual-homing for aviation (ground ruled out of original work)
All solutions require extensive use of IPSec
Interoperability issues with PKI and IPSec NOT being addressed by IETF
ICANN restrictions on aircraft mobile routing implementations due to BPG table churn - Requested addition to ICANN strategic planning work.

5. IP Mobility Work Status
Next “Ranger” draft for v4/v6 routing arch.
Continued work on HIP (Host Identity Protocol). Combines identity, authentication, encryption, & v4-v6 comm.
IETF action and direction on next generation routing expected in late 2010

6. IP Mobility Work Status
IP Security Protocols Interoperability Workshop – Nov 3, 2009 Seattle
Aviation – Boeing, SITA, Honeywell, UPS, NASA, United, Delta, and Continental
Government – NSA, NIST
Academia - UW, UNH
Vendors – Microsoft, Cisco, Juniper, Aruba, F5, ICSA Labs, SonicWall, StoneSoft, McAfee, Verizon

7. IP Mobility Work Status
IP Security Protocols Interoperability Workshop – Nov 3, 2009 Seattle
Outcomes:
Working group forming
Initial target – NSA IPSec Suite B 2011
UW initiating R&D scoping – Output in Dec
Anticipate follow-on meeting 1Q2010
Precede or follow NIS?

8. ICANN
ICANN restrictions on aircraft mobile routing implementations due to BPG table churn - Requested addition to ICANN strategic planning work.
(TLD – DNS Top Level Domain Names – i.e. .aero )
(IDN – Use of non-latin based scripts for naming)
IDN ccTLDs – Release on Nov 19th
gTLDs
IDN-gTLDs

9. ICANN New IDNccTLD, gTLDs, IDNgTLDs will require also:
DNSSec, IPv6 reachability, IPv6 Name Resolution, new DNS root infrastructure, and new allocation processes.
Impacts to interoperability and security
IPv6 address allocation policies changing
IPv6 will start next year – v4 allocation cutoff

10. ICAO 9896 Follow-on Standization?
ICAO IPv6 Address Allocation
IPv6 Network Architecture Design Guidance
PKI and IPSec Implementation Guidance
Aircraft Naming/Identity for PKI Use
Aircraft IPS Naming (DNS) Structure
IPS DNS Implementation Guidance
IPv4 – IPv6 Transition Guidance

11. IPv6 Impact on Aircraft Systems
Impacts of 64 bit unit address to hardware?
Development of onboard addressing mechanisms (assigned addressing not recommended)
Requires DNS and DynamicDNS (MEXT)
Development of onboard and offboard DNS structures and naming standards
Evaluation of the need for DNSSec
Common security architecture

12. IPv6 Impact on Aircraft Systems
Onboard and offboard routing protocols
Routing security
v6 Network architecture
Transition architecture requirement?
v4-v6 connectivity solutions
v6 Address allocations from: ICAO – ATM, AOC – ICAO/airline/ISP?, PIES - ICAO/airline/ISP/IFE?,

13. Summary
Lots of R&D work to do
Questions?