federal aviation administration faa amhs subnetwork overview sp/2
TRANSCRIPT
Federal AviationAdministration
FAA AMHS Subnetwork Overview
SP/2
Federal AviationAdministration 2
FAA AMHS Subnetwork
The United State Federal Aviation Administration has implemented an AMHS subnetwork configuration that provides flexibility for both the U.S. and its partners, based in part upon the following factors:
1. Regional requirements
2. Needs and preferences of partner states to which the U.S. is connected
3. Cost and other circuit acquisition issues
Federal AviationAdministration 3
FAA AMHS Subnetwork Environment
The following network configuration options currently exist with the FAA AMHS environment:
1. AMHS via an ATN Router over X.25
2. AMHS via an ATN Router over IP-SNDCF
3. AMHS using RFC-1006 over TCP/IP
Federal AviationAdministration 4
AMHS via an ATN Router Over X.25
Message Transfer Agent (MTA)
Presentation Layer
Session Layer
TP0
RFC1006
IPv4
TCPCLNP
TP4
Message Transfer Agent (MTA)
Presentation Layer
Session Layer
TP4TP0
RFC1006
CLNPIPv4
TCP
IP RouterATN
RouterIP Router
ATNRouter
X.25
Federal AviationAdministration 5
AMHS via an ATN Router Over IP-SNDCF
Message Transfer Agent (MTA)
Presentation Layer
Session Layer
TP0
RFC1006
IPv4
TCPCLNP
TP4
Message Transfer Agent (MTA)
Presentation Layer
Session Layer
TP4TP0
RFC1006
CLNPIPv4
TCP
IP RouterATN
RouterIP Router
ATNRouter
IP-SNDCF
Federal AviationAdministration 6
AMHS Using RFC-1006 Over TCP/IP
Message Transfer Agent (MTA)
Presentation Layer
Session Layer
TP0
RFC1006
IPv4
TCP
IP Router IP RouterIP
Message Transfer Agent (MTA)
Presentation Layer
Session Layer
TP0
RFC1006
IPv4
TCP
Federal AviationAdministration 7
FAA AMHS/ATN Router Configuration
ATN Router
AMHS Gateway
AFTN
FAAAtlanta
Network Enterprise Management Center (NEMC)
LANX.25
United Kingdom
IP-SNDCF Australia (2012-2013)
Fiji (March 2012)IP
IP
IP
Federal AviationAdministration 8
FAA AMHS/ATN Router Configuration (Connection #1)
AMHS Gateway
AFTN
FAAAtlanta
Network Enterprise Management Center (NEMC)
LAN
United Kingdom
IP
IP
1. Dictated by regional standard2. No ATN Router3. Numerous firewalls / proxies/ NAT’ing on both ends4. FAA: Circuit troubleshooting requires TelCo support
Considerations in Circuit Selection and Operation
Federal AviationAdministration 9
FAA AMHS/ATN Router Configuration (Connection #2)
ATN Router
AMHS Gateway
AFTN
FAAAtlanta
Network Enterprise Management Center (NEMC)
LANX.25 Fiji (March 2012)
IP
IP
1. Dictated by regional standard2. Use of existing capacity from U.S. to Fiji (minimizes cost and time lag)3. Numerous firewalls / proxies/ NAT’ing on both ends4. FAA: Greater circuit troubleshooting capability by AMHS Ops staff (OSI pings)
Considerations in Circuit Selection and Operation
ATN Router
FAASalt Lake City
Network Enterprise Management Center (NEMC)
X.25
Federal AviationAdministration 10
FAA AMHS/ATN Router Configuration (Connection #3)
ATN Router
AMHS Gateway
AFTN
FAAAtlanta
Network Enterprise Management Center (NEMC)
LAN
IP-SNDCF Australia (2012-2013)
IP
IP
1. Dictated by regional standard2. Preference of remote state (AUS)3. FAA: Significant lead time, but time is available
Considerations in Circuit Selection and Operation
Federal AviationAdministration 11
Conclusion
The FAA’s ATN infrastructure has evolved to provide connection establishment to multiple regions using a variety of protocols and standards, ensuring seamless message delivery across all regions.