CoAX - Coalition TIE Briefing DARPA CoABS PI Meeting AFRL Rome, AIAI, Boeing, Dartmouth, DERA Malvern, Lockheed Martin ATL, Michigan, MIT Sloan, Stanford, USC/ISI, UWF/IHMC Support from GITI, ISX, Mitre Coalition Agents eXperiment (CoAX) Supported by the DARPA CoABS Program

CoAX /10 August 2000 Briefing Supported by the DARPA CoABS Program CoAX Briefing Outline u Overview u Key Coalition and Technical Drivers u Binni Scenario u CoAX Components u Domain Management u Demonstrations u 6 Month Demonstration Report u 9, 18 and 30 Month Demonstration Plans u Status and Next Steps

CoAX /10 August 2000 Briefing Supported by the DARPA CoABS Program CoAX Aim of Coalition TIE u Aim: u Address unique aspects of coalition operations through the development and evaluation of agent domain and task management services. u Aim will be met through delivery of: u Phased technical demonstrations of increasing complexity u Technical reports and research papers u Coalition-oriented grid services u Requirements u Use of existing military applications (MBP, CAMPS) u Use of heterogeneous set of both domain-aware and ‘come-as-you-are’ grid agents

CoAX /10 August 2000 Briefing Supported by the DARPA CoABS Program CoAX Key Coalition Drivers u Different doctrine, decision making, rules of engagement and, in general, mission “agendas”. u Different technology skill and equipment levels. u Different cultures and languages. u Questionable compatibility of respective national information systems. u Limited models for coalition force operations. u Command authorities - agreement and transfers. u Variable reliability of components and infrastructures. u Information systems resource sharing agreements and capacity. u Different interpretation of situational information. u Lack of compatible security architectures. From LeRoy Pearce (Canadian MOD), 1999

CoAX /10 August 2000 Briefing Supported by the DARPA CoABS Program CoAX Key Technical Drivers u Working with agents in multiple dynamic domains. u Need for partial (secure) sharing and visualization of processes, data and facilities. u Need flexible interagent task and process management. u Unclear and/or emerging objectives and tasking. u Cannot assume compatibility or complete reliability of functional capabilities, communications, security arrangements or information resources. u Need to integrate and use legacy systems. u Need for rapid formation and management of agent relationships. u Need to respect national concerns, limitations, cultural and political differences, etc.

CoAX /10 August 2000 Briefing Supported by the DARPA CoABS Program CoAX Binni - Gateway to the Golden Bowl of Africa Rathmell, R.A. (1999) A Coalition Force Scenario 'Binni - Gateway to the Golden Bowl of Africa', in Proceedings of the International Workshop on Knowledge-Based Planning for Coalition Forces, (ed. Tate, A.) pp , Edinburgh, Scotland, 10th-11th May 1999.

W E N S Geography Binni - All Features BANDARPopulation centres × Military airfieldsGravel roads Brongo Ports Q Civilian AirfieldsTracks KEY Tarmac roads 175 Heights (metres)Railways LAYERS: Return Cape Vincent Cape Amstado Caca Kaso Lagoon Amisa Jacal Pra Ankobra Tana Ofin Afram Daka Black Caca Kapowa White Caca Mawli LAKE CACA Water Brongo Ports Q Civilian AirfieldsTracks Q Q Q Q Q Q × × × × × Transport WESTERN REGION AGADEZ Zingato SIKASSO COSTA DEL MARIA LAKI BANDAR UGWULU UPPER REGION NORTHERN REGION CACA REGION EASTERN REGION CACA REGION ASHANTI REGION CENTRAL REGION BANDAR REGION AGADEZ GAO Kwanabouri Gambaga 268 Masembi Gambaga Escarpment Higgville Libar Zatu To Cunmege To Tifillo Dinga Anala Akwapim-Gao Range Kwahu Plateau To Pample To Segumbo Kamongo Jinja Brongo Laval Biloo Sagiba Bave Gamba Kolla Antok Grandville Hakkali To Cecil Dado Minga Kaso Nanga Caca Dam Esuko Blackman Laponga Zaribe Bonrope Tonka 775 Atewa Ranga Saltpond Achobo Adaido Diplombo Elmina Wonka Deanville Sonara Sandosta Komenda Gonobo Grandvache Polia Jamestown Slabo Donga Anguiba Kutchi Akimbo Sago- town Wazilla Suthertown Bisa Wampimba Belucar Salisbury Bisha St Andrews Sellerham Kingtown To Petit Paris To Escallope Lissa Libretto Slafito Langford To Falo Asoba Nedalla Epidurango Aida To Harra Names Setting Lat / Long Lat / Long 31E 36E 35E 34E 33E 32E 39E 38E 37E 36E 35E 34E 33E 32E 31E 39E 38E 37E 17N 16N 15N 20N 19N 18N 17N 16N 15N 19N 18N 21N

