Trans-enterprise Service Grid (TSG)Active Interoperability AcrossIndependent Partners David E. EllisInformation Management Architect(505) 844-6697, dellis@sandia.gov

Interoperability ChallengeThere are situations requiring cross enterprise messagingMany current architectures discuss message exchanges in terms of a single enterpriseSOA benefits from its ability to cross ownership boundariesFederalRegionalStateLocalTribalCrossing ownership boundaries must accommodate both Technical aspects: syntax, semanticsPolicy aspects: access control, security, to be interoperableInteroperability among diverse participants requires a prearranged groundwork for communications and understanding supporting:Different policy and security contextsIncremental addition of services and participantsResource multiplier when adding another stakeholder

IPAWS ExampleIPAWS as example of cross enterprise challengeIntegrated Public Alert and Warning SystemCoordination between independent entitiesComponent systems separately owned and governedEach component provides messaging capabilities but each originally exists with different purposes and goalsEach entity must fulfill its coordinated role in context of its usual purposeNot possible to centrally coordinate all details of operationsAccommodate current system status, including degraded operationsRequires Geo-Targeting of message deliveryRequires non-repudiation of message content

Local EOC

Satellite and IP Network State EOCMobile IPAWS Coordination CenterIPAWS Connecting CommunitiesFederal AgenciesRadioTelevisionCommercial Mobile ServicesSPORSPORSPORSPORSPORSPORSPORIPAWS Alert Aggregation

Laptop

Local EOC

Satellite and IP Network State EOCMobile IPAWS Coordination CenterIPAWS Connecting CommunitiesFederal AgenciesRadioTelevisionCommercial Mobile ServicesSPORSPORSPORSPORSPORSPORSPORIPAWS Alert AggregationHow do we connect such an independent, distributed set of resources?

Laptop

Coordinating SOA Services: Choreography vs. OrchestrationDifference between active, central control and adaptive coordinationOrchestra versus BalletIn orchestration, theres someone the conductor who tells everybody in the orchestra what to do and makes sure they all play in synchronization Conductor is an active leaderCorrects for anomalies in real-timeCan introduce new information only he hasIn choreography, every dancer follows a pre-defined plan everyone independently of the others Choreographer coordinates plan but not part of executionEach participant responsible for adaptive behavior for anomaly responseMessage exchange must contain all state information needed to evaluate next action

IPAWS Trans-enterprise Services Grid (TSG)Specific SOA implementation to enable multi-jurisdictional government interoperabilityBuilt on existing and evolving standardsUses OASIS Emergency Data Exchange Language Distribution Element (EDXL-DE) for distribution metadata which:Carries arbitrary Document-Oriented Message content payloadEncapsulates Policy and other context for distribution Choreography Uses OASIS Common Alerting Protocol (CAP) as alert content standardLeverages current work on OASIS Service Oriented Architecture - Reference Architecture (SOA-RA)

IPAWS Node Terminology - Diverse ScopeIPAWS nodea node that produces, processes, and/or consumes IPAWS contentMay reside inside or outside of grid (TSG) trust boundarySecure Policy-oriented Object Routers (SPORs) a special IPAWS node that process/forwards EDXL-DE content not explicitly addressed to itselfEdge SPOR is a special node which has bridges between TSG and external interfacesCore SPOR is a general purpose router with internal TSG capabilitiesHigh Assurance SPOR (HA-SPOR) a SPOR which uses cryptographic protection to eliminate host Operating System and application exploitation processes IPAWS hostany node that is not a SPOR but connects to the TSG via a SPORStakeholder nodes which produce or consume IPAWS contentIPAWS communications terminologyIPAWS link a communication facility or medium which delivers IPAWS content either within the TSG or across the TSG trust boundaryIPAWS neighbors nodes attached to the same linkIPAWS interface a nodes attachment to a link

IPAWSNational TSGInternetState EOCFederal EOCCommercial ServiceProvidersProtectedExternal ServiceTSG = Trans-enterprise Service Grid

IPAWS and ChoreographyIPAWS requires adaptive coordination of independent entities within bounds of agreed upon actions and objectivesIdentity to ensure non-repudiation follows guidance by Trust Council for Communities Of Interest (COIs)Roles defined by Trust Council must be associated with participantsMessages must be self-contained, including associated role identityMOU and SLA State attributes are also included as needed by COIs to allow message exchange with other COIs by TSG policy enforcement points

EOC WebBrowserIdentity AgentHTTPS Proxy AgentTrust AgentGateway AgentHTTPS1.2.3.4.5.6.EDXL-DE +Creds7.EDXL-DE +SessionID8.9.10.11.EDXL-DE +HTTP ReqHTTPSPOSTHTTPS +CookieHTTPS +Cookie13.HTTPSHTTPSRedirectHTTPSFORMEDXL-DE +HTTP Resp12.TSGIPAWS (TSG) Client Trust modelEDXL-DE + HTTP Req + Role(s)Local IdentityStoreEDXL-DE + HTTP Resp + Role(s)14.15.16.HTTPSResponseProposed SPOR Communications DiagramNeeds to generate an Alert Message

Commercial ServiceProvidersIPAWSNational TSGInternetState EOCFederal EOCProtectedExternal ServiceCAPMessage

Alert

Alert

Alert

Unprotected MsgProtected (EDXL)

Status of TSG and future workOASIS standards are being improved to enable cross enterprise messagingOASIS SOA Reference Architecture is addressing governance and policy management.OASIS Emergency Management Technical Committee is developing a next version of EDXL-DE to deliver state information into metadata for policy assertions like securityW3C working on Addressing, Policy, Choreography specsIPAWS Pilot is underway to address issues likeJurisdictional constraints for emergency messaging Usability of OASIS and other international StandardsScalability of TSG Grid conceptPerformance limitation of HA-SPORPilot feedback will be shared with appropriate agency and standards organizations to improve cross enterprise messaging

Summary - ConclusionsCross enterprise messaging is a concern for eGov initiativesStandards organizations are developing standards to address this concernService Oriented ArchitectureData Exchange Language using XMLIPAWS will help frame the solution spaceOther eGov initiatives could use TSG capability

*Overall IPAWS Architecture*CAP Message Flow