190 likes | 499 Views
FIND: Future Internet Design PI Meeting November 8-9, 2006. Darleen Fisher CISE National Science Foundation dlfisher@nsf.gov. Future Internet Design (FIND). Creating the Internet you want in 10-15 years. The Future Internet:. Worthy of our society’s trust—security and availability
E N D
FIND: Future Internet DesignPI Meeting November 8-9, 2006 Darleen Fisher CISE National Science Foundationdlfisher@nsf.gov
Future Internet Design (FIND) Creating the Internet you want in 10-15 years
The Future Internet: • Worthy of our society’s trust—security and availability • Even for managing and operating critical infrastructures • Provides a bridge between physical and virtual worlds • Via instrumented and managed sensorized physical environment • Privacy preserving in environment of pervasive sensing, computing, content, datamining . . . • Suitable for tomorrow’s technologies • Manageable and usable • Capable of applications support • Content-rich, storage, services, realtime, etc. • Economically viable • Fosters a social world in which we would want to live
What is Different This Time? • Clean-slate approach • To overcome Internet ossification • Research not constrained by the features of the current Internet • But does not mandate rejecting what currently works • A comprehensive coordinated effort • Ability to try different approaches (We do not have a preconceived idea of what they are) • Ability to experiment at scale • With real users and applications
Success Scenarios • Internet evolution influenced by clean-slate approach • Alternate Internet architecture emerges • Alternate architecture(s) coexist with the current Internet • Virtualization becomes the norm with plurality of architectures • Single architecture emerges and dominates • New services and applications enabled • Invigorate the research community— • creativity unbound by current Internet, design architectures and build large systems • Many other payoffs--some unexpected
FIND - Different Process • “Goal” oriented Future Internet • Not typical for NSF research programs • Area has a longer timescale with sustained funding • Three phases -- iterative and overlapping • Exploration of architectural components and 1st cut overarching architectures • Convergence into multiple full-scale architectures • Experimentation of architectures at scale • “Competitive cooperation” model • Competition – Proposal reviews • Cooperation – Among awardees • Regular meetings -- three times a year • Commitment to openness and transparency
Stages of ResearchBeginning in 2006 • 26 of 98 projects awarded • some 1 year seed investments • NeTS = $40M • FIND = ~$15M (38% of NeTS)
FIND 2007 • NSF 07-507; January 22, 2007 deadline • FIND project descriptions at:http://nsf-find.cs.umn.edu • First FIND PI meetings • Begin to create a FIND community and identify areas of commonality and differences, open research areas • Create new architectures • Nurture creativity and architectural thinking in future generations of researchers through enriched experiences for graduate students • Establish a process for including FIND-like researchers from industry, international and academics funded elsewhere
Challenges • How are network architectures created? • Are they envisioned or composed? • Individual’s vision? • Small group process? • Community effort? • Does one start with an overall framework and flesh it out? • Or is an architecture composed of network elements? • Does an element choice determine the architecture? • Can components be reused by different architectures? • Can architectures be dynamically composed from building blocks? • Not presuming a process or the outcome • Expect will emerge over the course of FIND
Challenges • How does FIND enable the creation of architectures? • FIND PI Meetings • What format/content works? • Should there be “focused” additional or alternative meetings? • How to add researchers funded elsewhere? • Creative ways to engage graduate students • How ensure newcomers are first class citizens—no first settler royalty
Challenges • Broader Impacts • How ensure that students and young faculty are “safe” to work in the FIND area? • How can FIND group enable publications and conferences in this area? • How will FIND impact GENI? • Contribute to GENI Science Plan now • How to make sure FIND architectures inform GENI • Impact on Future FIND Solicitations • What topics/components are completely missing from the FIND portfolio? • Where would competing approaches to current portfolio be healthy?
Challenges • Broader Impacts • How ensure that we build a society we want to live in? • Security • Can you make the Future Network inherently secure/robust—in cyber war no distinction between military and civilian • Is it safe for what runs on it e.g. critical infrastructures? • Privacy • (Revocable?) privacy-preserving mechanisms • With data mining, are there mechanisms for “spyglass” into how information being collected? Used? How correct the data? • Social control vs open-society • Who controls content, access to content and sources, collects data on access records and content (e.g. traffic analysis for predatory behavior)
NeTS Program Directors 2007 • FIND—Darleen Fisher & Allison Mankin • NBD—Darleen Fisher • WN—David Goodman (leaves 2/06) • Recruiting new PD with wireless networking expertise • NOSS—David Du
Allison Mankin • Co-program director FIND (with Darleen Fisher) • Co-program director GENI (with Guru Parulkar) • Consultant, Shinkuro, Inc., Bell Labs, USC/ISI, NRL, U. Wisc (visiting scientist), MITRE • Author of many published networking research papers • Co-editor IPng: Internet Protocol Next Generation 1995 • Co-Director, IETF Process for Selection of the Next Generation Internet Protocol • Director, CAIRN (successor to DARTnet) • Internet2 Abilene Technical AC • Area Director, Internet Engineering Steering Group • Chair, IETF Geolocation Privacy WG (ongoing) • ICANN Security & Stability Committee • Member of various boards, directorates, and working groups
David Clark “FIND Architecture and Outreach Coordinator” • Remain a member of the research community, but work with NSF & community • Plan PI meetings • Identify FIND research priorities • Lead FIND team-building • Help FIND researchers frame new architectures • Outreach to researchers funded elsewhere • Outreach to international FIND-like researchers • Provide linkage between FIND and GENI
FIND Coordination and Planning Committee • Focused community input into PI meetings, outreach, etc. • Paul Francis, Cornell • Jim Kurose, UMass • Jen Rexford, Princeton • Srini Seshan, CMU • Vern Paxson, ICSI
Agenda November 8, 2006 9:00-10:00 Introduction: Report on the FIND program and awards Review of the program objectives and objectives of the meetings Next steps in creating network architectures Review of the agenda 10:00-10:30 break 10:30-12:00 Technical program I: Network virtualization Speakers: Nick Feamster, Jon Turner, Vincent Chan and Sergey Gorinsky 12-1:30 Lunch: Table discussion: Meet with an NSF program officer 1:30-3 Technical program II: Services architectures Speakers: Tilman Wolf, Dan Duchamp, Paul Francis 3-4:00 Working break 4:00-5:00 Envisioning the future—a plenary session interactive exercise 5:00-6:00 Reception 6:00 Dinner: Table discussion: TBD
Agenda—November 9, 2006 • 8:30-9:30 Discussion groups: Size and makeup of the FIND group; student participation • 9:30-10:00 Plenary session: summary of discussion groups, future meetings • 10-10:30 Break • 10:30-12:00 Technical program III: Sensor networks and future architecture • Speakers: Mark Hansen, Deborah Estrin, Mani, Srivastava, Jeffrey Burke, • John Heideman, Junghoo Cho, Srini Shesan • 12-1:30 Lunch • 1:30-2:30 Discussion groups: Review of technical sessions: requirements for future nets • 2:30-3:00 Plenary discussion: summary of discussion groups. • 3:00 Adjourn
Stages of Research2008 and Later Coordinated effort to assemble overarching coherent architectures • Multiple PI meetings to formulate architectures • FIND awardees • But also other “architectural” researchers e.g. funded by NeTS, CyberTrust, DARPA, industry, internationally funded researchers, etc. • Small number of architectures developed Architectures as they emerge will be made operational and tested • Simulation • Emulation • Run on a large-scale GENI facility • Experiment with new architectures at scale