A QoS Plan for IP-based Data Sharing Between the GIG and SWIM

A QoS Plan (QoS-P) uses networking resources intelligently and dynamically, rather than using a hardware surfeit to achieve similar results. As more real-time applications are deployed in an IP setting, implementations of historical IP “best efforts” QoS do not suffice—in an IP-based network, especially one employing TCP, a QoS-P cannot simply emphasize control of the topological path and timing of differing protocols/data types—unknown future participants are able to alter QoS-P efficacy unless governance requires entrance into a known SLA creating end-to-end functionality. This possibility for change is inherent to IP’s historical vision and purpose as the “common glue” for diverse and transparent protocols, unlike predecessor ARPANET, which left reliability to its hosts. Topia acknowledges that network QoS is an essential function of IP and that hosts must be included in any comprehensive QoS-P. A QoS-P could not be built for IP in a random system. However, GIG and SWIM are net-centric and service-oriented, with SLAs (within the SOA service contracts) at their interfaces, and this makes a realistic network-wide QoS-P possible. This proposal ties these aspects of IP and of more traditional QoS-Ps to develop a realistic QoS-P for the transfer of radar data between GIG and SWIM.