W E N S Cape Vincent Cape Amstado Caca Kaso Lagoon Amisa Jacal Pra Ankobra Tana Ofin Afram Daka Black Caca Kapowa White Caca Mawli LAKE CACA Gao forces Agadez forces Fire Storm Forces separated by fire storm

W E N S Cape Vincent Cape Amstado Caca Kaso Lagoon Amisa Jacal Pra Ankobra Tana Ofin Afram Daka Black Caca Kapowa White Caca Mawli LAKE CACA Gao forces Agadez Forces Fire Storm False Agadez forces False Gao forces Gao deception is intended to displace firestorm: separation fails.

CoAX /10 August 2000 Briefing Supported by the DARPA CoABS Program CoAX CoAX Components u Agent management services u KAoS domain and resource management (Boeing, IHMC) u Exception handling (MIT) u Task management services u Task and process management (AIAI) u Plan deconfliction (Michigan) u Market-based incentive management (Stanford) u Domain-aware grid agents u MBP (DERA) u CAMPS (AFRL) u Malicious agents (IHMC, Boeing) u Various information, monitoring, visualization, and observer agents u “Come-as-you-are” grid agents u EMAA/CAST AODB info agent (LM-ATL) u Ariadne Web-enabled weather agent (USC/ISI) u Observer agents (Dartmouth)

CoAX /10 August 2000 Briefing Supported by the DARPA CoABS Program CoAX Briefing Outline u Overview u Key Coalition and Technical Drivers u Binni Scenario u CoAX Components u Domain Management u Demonstrations u 6 Month Demonstration Report u 9, 18 and 30 Month Demonstration Plans u Status and Next Steps

CoAX /10 August 2000 Briefing Supported by the DARPA CoABS Program CoAX Agent Domains DM An agent domain consists of one or more agents registered with a common Domain Manager which provides for common administration and enforcement of domain-wide, VM- specific, and agent-specific policies.

CoAX /10 August 2000 Briefing Supported by the DARPA CoABS Program CoAX Agent Domain Management in CoAX u Broadens typical distributed security concerns to include: u Communication and access management: Who can communicate with whom for what services? u Registration management: Who can join the domain under what circumstances? u Resource management: Who can have which kind and how much of a given computing resource? u Mobility management: Who can move where under what circumstances? u Conversation management: What constraints govern interaction between conversing agents? u Obligation management: Who is not meeting commitments? Initial capability shown in six-month demo Initial capability slated for nine-month demo Initial capability slated for demos

CoAX /10 August 2000 Briefing Supported by the DARPA CoABS Program CoAX Native Mech Native Mech Other Guard Policy Management Framework Policy Admin Tool Policy Admin Tool Java VM Guard Aroma VM Guard Servlet RMI KAoS Domain Manager KAoS Domain Manager HTTP Agent Policy Directory Agent RMI JNDI Guard is responsible for: 1. Interpreting policy 2. Enforcing with appropriate native mechanism 1. Abstract, mechanism- neutral representation/XML syntax (DAML collaboration) 2. Distributed networked availability 3. Secure 1. Ensures policy consistency at all levels 2. Stores policy changes 3. Notifies guards Authorized user makes changes over the Web Event-driven policy changes

