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

4.0 AGIE FUNCTIONAL SPECIFICATIONARINC PROJECT PAPER 830 – Page 413. Manage time-to-live by standard default, which the admin may override, bymessage type.4. Automatic message deletion after delivery and/or timeout. Originator mayrequest message deletion or request status any time after the message issent (until the message expires).5. Message persistence, which is default to NO-CHECKPOINT, where theoriginator may request persistence to check point it when possible byservers with access to persistent store. This allows very important messagesto reduce the likelihood of being lost and unrecoverable.COMMENTARYIt is not a requirement (except logging) for any data to be consideredpersistent. This is a request, which may or may not be honored by any AGIEnode handling the message based on the node’s AMQP durabilitycapabilities and settings.What happens when a message times out is left to implementation (other thandefined logging, reporting, and deletion). The implementation may simply delete themessage, query the application, or process the message in some other way for resubmission.The minimum or default is to simply delete the message and ifreporting, status, or logging is requested, follow that line of response.AGIE provides for message persistence using AMQP durability settings. Not allAGIE servers or AMQP brokers will have access to persistent storage. AGIEpersistence is managed in the XML templates via a standard message field called“Checkpoint” that when set, requests the message be check pointed any time thedestination is not immediately reachable. This is important for critical logging events,such as security events. One task of association is reporting status of storedmessages, which include check pointed messages not yet delivered as well asmessage segments received but not completed.AGIE shall provide logging function that provides logged events to an external logfunction via Log Client. AGIE does not define what happens to these logged eventsoutside of AGIE.4.4.3 Message Service ConsiderationsEach messaging service has unique considerations.4.4.3.1 Immediate MessagingImmediate messaging is a service defined to provide real-time like capabilitieswithout adding strict real-time requirements to AGIE. This service is defined simplyas a high priority message with an immediate (zero) “time-to-live.” Immediatemessages have the guarantee of real-time response to success or failure. Thissupports applications such as chat-like services and low latency aviation messages,where it is important to either have a real-time AGIE service or real-time (immediate)response, be it positive or negative. AGIE shall provide immediate messagingservice. AGIE implementation shall include provisions that are aimed at minimizinglatency when processing for immediate messaging.