Title: EUROCONTROL Focus on Air Traffic Control
1EUROCONTROLFocus on Air Traffic Control
Convergence New opportunities for Accelerating
the IPv6 momentum 1-2 June 2006, Vienna Eivan
Cerasi Communications Domain, DAS/CSM
European Organisation for the Safety of Air
Navigation
2Strong Air Traffic Growth in Europe
- Air Traffic in Europe will double within the next
20 years (2000 -gt2020)
3Air Traffic Control
European Organisation for the Safety of Air
Navigation
4ATC Communications in the Air
- ATC Communications requires Quality Of Service
- Largely based on analogue voice communications
over VHF and HF (oceanic) - Requires global co-ordination led by the
International Civil Aviation Organisation (ICAO) - Data link services have started to be deployed
5Operational CPDLC in the Cockpit
6Status in the Air
- CPDLC makes use use of ICAO Aeronautical
Telecommunication Network (OSI) over a VHF data
link (VDL2) - Narrowband
- Independent of other on-board data communications
services such as - Passengers (satcom)
- Airline Communications (ACARS)
- Several on-going intiatives
- Investigations into wide-band technologies for
air/ground ATC communications - Continuous trials worldwideUMTS, US Coast Guard,
NASA, - ICAO considering to define new IPv6-based
standards for the ATN - Slow process avionics certification, retro-fit
costs, etc.
http//www.eurocontrol.int/link2000
7On the Ground mixed X.25 and IPv4
- International Data
- ATC over X.25
- Application-specific IP VPN
- National Services
- Internal IP/X25 applications
- X25 Links to SITA/ARINC
- Management, etc..
8IPAX Task Force Trials (2001-2004)
- WAN trials to support RD activities to plan
migration from X.25 to IP - 12 European ANSPs, 22 logical interconnections
- various lower media (VPN, Internet, LL, ISDN, MW)
- 14 European sites NASA connected via IPv6
- Directory services (DNS)
- IP security (IPsec and firewalls)
- X.25 over TCP/IP
- ATC Applications
9Our Rationale for IPv6
- Re-numbering is not acceptable to overcome IPv4
address conflict - Multiple layers of IPv4 NAT over-complicate the
architecture and difficulty to find a common
address pool for a double NAT environment between
conflicting routed domains - End-systems that require international access
should be dual-stacked (IPv6 is defined as the
standard network protocol to which all
applications should converge to ensure
interoperability) - Trials prove that in our context, international
Multicast, VoIP and MobileIP are best supported
over IPv6 - Trials prove NAT-PT is compatible with our
unicast applications, so even if we have to do
NAT why not NAT to IPv6 (NAT-PT) ?
10Other Motivations for IPv6
- Deployment Issues
- IPv6 does provide a valid long-term architecture
(due to deployment cycles) - Trials prove that we can handle a transition
phase over a long period - Minimise exposure to IPv6 to reduce market
risks - Own a /32 to ensure telecom provider IP address
independence - IPv6 is not vendor dependent
- Global/Regional Issues
- Future IP for air/ground communications is likely
to be IPv6 based - EUROCAE WG67 is investigating the use of VoIP for
ATC (likely to be IPv6) - IPv6 pick-up rate
11Deployment Actions
- 2005-2009
- X25 -gt IP migration has already started leading
to a mixed X.25/IPv4/IPv6 environment - PEN Project still in a scope definition phase
- 2006 Pan-European Network Call for Interest
- 2007 Pan-European Network Call for Tender
- 2008 Deployment of Pan-European Network and
operational evaluation/validation - Summer 2008 initial operations
- 2010 Application and Service extension
- Voice, A/G applications, International Multicast,
.
12What is PEN
- Pan European IP network service of the ATM sector
which will ultimately carry all data and voice
applications - A procured multi-protocol managed service
(supporting both IPv4 and IPv6) to initially
provide (as a minimum) the data backbone to
interconnect existing IP networks - Overtime to be scaled to include multicast and
voice at a later stage - http//www.eurocontrol.int/corporate/public/standa
rd_page/bwu_welcome.html
13Ground Applications IPv6
- EU Single European Sky Implementing Rule on
Flight Message Transfer Protocol (FMTP) - Forthcoming Rule mandating a EUROCONTROL FMTP
Specification (IPv6) - Some stakeholders ready for operations
- EUROCONTROL Introduce both IPv4 and IPv6 in
communications and surveillance products under
its remit - Worldwide ICAO Aeronautical Communications Panel
(ACP) - Drafting of new networking standards and
recommendations based on IPv6 - First operational deployment of Air Traffic
Services Message Handling System (AMHS) based on
the outcome of the iPAX trials making use of IPv6
14More information
- Contact
- Eivan CERASI
- Email eivan.cerasi_at_eurocontrol.int
- Telephone 32 2 729 3791
- EUROCONTROL Network SubDomain
- http//www.eurocontrol.int/communications/public/s
tandard_page/com_network.html