CoAX /10 August 2000 Briefing Supported by the DARPA CoABS Program CoAX Policy Enforcement Problems and Solutions u u Problem: Enforcing policies on unmodified, potentially malicious agents u Solution: Platform-based enforcement (e.g., Java 2 security) u Problem: Permissions granted statically according to code source (can’t have different permissions for two agent instances from same code base) u Solution: Hack JAAS (Java Authentication and Authorization Service) to allow dynamic permissions and instance-level authentication and authorization u Problem: High-level agent security requirements do not always map to low-level built-in Java security mechanisms u Solution: Lock down permissions of untrusted (agent) code and force agent to use a trusted privileged-code wrapper under control of the guard (eventually to be packaged as domain-aware “grid helper”) to perform selected actions u Problem: Fine-grained resource allocation and control and revocation of permissions in the face of denial-of-service attacks u Solution: Run agent under Java-compatible Aroma VM allowing dynamic fine-grained resource rate and quantity control u Problem: “Obligation policies” cannot be enforced by preventing actions in advance but only by monitoring and after-the-fact sanctions u Solution: Sentinel-based policy enforcement (relevant work in this area by MIT)

CoAX /10 August 2000 Briefing Supported by the DARPA CoABS Program CoAX Briefing Outline u Overview u Key Coalition and Technical Drivers u Binni Scenario u CoAX Components u Domain Management u Demonstrations u 6 Month Demonstration Report u 9, 18 and 30 Month Demonstration Plans u Status and Next Steps

CoAX /10 August 2000 Briefing Supported by the DARPA CoABS Program CoAX Demonstration Schedule u u 1-month demo at kick-off in February 2000 showing direct connection between DERA MBP and LM ATL AODB. u u 6-month demo (internal milestone) in July 2000 showing initial integration of selected CoAX components for 9-month demo. u u 9-month demo (deliverable) in October 2000: u u Brief the CoAX TIE and Binni scenario; u u Show full integration of selected CoAX components; u u Show that selected components interoperate in a Binni-based scenario and that a relevant 'story' can be told about agent functionality; u u Additional stand-alone demos of other components. u u 18-month demo in July 2001 showing full integration of all CoAX components in a rich coalition scenario: u u Focal point to engage other nations and research teams. u u 30-month demo in July 2002 showing dynamic aspects of domain management and tasking.

CoAX /10 August 2000 Briefing Supported by the DARPA CoABS Program CoAX 6-Month Demonstration Report u u Overall Objective: u u Integrated Binni scenario demonstration centered on MBP containing Process Panel monitoring and multiple information-providing agents showing dynamic communication policy management between three KAoS domains on the grid u u Specific accomplishments: u u Binni scenario information used to populate MBP, PP, and LM-ATL agents and shape storyboard u u Domain-aware conversational grid agents registered in three separate KAoS- managed domains representing coalition function units and countries u u KAoS matchmakers transparently federate across domain boundaries consistent with current domain policy u u LM-ATL ‘come-as-you-are’ message-based grid agent interacts with domain-aware agents u u Tasking and control across coalition functional units u u Visualization of coalition C2 process via a simple process model u u Use of simple web-based policy administration tool to change domain policies and update policy enforcement mechanisms to selectively block and unblock interdomain agent communication

CoAX /10 August 2000 Briefing Supported by the DARPA CoABS Program CoAX JTF HQ JFAC HQ Gao Intel 6-Month Integrated Demo Structure ‘Come-as-you-are’ message-based grid agents AODB LM-ATL Db ii PP' Domain-aware conversational grid agents Db i MBP Intel1 Intel2 DM2 MM2 DM3 MM3 DM1 MM1

CoAX /10 August 2000 Briefing Supported by the DARPA CoABS Program CoAX 9-Month Demonstration Plan u u Overall Objective: u u Integrated Binni scenario demonstration with MBP/CAMPS link containing PP monitoring, information-providing, and malicious agents, and showing dynamic task and communication, registration, and resource control policy management of ~25 agents in six KAoS domains (including a subdomain) on the grid u u Stand-alone demonstrations of additional coalition-related capabilities u u Specific additional objectives beyond the 6-month demonstration: u u US domain with domain-aware AODB and CAMPS agents u u Ariadne ‘come-as-you-are’ open source weather agent u u Observer (Intel) domain containing surrogates for Dartmouth agents u u Gao Observer subdomain containing malicious observer agent whose denial-of-service attack is countered by KAoS and NOMADS resource control mechanisms u u Stand-alone demonstrations of: MIT ‘agent death’ exception handling, Stanford incentive management, U. Michigan plan deconfliction, and Dartmouth ‘observer agents’ u u More powerful web-based policy administration tool administering communication, registration, and resource policies

