Next Generation Networking and The HOPI Testbed

Transcription

1 Next Generation Networking and The HOPI Testbed Rick Summerhill Director, Network Research, Architecture, and Technologies, Internet2 CANS 2005 Shenzhen, China 2 November 2005

2 Agenda Current Abilene Network The next generation Abilene The HOPI project HOPI igrid demo 2

3 Abilene Backbone 3

4 Time-Line October End of recent 1-year Abilene transport MoU extension Sets next-generation network planning timeline Architecture definition: 1/1/2006 Transport selection: 4/1/2006 Equipment selection: 7/1/2006 Backbone deployed: 1/1/2007 Connector transition: 2007 Concurrently, review overall business plan and management model Network design time frame: HOPI testbed is expected to be in place for 2-3 years, to experiment with future protocols Refine and evolve next generation architecture 4

5 Basic Requirements Recent technical reports Abilene Technical Advisory Committee report Group A (NLR and Internet2) report Requirements multi-dimensional in scope, for example: Provide capabilities at all network layers (layer) Provide capabilities for both short term and long term applications or projects (duration) Provide capabilities at a variety of different levels of robustness, from production to experimental (robustness) An infrastructure consisting of dark fiber, a significant number of waves, and a production quality IP network Create a new architecture for the R&E community 5

6 Architecture Requirements Uncongested data transport Including IP packet switching Dedicated capacity Duration, Reliability, Capacity Simplified connectivity to Research and education community in the US Other national networks International research and education networks Potential for commodity network peering Architectural constraints Standard hierarchy: national, regional, campus Expansion to additional layers if necessary Must be capable of evolving to support new features Dynamic provisioning to some degree Hybrid models for data networking 6

7 Applications Focus must on applications It s not just about creating dynamic circuits, but supporting applications that need rich topologies. Application specific topologies Important to understand how existing applications will use a richer architecture, and also how existing applications might be redesigned, or new applications created Application layer plays a fundamental role in the architecture Setup and tear down of application specific topologies is above the control plane layer Again, all this should be transparent to the user 7

8 Backbone Footprint Basic component will be ITU grid waves that interconnect nodes on a national fiber footprint Number of waves expected to be from 10 to 40 waves Bandwidth of each wave expected to be 10 Gbps (and possibly 40 Gbps) Switching nodes between segments, optical or electrical Schematic: 8

9 Switching Capabilities Through an optical interconnecting device that serves 3 purposes: Provides a client interface to connecting network Provides access to waves on the network Provides support for sub channels on a wave i.e. Ethernet VLANS, SONET paths, or other suitably framed capacity. Potentially using GFP, VCAT, and LCAS 9

10 RON Interface The interface to the backbone: Two or more client interfaces between optical interconnects (analogous to router-to-router connections today) Requirements: Support connectivity to IP Network Support multiple sub channels through backbone to other RONs up to capacity of interface Potential for alien waves in the future 10

11 Next Generation Architecture 11

12 Campus Connectivity Hierarchy is likely to remain national to regional to campus RON - campus connections similar to Backbone - RON connections Bandwidths may be lower There may be state networks or campus departments in the hierarchy The ability to create dedicated capacity across administrative domains is a key factor End-to-end high performance networking is a fundamental goal High performance IP service High performance dedicated capacity from deep within a campus to deep within another campus 12

13 Dynamic Provisioning and Switching Dynamic provisioning across administrative domains Setup on the order of seconds to minutes Durations on the order of hours Eventually understand the need for more dynamic capabilities Control plane development will be a key Switching may require unique partnerships and development of capabilities on hardware platforms For example, being able to isolate user capabilities at switching nodes There is interest from carriers from the point of view of providing additional services All this should be transparent to the user View as a single network Hybrid aspects must be built into the architecture 13

14 Further Investigation Requirements Group A report? Abilene TAC report? Backbone What is the national footprint? Is 100 Gbps the right total bandwidth? Where are the switching nodes located? What provides the switching capabilities? What is the backhaul availability? What is the framing on the waves? Is it possible to provide support for alien waves? 14

