ARINC 830 AGIE Specification Outline & Notes

1. ARINC 830 AGIESpecification Outline&Notes By: Rick Wilber – Boeing – 206-931-5561 With: Wolf Sonnenberg – Teledyne - 310-765-3745 Version: June 14, 2013

2. ARINC 830 Specification Notes • Goal is full draft in June and final in October • The specification has been updated per 5/29/13 Telecon • Spec changes for preparation • Reformatted diagrams • Bold & italics to see “shalls” • Cleaned up AMQP references • Fixed various typo’s & word-smithing • Wolf made significant contributions to wording in section 1-3 • Added TBD • Status • Sections 1, 2 & 3 are complete with actions • Section 4 & 5 are draft ready for review except where noted • Section 6 is structurally complete with interfaces placeholders • Appendices • Glossary is complete • Threads ready for review & tighter mapping to AMPQ appendix • AMQP thread mapping is placeholder

3. Spec Top Level Section Outline • Introduction • Purpose & Objectives • All business and level discussions • Introduction oriented not technically oriented • No shalls • AGIE Overview • Overview capabilities from user perspective • User oriented not technically oriented • Describe operational concepts, approach • No shalls • Functional specification • All technical discussions with functional view • Developer focus • All functional shalls • AGIE Operations • Operators perspective • All operational shalls • No functions • How to use AGIE • Protocol interfaces • Functional interfaces between components • Functional interfaces to external components • XML interfaces for messages • Database descriptions • No shalls • Appendices • Glossary • Threads • AMQP thread mapping • AGIE Interface Definitions • Papers references • Considerations for AGIE Certification and Approval • AGIE DNS Use • Deferred AGIE Features • AGIE Demonstration and Testing Scenarios • AGIE Topologies • AGIE Use Cases

4. ARINC 830 Specification Status • Major writing tasks remaining • AMQP section development • 4.6.4 function mapping • 5.1.1 operational considerations • Appendix C thread mapping for functional flows • Will cause Appendix B update • Validate protocol & interface lists • Describe protocols & interfaces • Client XML interface templates • Coordination interface templates • Coordination database definitions • Appendix D AGIE interface definitions • Each XML, coordination message & database will defined

5. ARINC 830 Specification Status • Major review tasks remaining • Section 4 • Review all concepts • Validate all requirements • Fill in TODOs • Section 5 • Review all concepts • Validate all requirements • Fill in TODOs • Ensure appropriate scope (need ops inputs) • Section 6 • Review concepts & text • Validate interface lists • Define each interface & protocol • Validate them against sections 4 & 5 • Appendices • After AMQP threads update AGIE threads • After XML definitions make sure semantics flow

6. Section Status • Introduction • Purpose • Scope • Overview • Related documents • Regulatory • Compliance • Purpose & Objectives • Objectives • Benefits • Approach • Data exchange • Concept of operations approach • Development & validation • Interoperability • Policy considerations • Operational (cost, performance, QoS) • Certification & approval • Security approach • Key • Placeholder – no or limited text • Partially complete – some text, more work needed • Draft - all text ready for initial review • Final Review – completed waiting for final review • Complete – updated only as errors, changes required • AGIE Overview • General description • Client-server • Service oriented • Priorities, paths, naming concepts • Terminology • Architecture & topologies • Components, functions, interfaces • Admin concepts • Messaging operations • Principles of operation • AGIE organization • Connection management • Protocol binding • Addressing • Data delivery • Prioritization • Message management • List of operations

7. Section Status • AGIE functions • Client functions • Server functions • System and Primary functions • AMQP functions • Security requirements • AGIE Operations • System setup • AMQP configuration • Configuration management • Naming • Priorities • Paths • Security & partitioning • Use case overview • Key • Placeholder – no or limited text • Partially complete – some text, more work needed • Draft - all text ready for initial review • Final Review – completed waiting for final review • Complete – updated only as errors, changes required • Functional specification • Top-level capabilities • Architecture • Clients • Servers • Topologies • Cross domain • AGIE-AMQP • Architectural security • Paths & routing • IP routes • Connections • Paths & selection • Messaging & delivery • Interface • Attributes • Services • Flow control & priorities • Naming & addressing processing • Name space • Considerations • AGIE descriptor • Parsing • Name resolution • Address resolution • AGIE name service

8. Section Status • Appendices • Glossary • AGIE Threads • AMQP thread mapping • AGIE interface definitions • Key • Placeholder – no or limited text • Partially complete – some text, more work needed • Draft - all text ready for initial review • Final Review – completed waiting for final review • Complete – updated only as errors, changes required • Protocol interfaces • XML interfaces • App-client-host interface XML • Host-to-AGIE client-to-app XML • Coordination messages • Server – server • Sort list of services • Coordination databases • Clients DB • Servers DB • Current associations DB • Connection profiles DB • Current paths DB • Message types DB • Best Path selection Table DB