CoAX /10 August 2000 Briefing Supported by the DARPA CoABS Program CoAX JFAC HQ Gao Intel US JTF HQ Observers (Intel) Gao Obs. Subdomain of “Observers” 9-Month Integrated Demo Structure Db ii Db i MBP Intel1 Intel2 DM2 MM2 DM1 MM1 DM4 MM4 AODB PP' DM3 MM3 DM5 MM5 DGO DAO GAO DM6 MM6 WeatherViz AL Plan AODB LM-ATL Weather Ariadne CAMPS ALDB

CoAX /10 August 2000 Briefing Supported by the DARPA CoABS Program CoAX 18-Month Demonstration Plan u u Overall Objective: u u Integrated Binni scenario demonstration including all CoAX participants showing exception handling, incentive management, plan deconfliction services, and dynamic task and domain management of ~35 agents in nine KAoS domains (including a subdomain and agents with multiple domain membership) on the grid u u Specific additional objectives beyond the 9-month demonstration: u u Emphasis on execution phase of Binni scenario u u Packaging of initial task and domain management capabilities as grid services u u Separate UK and meteorology domains and coalition superdomain u u Policy conflict resolution mechanisms in place for GAO agent registered as member of multiple domains u u Use of MIT exception handling grid services u u Use of Stanford to allocate tasks and computing resources and manage incentives u u Use of Michigan services to identify and resolve plan conflicts u u Use of Dartmouth ‘observer agents’ to feed coalition command u u Management of mobility and conversation policies through policy admin. tool u u Additional forms of attack by malicious agents countered by enhanced agent domain management mechanisms

CoAX /10 August 2000 Briefing Supported by the DARPA CoABS Program CoAX JTF HQ JFAC HQ Gao Intel US Observers (Intel) UK Coalition Met. 18-Month Integrated Demo Structure Gao Obs. AODB LM-ATL Weather Ariadne CAMPS ALDB Db ii Db i MBP Intel1 Intel2 DM2 MM2 DM1 MM1 DM4 MM4 AODB DM8 MM8 DM5 MM5 DGO DAO GAO DM6 MM6 AL Plan Intel1a Intel3 DM7 MM7 Db iii DM3 MM3 WeatherViz DM9 MM9 PP EH IM Plan Dec.

CoAX /10 August 2000 Briefing Supported by the DARPA CoABS Program CoAX 30-Month Demonstration Plan u u Overall Objective: u u Integrated Binni scenario demonstration including CoAX participants showing dynamic creation and reconfiguration of agent domains, virtual organization, and overall coalition process u u Specific additional objectives beyond the 18-month demonstration: u u Demonstration includes all phases of Binni scenario u u Possible participation of other nations (especially TTCP) and additional CoABS research teams u u New coalition members and domains added on-the-fly u u Generic task and process management facilities u u Tailored visualizations u u High-level task, process, and domain management tools u u Management of obligation policies, and fleshing out set of communication, access control, resource management, conversation, and mobility policies

CoAX /10 August 2000 Briefing Supported by the DARPA CoABS Program CoAX Briefing Outline u Overview u Key Coalition and Technical Drivers u Binni Scenario u CoAX Components u Domain Management u Demonstrations u 6 Month Demonstration Report u 9, 18 and 30 Month Demonstration Plans u Status and Next Steps

CoAX /10 August 2000 Briefing Supported by the DARPA CoABS Program CoAX Status and Next Steps u 1-month and 6-month demo milestones successfully completed u 100+ page ‘living document’ describing CoAX and Binni ‘FLASH’ scenario delivered u Ongoing work with GITI on design for packaging of agent domain services for the grid u 9-month demonstration ready in October u Integrated demonstration u Stand-alone demonstrations u Sneak preview of progress on 9-month demonstration at Malvern TTCP meeting in September

CoAX /10 August 2000 Briefing Supported by the DARPA CoABS Program CoAX Summary u Coalition operations is a matter of high concern for the military and a great proving ground for agent research u Binni provides mature rich source of realistic scenario data u Actual military tools used in true cross-national collaboration—hope to expand to additional nations in the not-too-distant future u Fourteen CoABS partners cooperating in phased technical integration u Grid provided necessary interoperability u Significant new research issues being addressed of both theoretical and practical significance

CoAX /10 August 2000 Briefing Supported by the DARPA CoABS Program CoAX Further Information u See u u CoAX and Binni documentation available