Federal Aviation Administration. Connection

Transcription

1 AMHS Implementation Workshop Administration International ti User Connection Miami, Florida, USA April 10-12, 12, 2012

2 Agenda Current AFTN Connections Planned International Connectivity FAA IP Access Future AMHS Connections IP Connections to the NESG IP Address Translation Connections for Testing Summary Administration 2

3 Current International AFTN Connections FAA has implemented AFTN X.25 connections to international partners using its NADIN-II Packet Switched Network Connections were made the convenient NADIN-II node AFTN centers are Atlanta (ATL) & Salt Lake City (SLC) National Enterprise Management Center (NEMC) locations also at ATL & SLC Connections are being consolidated at ATL & SLC Administration 3

4 Previous X.25 AFTN Connections ZAN ARTCC Consolidated Facility ATCSCC NEMC WJHTC Canada NADIN PSN ZSE ZMP Japan South Pacific AFS Network Fiji Australia New Zealand (AMHS) ZOA 19.2kbps 19.2kbps HNL ZLA SLC ZLC ZAB ZDV ZFW x2 ZKC ZAU ZME ZID ATL ZTL ZOB DCC ZJX ZCY ZDC B13 ZBW ZNY Turks & Caicos Portugal Bermuda United Kingdom American Samoa Kwajalein Wake Mexico Brazil ZHU ZMA MEVA-II Peru Venezuela (via Puerto Rico) COCESNA: Honduras, Belize, Guatemala, El Salvador, Nicaragua, Costa Rica Honduras Cuba Jamaica Haiti Cayman Panama St.Maarten Curacao Aruba Bahamas Dominican Republic Antigua (via Puerto Rico) Trinidad (via Puerto Rico) E/CAR Network: (AFTN Piarco, Trinidad): Anguilla, Antigua, St.Kitts&Nevis, Monserrat, Guadeloupe, Dominica, Martinique, St.Lucia, St.Vincent, Barbados, Grenada, Trinidad Administration 4

5 Current X.25 AFTN Connections ZAN ARTCC Consolidated Facility ATCSCC NEMC WJHTC Canada NADIN PSN ZSE ZMP Japan South Pacific AFS Network Fiji Australia New Zealand (AMHS) ZOA 19.2kbps 19.2kbps HNL ZLA SLC ZLC ZAB ZDV ZFW x2 ZKC ZAU ZME ZID ATL ZTL ZOB DCC ZJX ZCY ZDC B13 ZBW ZNY Portugal Bermuda United Kingdom Turks & Caicos ZHU Mexico ZMA Antigua (via Puerto Rico) ATL Ground Station handles MEVA connections COCESNA: Honduras, Belize, Guatemala, El Salvador, Nicaragua, Costa Rica Brazil Honduras Haiti Panama Cuba Jamaica Cayman Aruba Dominican Republic Bahamas Curacao St.Maarten Trinidad (via Puerto Rico) E/CAR Network: (Piarco, Trinidad): Anguilla, Antigua, St.Kitts&Nevis, Monserrat, Guadeloupe, Dominica, Martinique, St.Lucia, St.Vincent, Barbados, Grenada, Trinidad Venezuela (via Puerto Rico) Peru Administration 5

6 Planned International Connections ZAN ARTCC Consolidated Facility ATCSCC NNCC WJHTC Canada ZSE ZMP Japan (AMHS) Japan (AIDC) ZOA SLC ZLC ZDV x2 ZKC ZAU ZID ZOB DCC B13 ZBW ZNY ZDC ZCY United Kingdom Portugal Bermuda 19.2kbps Fij New Zealand i Australia ATL Ground Station handles MEVA connections 19.2kbps HNL ZLA Mexico (MEVA-REDDIG) ZAB Brazil COCESNA: Honduras Honduras, Belize, Panama Guatemala, El Salvador, Nicaragua, Costa Rica Peru (MEVA-REDDIG) ZFW Haiti ZHU Dominican Republic ZME ATL Cuba Jamaica Cayman Aruba ZTL ZJX ZMA Turks & Caicos Trinidad (E-CAR Network) Bahamas Venezuela Curacao St.Maarten (MEVA-REDDIG) MEVA-II Administration 6

7 FAA IP Access AMHS connections will most likely use Internet Protocol (IP) transport for CAR/SAM FAA has a National Airspace System (NAS) IP network FAA has 4 NAS Enterprise Security Gateways (NESG) for boundary protection: Atlanta (ATL) manned 24x7 Salt Lake City (SLC) manned 24x7 Atlantic City, NJ (ACY) manned 8 hours Monday-Friday Oklahoma City, OK (OEX) manned 8 hours Monday-Friday ACY & OEX have Internet access Administration 7

8 FAA External IP Access Points Internet NAS Enterprise Security Gateways ZAN NEMC Oklahoma Atlantic City City ZSE Salt Lake City 24x7 Operations All Gateways can support dedicated circuit access ZOA ZLA SLC ZLC ZAB ZDV x2 ZKC 8-5 M-F OEX ZMP ZAU ZME ZID ZOB ATL DCC B13 ZDC ZBW ZNY ACY WJHTC FNTB Test Bed Atlantic City 8x5 M-F Operations 19.2kbps ZTL HNL Oklahoma City Operations 8x5 M-F ZFW ZHU ZJX ZMA Atlantat 24x7 Operations Administration 8

9 Future AMHS Connections AMHS Gateways & AFTN switches at ATL & SLC ICAO suggests that international connections be made with dedicated circuits (MEVA-II or Telco) FAA recommends that international IP circuits be routed directly to ATL and SLC FAA recommends using BGP-4 routing between States that can be used to monitor links FAA desires to be able to ping States boundary router for troubleshooting Administration 9

10 FAA International User Portal International User Portal is the FAA touch point to the Aeronautical Telecommunications Network (ATN) Dedicated routers at ATL & SLC external to the NESG: Support for any custom IP addressing for individual States Support for CAR/SAM 10. private IPv4 addressing scheme Support for IPv6 inter-regional addressing IPv6 to IPv4 conversion FTI monitoring of IP circuits (through BGP-4 or ICMP ping) Support for legacy X.25 over IP (XOT or STUN) Future transit routing between States Test router at the Atlantic City Technical Center: Easy patching of operational circuits to test facilities Replicated equipment for access to test AMHS facilities Administration 10

11 ATL International User Portal Administration 11

12 Connection Security Architecture External IP sessions are proxied by a non-faa server The non-faa server will forward data to the AMHS Gateway International users will each have a dedicated port# on the non-faa server to access the AMHS Gateway Users will be required to support a port number other than 102 Administration 12

13 IP Connection Architecture Administration 13

14 IP Address Translation Administration 14

15 Test Connectivity FAA performs AMHS testing at the William J Hughes Technical Center (WJHTC) in Atlantic City, NJ WJHTC has an FTI National Test Bed (FNTB) which duplicates the operational IP architecture Test connections to the FNTB AMHS Gateway can be: 1. Via the Internet IPsec (VPN tunnel required) 2. Via patched connections from the International User Portal Administration 15

16 Test Connection Options Option#1: Internet Access Option#2: Operational Circuit Patch Option#2: Also from SLC Administration 16

17 Summary ICAO has mandated that States move to support AMHS/ATN FAA AMHS operational access is by dedicated circuits FAA AMHS Gateways are deployed at Atlanta and Salt Lake City CAR region will use IP transport for AMHS IP Circuits should be routed to Atlanta and Salt Lake City FAA has an International User Portal to support ATN addressing Testing at Atlantic City duplicates the operational IP network Administration 17