1. Emerging StateNets Issues Associated with CI and the 3- Tier Networking Model Steve Corbató CI Strategic Initiatives, University of Utah StateNets – Tempe – 04 February 2009

2. Panelists ‣ Shaun Abshere, WiscNet (vice-chair, Internet2 RAC) ‣ Mike Hrybyk, BCnet ‣ Jen Leasure, The Quilt ‣ Rob Vietzke, Internet2

3. CI & StateNets Governance and strategic planning Resources – Data centers (unique HPC/CI requirements) – Optical networks Services – Cycles: capacity vs. capability, links to national centers – Data: storage, curation, access – Middleware: identity management and VOs – Faculty resources Changing fiscal environment (state vs. federal)/priorities Enabling broader research outreach to K-12

4. GENI and StateNets Large-scale effort to build a testbed for experimentation with and the more rigorous engineering of networking systems, protocols, and applications GENI Spiral 1 underway – GENI-enabled campuses (OpenFlow) – Aggressive R&D cycle Potential for StateNets engagement – Dedicated connectivity & co-location – End-user opt-in experiments – Outreach to K-12 and other higher ed institutions

5. Discussion topics 1. How can Middle Tier Networks (MTNs) better position themselves to support CI? 2. Do the regional aggregation/engagement roles of MTNs create unique opportunities for CI services? 3. How can MTNs engage in the early stage of large scale network research (GENI)? 4. What impact will the changing fiscal environment have on MTNs’ abilities to support emerging research requirements?

6. Adapting the Middle Tier S. Abshere WiscNet

7. Ideas to Juggle “Adapt:” Make suitable for new use or conditions. N: Data is the problem, not compute cycles. N: Focus on end-to-end CI services. N: Target engagement with domain disciplines. N,M: Regional networks are culture-changing activities. M: Intra-state R&D collaborations must increase. C: Campuses must adapt their environments for CI.

8. Wisconsin: R&D Campus Tier Economics: $1,100M academic R&D & 38K jobs Campuses: $841M to $35M to $3.5M to $0.3M Campus WAN Transport Capacity: 3 Mbps to 10 Gbps: 24 different bit-rates Favorable Political Themes: Rebuild “undermined” R&D infrastructure. Fund inter-institutional R&D in WI. Promote R&D on more WI campuses. CIO -- not PI -- is WiscNet customer

9. WiscNet Adaptations Increase emphasis on “trust” as attribute of WiscNet community & services: Let’s share and manage the risk of CI deployment Promote & fund community R&D CI pilots (MasStore) Focus members on growing transport capacity and trying new network uses (Grow Smart) Challenge WiscNet staff to increase competence at designing, consulting and managing advanced hybrid networks at campus, state and multi-state levels (Consulting; BOREAS; NTN-ND)

10. Example Multi-Tier R&D Engagement Comprehensive outreach program with several domain science communities –Identify several communities with near term needs –In-depth involvement with these communities to understand specific needs and problems –Convert lessons learned into specific tasks and actions for all stakeholders

11. Example Engagement Criteria Criteria for domain research communities Willing to work with us Significant network usage Problem with current network environment Willingness to explore solutions Explores a unique network problem space Short term operational goals Impact on long term planning Potential for general benefit

12. Ranking of Communities

13. Cyberinfrastructure and Three- Layer Model Jen Leasure The Quilt February 4, 2009

14. MTN’s and CI Projects MTN’s unique role CI efforts –trusted by the community to deliver high quality advanced services at an economic price –flexible, robust network architecture to provide a suite of innovative, challenging problems –role as convener is a geographic area multiple entities engaged in R&E efforts

15. MTN and CI Projects MTN’s don’t just do networks but provide a broad range of services –Shared Services –Multi-State Network Collaborations

16. MTN’s and GENI Quilt WG –Established 2008 –Goal: Establish a forum for RON’s to exchange information on the GENI project and provide a point of contact for RON communications with the GPO Middle Tier Spiral 1 Efforts – Example Mid-Atlantic Crossroads

17. Instrumentation Data Storage Networking Computation User support Policy and Funding Management Security and Access Cyberinfrastructure: Defined

18. CI Encompasses Physical Assets, Information, People, and Skills Working as a System Instrumentation Security Control Data Generation Computation Analysis Simulation Program Security Management Security and Access Authentication Access Control Authorization Researcher Control Program Viewing Security 3D Imaging Display and Visualization. Display Tools Security Data Input Collab Tools Publishing Human Support Help Desk Policy and Funding Resource Providers Funding Agencies Campuses Search Data Sets Storage Security Retrieval Input Schema Metadata Data Directories Ontologies Archive Education And Outreach Network Training

19. Cyberinfrastructure and the Internet2 Community Operating advance services by and for the community –e.g. Networks, Observatories, Federations Experimenting with developmental services –e.g. Dynamic Circuits, Distributed Monitoring, Hybrid Networking Adopting new technologies –e.g. Workshops, Targeted Communities Partnering with like-minded organizations

20. Integrated Systems Approach

21. Distributed System Requirements CI distributed systems share common requirements: Heterogeneous network architecture Multiple administrative entities; no central authority Local customization of operational environment Applications driven by virtual organizations Suggests parallel design approach Toolkit approach Web services / defined APIs

22. Discussion topics 1. How can Middle Tier Networks (MTNs) better position themselves to support CI? 2. Do the regional aggregation/engagement roles of MTNs create unique opportunities for CI services? 3. How can MTNs engage in the early stage of large scale network research (GENI)? 4. What impact will the changing fiscal environment have on MTNs’ abilities to support emerging research requirements?