15 Further Investigation Interconnects Where are the optical interconnects located? What are the optical interconnects? What are the interfaces? What is the framing on the client interfaces? What is the service offering? Dynamics What degree of dynamic provisioning is required? What control plane properties are needed? What availability is required day one? When are carrier class waves needed? IP Providing carrier class waves for the IP network? What is the topology of the IP backbone? What role does dynamic provisioning play in the IP network, for example in redundancy? 15

16 HOPI Project - Overview As outlined in requirements documents, we expect to see a richer set of capabilities available to network designers and end users Core IP packet switched networks A set of optically switched waves available for dynamic provisioning Fundamental Question: How will the core Internet architecture evolve? Many options being examined Examine a hybrid of shared IP packet switching and dynamically provisioned optical lambdas HOPI Project Hybrid Optical and Packet Infrastructure - how does one put it all together? Dynamic Provisioning - setup and teardown of optical paths Hybrid Question - how do end hosts use the combined packet and circuit switched infrastructures? 16

17 HOPI General Problem 17

18 HOPI Topology 18

19 HOPI Deployment Installed node locations Los Angeles Equinix facility - same location as NLR node Washington, DC MAX/Dragon facility - same location as the NLR node StarLight in Chicago The Pacific Northwest GigaPoP in Seattle - Westin Building, the new location of the NLR node Future node locations New York City NYSERNet area in 32 AoA - same location as NLR node (many thanks to NYSERNet for donating rack space and power to support the HOPI project). Looking at additional possibilities as the southern route of NLR is installed - potentially Houston Circuit from NYC to London Early November, 2005 Connection to GEANT2 testbeds 19

20 HOPI Node 20

21 Recent Activities Connections to HOPI UltraLight - Physics project to explore similar ideas UltraScienceNet - A project of the Department of Energy GEANT2 Testbed DRAGON CHEETAH RONs in the process of connecting Connections to the ITECs at North Carolina, Ohio, Texas A&M, and UCSD Note - connecting to HOPI is not about providing connectivity, rather it is to understand new ideas and paradigms. It is a testbed that will require real participation from all participants 21

22 HOPI Support Advisory Groups HOPI Design Team HOPI Corporate Advisory Team HOPI Research Advisory Panel HOPI Supporters Force10 HP Glimmerglass The HOPI Testbed Support Center 22

23 HOPI Testbed Support Center Award of the TSC went to a collaboration between MAX, NCREN, and the GRNOC at IU Advanced engineering and design focus Implement control plane activities The MAX GigaPoP and the NSF supported Dragon project will focus on these issues Coordinate application activities NCREN will focus on these issues Manage and engineer the facility GRNOC at IU will focus on these issues Focus is on dynamics and the Hybrid aspects, but also applications, security, measurement, operations, engineering, AAA 23

24 igrid 2005 Demo Key points of the HOPI Demonstrations for igrid2005 E-VLBI Application real time access to radio telescopes, linking them to correlators at MIT Haystack Observatory GMPLS control plane Porting the DRAGON protocol stacks to manage the Force10 E600 switches Inter-domain provisioning Three exemplar administrative domains will be part of the demo: international, national, and regional International scope Telescopes in Onsala SE, Westerbork NL, Jodrell Banks UK, Kashima JP, Greenbelt MD, and Westford MA. Networks: UKLight, NetherLight, NorthernLight, SUnet, StarLight, HOPI, DRAGON, BOSnet Persistent infrastructure - A new type of demo: The infrastructure will remain in service for use by the end user community after the demos are over (!) Expanded Support for Supercomputing 2005 Support for UltraLight Support for the SC05 Bandwidth Challenge 24

25 HOPI: igrid

26 The 30,000 foot view HOPI Igrid Demo: Kashima JP StarLight Jodrell Banks UK Westerbork NE Onsala SE JGN2 UKLight NetherLight NorthernLight MIT Haystack Observatory Seattle Chicago Los Angeles Washington DRAGON HOPI Greenbelt MD Westford MA

27 Contact Information HOPI Call Center: (877)

28 28