CoAX Technology Contributions TTCP Meeting - Malvern - September 2000 AFRL Rome, AIAI, Boeing, Dartmouth, DERA Malvern, Lockheed Martin ATL, Michigan, MIT Sloan, Stanford, USC/ISI, UWF/IHMC Support from BBN, GITI, ISX, MITRE, Schafer Coalition Agents eXperiment (CoAX) DARPA

CoAX /Tech Briefing - 3 Technical Contributions u GITI - CoABS Grid Infrastructure u Boeing and UWF/IHMC- KAoS Domain Management u AIAI Process Panel - Task and Process Management u DERA Master Battle Planning u LM ATL EMAA/CAST AODB - Restricted Data Base Access u AFRL/BBN/GITI CAMPS - Air Logistics Support Tool u USC/ISI Ariadne - Open Information Access u UWF/IHMC - NOMADS safe and secure mobile agents u Stand alone demonstrations at 9 months: u MIT Robustness Services u Stanford Incentives Management u Dartmouth Observer Agent u Michigan Coordination Planning Aid

CoAX /Tech Briefing - 4 GITI/ISX The CoABS Grid u The CoABS/Infrastructure code provides a framework for integrating diverse agent-based systems, and provides additional common services. u The Grid allows agents to find services and other agents so that agent teams can be dynamically formed to solve context-based tasks. u The Grid is built using Jini TM technology. Direct agent communication is provided using message queues built on JAVA RMI. Grid Logging Markup Language based on XML.

CoAX /Tech Briefing - 5 Prototype Grid Architecture Java Platform: RMI, Jini™ Grid Core Services Grid Agent Helper Grid Service Helper ServiceRepRegistry AgentRep Message Queue Logging Visualization Admin EventsSecurity Object RETSINA Proxy Agent OAA Proxy Agent Grid Ready Components Grid Aware Services Information Retrieval Agents Auction/Trader Agents Proxi Agents MatchmakerMobility Event Messaging Instrument- ation 0 Interoperability of distributed, heterogeneous objects, services, and multi-agent systems. 0 Registration and advertisement of capabilities. 0 Discovery of relevant participants, and flexible run-time communications. 0 Current Grid services include: Logging, Visualization, Security, Instrumentation, Communication, Registration, and Event Services.

CoAX /Tech Briefing - 6 Boeing/UWF - 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, platform- specific, and agent-specific policies.

CoAX /Tech Briefing - 7 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 /Tech Briefing - 8 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 /Tech Briefing - 9 KAoS Policy Admin Tool

CoAX /Tech Briefing - 10 AIAI I-X Process Panel u Initially maintains an overview of the current status the coalition C2 processes in accessible shared military terms. u Later adds the ability to monitor, plan and control the coalition C2 processes. u Can take on and address “issues” in the C2 process. u Links to and assists with domain management, authority, exception management and other Grid management services. u To be packaged as generic task and process management facilities that can be made available to other Grid applications.

CoAX /Tech Briefing - 11 AIAI I-X Process Panel

CoAX /Tech Briefing - 12 DERA Master Battle Planner u Visual planning tool for air operations. u Map-based graphical user interface - operator builds scenario and air missions using simple dialogs and “point and click” techniques. u Analyzes plans (identifying over-tasking, GANTT charts, animated flyout facility) u Obtains data on targets and assets from other agents. u Integrates air missions (e.g. air transport) and weather forecasts from other agents into the air visualisation. u Informs AIAI’s Process Panel of current planning status.

CoAX /Tech Briefing - 13 DERA Master Battle Planner

CoAX /Tech Briefing - 14 DERA Master Battle Planner

CoAX /Tech Briefing - 15 AFRL/GITI/BBN CAMPS Mission Planner u u Develops schedules for aircraft to pick up and deliver cargo within specified time windows. u u Takes into account a large number of constraints (aircraft & port capabilities, crew availability, work schedule rules) u Can be tasked by other agents. u Domain-aware agent obtains scheduled air transport flights and forwards them to Master Battle Planner for integration into the air visualisation.

CoAX /Tech Briefing - 16 AFRL/GITI/BBN CAMPS Mission Planner

CoAX /Tech Briefing - 17 USC/ISI Ariadne Weather Agent

