• End-user Opt-in

• Experiment Workflow and Services

• Facility Control Framework

• Operations, Management, Integration, & Security

• Substrate

GENI Substrate Working Group

<substrate-wg>

---

Chairs:

Patrick Crowley <pcrowley@wustl.edu>
Joe Evans <evans@ittc.ku.edu>
Kristin Rauschenbach <krausche@geni.net>

SE:

John Jacob <jjacob@geni.net>

Discussion Mail List Information:

subscribe
mailman archive
nabble archive

Wiki: http:/groups.geni.net/geni/wiki/GeniSubstrate

Scope:

What is the framework for evolution of substrate technologies? What technologies should be in GENI? How will they be used?

Initial Deliverables:

• Description of what can/should be implemented by the end of 2008: one brief (20pp) overview and one brief (20pp) document for each substrate type. Documentation should include high level functional architectures, initial capabilities definitions, projected development schedules with dependencies and identified risks, Technology Readiness Levels [PDF], and best-effort cost estimates.

Later Deliverables:

• Substrate Framework: e.g., generic substrate requirements; appropriate abstractions for specific technologies; evolution strategies
• Technology Identification: e.g., technology survey; technology tradeoffs including justification in GENI's scientific context; identification of candidate substrate technologies plus characterization of additional development to meet GENI requirements
• Requirements Definition & Design: significant contributions to the GENI Project Deliverables. In particular, the WG will develop contribute to the Technical Requirements Document to cover the substrate portion of an eventual construction RFP. The chapters in this document will span generic requirements applicable to all substrate technologies as well as requirements specific to each substrate technology. The WG will populate the specifics of this document based on the outcomes of trade studies, risk-reduction prototyping and analysis, e.g., Internet interconnect tradeoffs & recommendations or recommendations on incorporation of "disadvantaged" GENI nodes with various examples (sensors, cell phones, etc.).
• Risk Register: performance, cost, and schedule risks.