(AGIE) Using Internet Protocols - Aviation Committees - AEEC - AMC

4.0 AGIE FUNCTIONAL SPECIFICATIONARINC PROJECT PAPER 830 – Page 33onboard aircraft using ARINC Specification 664 addressing conventions. SeeSection 4.5 for detailed discussion on AGIE name space and namingconsiderations.4.2.3 Topology ConsiderationsThe following topologies describe a method of distributing AGIE functionality. It islikely that some airlines will require a melding of multiple topologies. AGIE shallpermit the implementation of mixed topology architectures, e.g.:1. All aircraft with a single AGIE server2. Some aircraft with multiple AGIE servers3. Some aircraft with only AGIE clients onboardAGIE implementation topologies can change over time. As newer aircraft with moreAGIE and connectivity come into an airline’s fleet, a more robust topology may beexpected. For example, early on in AGIE deployment there may be only a fewaircraft with onboard servers, many aircraft with only onboard clients, and evensome aircraft without in flight connectivity. Over time this will shift until the oppositebecomes true. Therefore, it is essential for AGIE to support such complex, mixedtopology implementations for the foreseeable future.The baseline AGIE topology is easily understood as a system with a single groundserver and a single server on each aircraft and multiple clients. Figure 3 depicts thistopology.Figure 3 – AGIE Topology