CoAX /Tech Briefing - 18 LM ATL EMAA/CAST AODB Access Agent u Provides access to AODB via XML formatted Grid messages. u Supports different kinds of queries: one shot, update, and persistent. u Will be evolving EMAA/CAST technology to create a deliverable generic Grid-aware core agent engine to other end users. This technology will be configurable and is intended to easily allow access to alternative sources.

CoAX /Tech Briefing - 19 LM ATL EMAA/CAST AODB Access Agent

CoAX /Tech Briefing - 20 Lm ATL EMAA/CAST AODB Access Agent

CoAX /Tech Briefing - 21 USC/ISI Open Information Access u Provide real-time access to Web data sources u Tools for learning wrappers to extract data for semi-structured sources u Agents learn the structure of data to support: u Source verification automatically detect when the source no longer provides correct data (possibly because the source has changed) u Source reinduction automatically revise wrapper when site change

CoAX /Tech Briefing - 22

CoAX /Tech Briefing - 23 Resource Control and Security in NOMADS u Dynamic and fine-grained resource control u NOMADS enforces security policies specified by the KAoS domain manager u Security policies include limits on CPU, disk, and network resource usage u Resource consumption monitoring u NOMADS Guard constantly monitors the resource consumption of the GAO agent u When the guard detects a potential denial of service, the guard reduces the resource limits available to the GAO agent

CoAX /Tech Briefing - 24 Resource Control and Security in NOMADS Aroma VM GAO Java VM DAO Observers Domain G KPAT Domain Manager

CoAX /Tech Briefing - 25 Field Observations (Dartmouth) Team of soldiers PDA’s Ad-hoc wireless networking Soldiers make observations. Ground traffic Air traffic Personnel and equipment Buildings and other structures Observations are fed into battle-planning systems (e.g., MBP) through the CoABS Grid. In the demo, a team of CoAX soldiers will make observations to correct Gao mis-information.

CoAX /Tech Briefing - 26 Observations Field Observations (Dartmouth) Observation Agent D’Agents API Grid API I see a tank! Observation Viewer MBP (9-month demo - standalone) (18-month demo - integrated) Query/ Response Registration/ Update Stream

CoAX /Tech Briefing - 27 MIT Robustness Service u The Challenge u Open systems (like coalitions) include unreliable agents (bugs, malice) and infrastructures u The MIT Robustness Service u Monitors agent ‘health’ via polling u Tracks inter-agent commitments u Controls task cancellation, result caching & task re- announcement u Maintains reliability information (failure avoidance) u Informs registry of hung agents

CoAX /Tech Briefing - 28

CoAX /Tech Briefing - 29 Michigan Multilevel Coordinator Agent u Analyses the alternative plan spaces of coalition functional teams that plan independently and act asynchronously u Works top-down with plans chosen by teams to predict unintended interactions (resource contentions; friendly fire). u Identifies candidate resolutions (timing or action constraints). u Notifies process panel of possible plan conflicts and computed workarounds. u Operationalizes/enforces coordination decisions selected. u Given more time, isolates and resolves conflicts more precisely and efficiently. u Allows planning and coordination decisions to be postponed until runtime conditions become better known. u Packaged as a Grid-aware component that can be proactively executing and utilized by the AIAI Process Panel.

CoAX /Tech Briefing - 30 Michigan Multilevel Coordinator Agent

CoAX /Tech Briefing - 31 Removed and Spare Slides u Old versions and spare slides

CoAX /Tech Briefing - 32 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 /Tech Briefing - 33 Field Observations (Dartmouth)

CoAX /Tech Briefing - 34 Michigan Coalition Coordination Coalitions formed in response to emergent needs Functional teams (firestorm, logistics, etc.) formed with participants from contributing partners Without prior history, functional teams can possibly act redundantly, counterproductively, or even harmfully (e.g., friendly fire) Problem: Supporting (through automation) the identification of potential interferences between functional teams at appropriate level(s) of detail, and proposing mitigation strategies

CoAX /Tech Briefing - 35 Coordination Decisions: Logistics stays on ground Combat waits for Logistics to use Epsilon before destroying Michigan Coalition Coordination Example Logistics: Deliver experimental weapon from Alpha to Foxtrot Alpha Foxtrot Gamma Delta Combat: Deny airspace Beta; destroy bridge Epsilon Beta Epsilon