140 likes | 208 Views
Authority Vectors. David E. Ellis. U.S. Geo-Political Example. Territory : a region or district of the U.S. not admitted to the Union as a state but having its own legislature, with a governor and other officers appointed by the President and confirmed by the Senate.
E N D
Authority Vectors David E. Ellis
U.S. Geo-Political Example Territory: a region or district of the U.S. not admitted to the Union as a state but having its own legislature, with a governor and other officers appointed by the President and confirmed by the Senate
Trans-Enterprise Service Grid (TSG) • OASIS Emergency Data Exchange Language – Distribution Element (EDXL-DE) is distribution metadata for distributing TSG content. • OASIS Common Alerting Protocol (CAP) is a specific alert content standard. • TSG node – a node that produces, processes, and/or consumes EDXL-DE documents and/or their content. • Secure Policy-oriented Object Router (SPOR) – a TSG node that process/forwards EDXL-DE content not explicitly addressed to itself. • Edge SPOR – a special node which has bridges between TSG and external interfaces. SPOR which receives Injection from/provides Deliver to TSG Node. • Core SPOR – a general purpose router with internal TSG capabilities. • High Assurance SPOR (HA-SPOR) – a SPOR which uses cryptographic protection to eliminate host Operating System and application exploitation processes. • A SOA Application Host – any node that is not a SPOR but connects to the TSG via a SPOR. These hosts represent the Sender and Recipient for any information exchange. • TSG Link – a communication facility or medium which delivers TSG content. • TSG Neighbors – nodes attached to the same link. • TSG Interface – a node’s attachment to a link.
Information and Policy Flow • Policy Flow • Nation -> Nation • United States (National) -> States • States -> States • States -> County (or Tribal) • County -> County • County -> City • City -> City • Information Flow • Inject (Sending something into the TSG) • Deliver (Receiving something from the TSG) • Forward (Sending something up the authority vector) • Distribute (Sending something down the authority vector) • Exchange ( Sending something to a peer at same authority)
Data in Motion • Domain is Distribution (What) • Who/What should get content (Purpose) • Sender Authority (Empowerment) • Recipient Authority (Empowerment) • Other (policies about content distribution) • Metadata Usage (How to use XML elements) • Message Authentication • Intent of Distribution • Empowerment (Authority for Distribution) • Disclosure control (Who can see what) • Ontology issues • Intrinsic Part of the Thing • Extrinsic Context of the Thing • Willingness Issues
Policy Examples • General: Policies which effect entire TSG • This.TSGshall distribute all EDXL-DE Msg (allow example) • This.TSGshall not distribute sensitveEDXL-DE Msg (deny example) • This.TSGshall exchange with TSGs (Value A, Value B, etc.) • This.TSGshall support multiple ContentObjects per message) • This.TSGshall support Explicit Distribution (e-mail, Open) • Inject(Sending something into the TSG) • This.SPORaccepts EDXL-DE Msg only • This.SPORaccepts CAP Msg • This.SPORacceptsMsg from only COI( Social Structure or Jurisdiction) • Deliver (Receiving something from the TSG) • This.SPOR delivers to RecipientRole (Value A, Value B, etc.) • This.SPOR delivers to ExplicitAdrress(Value A, ValueB, etc.) • Forward (Sending something up the authority vector) • This.SPOR endorses Msg from COI (Value B, Value B, etc.) • Distribute (Sending something down the authority vector) • etc. • Exchange ( Sending something to a peer at same authority) • Etc.
SOA Willingness • Authority Flow • Local • Tribal • State • Federal • International • Content Authority • Law Enforcement • Health Receiver DistributionCloud Federal Sender State
ElementPurpose Authenticity Intent Empowerment Disclosure • Policy Example • Non-Repudiation • Authenticity • Intent • Empowerment • Routing Issues • Hop count • Token versus • CRL validation
Jurisdiction or Social Structure Taxonomies SecurityLevel Collection Of InterestvalueListUrn (Structure) Locations TBDAttributes OwnsSenderRecipientOriginatorConsumerKeywordscontentKeywords Keywords and contentKewords can be used to represent any topic needed in RDF Triple ValueListURN related to EDXL function and Values for Function
RoleType Recipient Sender EDXLHeader ContentObject Originator Consumer Keyword ContentKeyword IER (IEPD)Needline AllowedValues Schema/Format TagNames MIMEType