icao acp wg-i – nov 2009 industry activity update terry davis boeing urn (geant) comments ip...
TRANSCRIPT
ICAO ACP WG-I – Nov 2009ICAO ACP WG-I – Nov 2009Industry Activity UpdateIndustry Activity Update
Terry DavisTerry Davis
BoeingBoeing
URN (GEANT) CommentsURN (GEANT) CommentsIP Mobility Work StatusIP Mobility Work StatusICANN WorkICANN WorkIPv6 Impact on Aircraft SystemsIPv6 Impact on Aircraft Systems
URN (GEANT) CommentsURN (GEANT) Comments
URN – Namespace management is not formalized URN – Namespace management is not formalized by standardsby standards
Currently done through the publication of Currently done through the publication of Informational RFC’sInformational RFC’s
Aviation registrar? AEEC, ATA, ICAO, ?Aviation registrar? AEEC, ATA, ICAO, ? Lots of policy and process to develop.Lots of policy and process to develop. Impacts of new IDNs?Impacts of new IDNs? Globally scalable?Globally scalable? Queries placed to W3C regarding their stand on Queries placed to W3C regarding their stand on
URN management, awaiting response.URN management, awaiting response.
IP Mobility Work StatusIP Mobility Work Status
Informational RFC 5522 published in Informational RFC 5522 published in October. “October. “Network Mobility Route Network Mobility Route Optimization Requirements for Optimization Requirements for Operational Use in Aeronautics and Operational Use in Aeronautics and Space Exploration Mobile NetworksSpace Exploration Mobile Networks””– Thanks to all who contributed and commented Thanks to all who contributed and commented
especially to Wes Eddy and Will Ivancicespecially to Wes Eddy and Will Ivancic
IP Mobility Work StatusIP Mobility Work Status
Work continues in MEXT working group.Work continues in MEXT working group. Discussions of how to support dual-homing for Discussions of how to support dual-homing for
aviation (ground ruled out of original work)aviation (ground ruled out of original work) All solutions require extensive use of IPSecAll solutions require extensive use of IPSec Interoperability issues with PKI and IPSec NOT Interoperability issues with PKI and IPSec NOT
being addressed by IETFbeing addressed by IETF ICANN restrictions on aircraft mobile routing ICANN restrictions on aircraft mobile routing
implementations due to BPG table churn - implementations due to BPG table churn - Requested addition to ICANN strategic planning Requested addition to ICANN strategic planning work.work.
IP Mobility Work StatusIP Mobility Work Status
Next “Ranger” draft for v4/v6 routing arch.Next “Ranger” draft for v4/v6 routing arch.– https://datatracker.ietf.org/drafts/draft-templin-rahttps://datatracker.ietf.org/drafts/draft-templin-ra
nger/nger/
Continued work on HIP (Host Identity Continued work on HIP (Host Identity Protocol). Combines identity, Protocol). Combines identity, authentication, encryption, & v4-v6 comm.authentication, encryption, & v4-v6 comm.
IETF action and direction on next generation IETF action and direction on next generation routing expected in late 2010routing expected in late 2010
IP Mobility Work StatusIP Mobility Work Status
IP Security Protocols Interoperability IP Security Protocols Interoperability Workshop – Nov 3, 2009 SeattleWorkshop – Nov 3, 2009 Seattle
Aviation – Boeing, SITA, Honeywell, UPS, Aviation – Boeing, SITA, Honeywell, UPS, NASA, United, Delta, and ContinentalNASA, United, Delta, and Continental
Government – NSA, NISTGovernment – NSA, NIST Academia - UW, UNHAcademia - UW, UNH Vendors – Microsoft, Cisco, Juniper, Aruba, Vendors – Microsoft, Cisco, Juniper, Aruba,
F5, ICSA Labs, SonicWall, StoneSoft, F5, ICSA Labs, SonicWall, StoneSoft, McAfee, Verizon McAfee, Verizon
IP Mobility Work StatusIP Mobility Work Status
IP Security Protocols Interoperability IP Security Protocols Interoperability Workshop – Nov 3, 2009 SeattleWorkshop – Nov 3, 2009 Seattle
Outcomes:Outcomes: Working group formingWorking group forming Initial target – NSA IPSec Suite B 2011Initial target – NSA IPSec Suite B 2011 UW initiating R&D scoping – Output in DecUW initiating R&D scoping – Output in Dec Anticipate follow-on meeting 1Q2010Anticipate follow-on meeting 1Q2010 Precede or follow NIS?Precede or follow NIS?
ICANNICANN
ICANN restrictions on aircraft mobile routing ICANN restrictions on aircraft mobile routing implementations due to BPG table churn - implementations due to BPG table churn - Requested addition to ICANN strategic planning Requested addition to ICANN strategic planning work.work.
(TLD – DNS Top Level Domain Names – i.e. .aero )(TLD – DNS Top Level Domain Names – i.e. .aero )
(IDN – Use of non-latin based scripts for naming)(IDN – Use of non-latin based scripts for naming) IDN ccTLDs – Release on Nov 19IDN ccTLDs – Release on Nov 19thth
gTLDsgTLDs IDN-gTLDs IDN-gTLDs
ICANNICANN
New IDNccTLD, gTLDs, IDNgTLDs will New IDNccTLD, gTLDs, IDNgTLDs will require also:require also:– DNSSec, IPv6 reachability, IPv6 Name DNSSec, IPv6 reachability, IPv6 Name
Resolution, new DNS root infrastructure, and Resolution, new DNS root infrastructure, and new allocation processes.new allocation processes.
– Impacts to interoperability and security Impacts to interoperability and security
IPv6 address allocation policies changingIPv6 address allocation policies changing IPv6 will start next year – v4 allocation cutoffIPv6 will start next year – v4 allocation cutoff
ICAO 9896 Follow-on Standization?ICAO 9896 Follow-on Standization?
ICAO IPv6 Address AllocationICAO IPv6 Address Allocation IPv6 Network Architecture Design GuidanceIPv6 Network Architecture Design Guidance PKI and IPSec Implementation GuidancePKI and IPSec Implementation Guidance Aircraft Naming/Identity for PKI UseAircraft Naming/Identity for PKI Use Aircraft IPS Naming (DNS) StructureAircraft IPS Naming (DNS) Structure IPS DNS Implementation GuidanceIPS DNS Implementation Guidance IPv4 – IPv6 Transition GuidanceIPv4 – IPv6 Transition Guidance
IPv6 Impact on Aircraft SystemsIPv6 Impact on Aircraft Systems
Impacts of 64 bit unit address to hardware?Impacts of 64 bit unit address to hardware? Development of onboard addressing mechanisms Development of onboard addressing mechanisms
(assigned addressing not recommended)(assigned addressing not recommended) Requires DNS and DynamicDNS (MEXT)Requires DNS and DynamicDNS (MEXT) Development of onboard and offboard DNS Development of onboard and offboard DNS
structures and naming standardsstructures and naming standards Evaluation of the need for DNSSecEvaluation of the need for DNSSec Common security architectureCommon security architecture
IPv6 Impact on Aircraft SystemsIPv6 Impact on Aircraft Systems
Onboard and offboard routing protocolsOnboard and offboard routing protocols Routing securityRouting security v6 Network architecturev6 Network architecture Transition architecture requirement?Transition architecture requirement? v4-v6 connectivity solutionsv4-v6 connectivity solutions v6 Address allocations from: ICAO – ATM, v6 Address allocations from: ICAO – ATM,
AOC – ICAO/airline/ISP?, PIES - AOC – ICAO/airline/ISP?, PIES - ICAO/airline/ISP/IFE?, ICAO/airline/ISP/IFE?,
SummarySummary
Lots of R&D work to doLots of R&D work to do
Questions?Questions?