[dias-p1] Re: DIAS P1 notes

  • From: "Y. Richard Yang" <yry@xxxxxxxxxxx>
  • To: "dias-p1@xxxxxxxxxxxxx" <dias-p1@xxxxxxxxxxxxx>
  • Date: Mon, 20 Jul 2015 23:21:09 +0800

Dear all,

First, sorry for missing the first half of the call :-(

Below is a rough writing, based on Erich's main idea paragraph, to organize
a storyline that can include all main ideas I understand at this point.
From my understanding, it definitely is a very cool project. I hope that
no main idea are missing or at a wrong place. We may not use the writing
directly, but can use it as a way to organize the "places" of the main



We propose Software Defined Coalitions (SDC) as the key innovation to
address these problems. Building upon Software Defined Networking (SDN),
SDC exposes, abstracts, and allows rapid and secure control of resources in
Coalitions. In contrast with standard SDN, SDC includes the concepts of
higher-level coalition programming, multiple resource types, multiple
controllers, incomplete information, and dynamism as a first class object.

Specifically, the basic operational unit of SDC is an Enclave, which
consists of a set of resources (e.g., warfighters, vehicles, nodes, link
bandwidth, computation, storage, power, radio) that is controlled by a
single domain (e.g., US, UK). In SDC, an Enclave has a single logical
controller that manages its resources (it may also have backup/failover
controllers), and the controller exposes high-level, programming
logic-based algorithmic control programming abstractions to substantially
simplify Enclave programming, so that Enclave control programmers can adapt
to dynamism such as coalition dynamism and security concerns at
unprecedently programming speed, simplcity, and verifiability. Going beyond
programming logic based algorithmic tools, SDC also introduces a novel,
network utility maximization (NUM) based foundational framework to allow
SDC controller programmers to systematically control and tradeoff multiple
resource types, including not only network but also storage and
computational resources.

An Enclave does not operate in isolation. In a coalition, there can be
multiple coalition parterns and each coalition partner can contribute
multiple Enclaves under its control (e.g., a battalion, a squad). Different
Enclaves may have different security, priorities, policies, and values of
their resources. SDC introduces systematic, novel techniques to support
inter-Enclave and inter-coalition partner interactions. Specfically,
declarative state abstraction, secure multiparty computation, and stable
computation for incomplete state allow one controller to achieve
principled, verifiable secure information flow control and computation when
collaborating with other controllers. When direct communications between
two controllers are not possible or when interacting with external entities
that do not support SDC, SDC introduces novel measurement techniques so
that one controller can probe, verify, and estimate the states of other

Realizing dynamism as a first-class object, SDC introduces graceful,
self-optimizing control-plane networks so that the control plane behaves
gracefully, when one Enclave fragments into two when the network is
partitioned, (re-)integrate when communication is restored or introduced,
or when coalitions separate after achieving a mission or when connectivity
is lost. agile, rapid, and dynamic manner.

Important: Certify Effort
10:00 pm
*ERS Pre Reviewer*
Hello Yang, Yang (Y. Richard), Effort reports for the following individuals
are available for your

On Monday, July 20, 2015, Erich M Nahum <nahum@xxxxxxxxxx> wrote:


For my own edification I went through the various emails about the
government feedback for P1, taken from the official response documents,
Dinesh's response slides from the visit, etc. I put them all together to
help focus my thinking about what we need in P1. I'm sharing it in the
hopes that it is useful to others.



Other related posts: