Why This Meeting

1
First EROS Working Group Meeting

• Welcome

2
Why This Meeting?

• Finalize the core EROS architecture. Its time to
  do applications.
• Get several of the early potential users of EROS
  into a common (padded) room.
• Take a sanity check on requirements to ensure
  we are headed in a useful direction.
• Begin a new experiment for JHU in methods for
  technology transfer.

3
JHUISI JHU Information Security Institute

• A cross-disciplinary approach to security,
  privacy, and integrity
• Technology and computing research
• Legal and policy arm
• Neutral evaluation
• Hands-on consulting
• Through SRL, EROS sits in the research arm of
  the JHUISI activities
• EROS is expected to be a core component of the
  JHUISI technologies

4
Technology Transfer

• Successful transfer out of universities has been
  rare
• Research stops before technology is usable
• Expertise (students) dissipates quickly
• There is no one to accept the handoff
• Disruptive technology funding is challenging
  must build a market, not just a company

• The experiment
• Gather a number of interested companies
• Invite them to participate actively in creating
  the new technology
• Create a collaboration framework in which to
  build a new market
• Centralize the technology core in a neutral third
  party.

5
Invitees

• JHU (Shapiro EROS)
• U. Md. College Park (Arbaugh AEGIS)
• Panasonic (Braun PiE-OS, (D)MERT)
• Sprint Labs (Roscoe NEMESIS)
• IBM (Hunt - several)
• Palm (Landau KeyKOS)
• Caplet, Inc. (Miller Xanadu, E)
• The Apache Group (Laurie Apache SSL)
• Key Logic graduates (Frantz KeyKOS, SPKI)
• DARPA (Witten)

6
Common Interests

• Desire to run dynamically adaptive, untrusted
  code in open, computing fabrics (liquid software)
• Desire to create a sensible distribution
  framework for distributed liquid apps (Spills?
  Splats?)
• Shared mission to change the current computing
  paradigm to make security and resource isolation
  commonplace

7
Agenda

• Day
• Architecture and Design Issues
• Application requirements
• Continuing discussion
• Need to frame the issues, but the purpose of
  these three days is discussion.

8
Anticipated Results

• Final EROS architecture revision
• Greater clarity on app. requirements
• Summary minutes from these discussions
• Build an initial core community