ATN Topology Considerations for Aeronautical NEMO RO draft-bauer-mext-aero-topology-00 Christian Bauer, Serkan Ayaz 72nd IETF, MEXT WG

Overview Draft tries to provide an overview of the Aeronautical Telecommunications Network (ATN) Focus is on –Air Traffic Services (ATS) –Airline Operational Services (AOS) –ignores Passenger Communications Terminology, involved nodes Networks Certificates

Networks Air Communications Service Provider (ACSP) –like an Internet Service Provider in the „normal“ world –Operates air/ground access network(s) –Airline chooses one of them for AOS Air Navigation Service Provider (ANSP) –Manages air traffic: FAA, Eurocontrol, DFS, AENA, etc. –Will have to provide air/ground communications network in the future (at least in Europe) Either by running it‘s own a/g access network Or by contracting an ACSP

Points Of Attachement and communication flow ATS

Points Of Attachement and communication flow /2 AOS

Trust Relationships Airlines always contract an ACSP (due to AOS) Each ANSP also has a relationship to an ACSP PKI discussion –Mentioned in requirements document –As of now: no PKI (single root or bridge CA) that covers all ACSP, ANSP and Airline entities/networks –Future: ? Currently: X.509 certificates for Secure ACARS –For AOS, End2End: MNN and CN both belong to airline –CA can be Airline itself or Service Provider

Questions / Discussion LMNs within ATS/AOS domain –Mentioned because it is stated like this in the Reqs-document –Relevant for AOS –Not for ATS (!) HA location –ACSPs are the air/ground communications providers –Airlines already have contracts to ACSPs anyway (for AOS) –Cost: redundancy, high-availability –Even large airlines have <1000 aircraft Aircraft without ACSP –And therefore without MSP

Thanks This work has been partially supported by the European Commission through the NEWSKY project.