Hybrid Optical and Packet Infrastructure (HOPI) Project Heather Boyles Director, International Relations, Internet2 Rick Summerhill Associate Director, Backbone Network Infrastructure, Internet2 TERENA Networking Conference Rhodes, Greece 8 June 2004
Outline The HOPI Project Hybrid Optical and Packet Infrastructure What is it? Why Design Team and White Paper results Next Steps CANARIE/GEANT/Internet2 Lightpath experiment Results 6/4/2004 2
HOPI Project - Summary In the near future we will 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? Examine a hybrid of shared IP packet switching and dynamically provisioned optical lambdas HOPI Project Hybrid Optical and Packet Infrastructure Immediate Goals Create a white paper describing a testbed to model the above infrastructure Implement testbed over the next year Coordinate and experiment with other similar projects Design Team 6/4/2004 3
HOPI Project Design Team Linda Winkler, Argonne (CoChair) Rick Summerhill, Internet2 (CoChair) Cees de Laat, U of Amsterdam Rene Hatem, CANARIE Mark Johnson, MCNC Tom Lehman, USC/ISI Peter O Neil, NCAR Bill Owens, NYSERnet Philip Papadopoulos, UCSD Sylvain Ravot, Caltech/CERN David Richardson, U Washington Chris Robb, Indiana U Jerry Sobieski, U Maryland Steven Wallace, Indiana U Bill Wing, Oak Ridge Internet2 Staff Guy Almes, Heather Boyles, Steve Corbato, Chris Heermann, Christian Todorov, Matt Zekauskas 6/4/2004 4
Architectural Issues Some specific disciplines have enormous bandwidth requirements High Energy Physics and the Large Hadron Collider The Square Kilometer Area (SKA) Community Medical Imaging, Real Time and File Transfer Questions concerning packet infrastructures The shared packet infrastructure itself the ability to support multiple large flows on the order of 6 gbps. Unlikely to have 40 gbps or 100 gbps in near future Increasing demands by some for deterministic paths Ability to have resources that don t exhibit congestion Demand for more dynamic control of bandwidth and topology Availability of dark fiber at the national, regional and campus levels has changed the landscape Where are we going? 6/4/2004 5
HOPI Resources The Abilene Network MPLS tunnels The Internet2 Wave on the NLR footprint MAN LAN Experimental Facility TYCO/IEEAF 10 Gbps lambda NYC - Amsterdam Collaborations with Regional Optical Networks (RONs) and other related efforts (GLIF, SURFNET6, TransLight, DRAGON, etc.) 6/4/2004 6
Abilene/NLR Map 6/4/2004 7
HOPI Project Problems to understand Goal is to look at architecture Temporal degree of dynamic provisioning Temporal duration of dynamic paths and requirement for scheduling Topological extent of deterministic provisioning Examine backbone, RON, campus hierarchy how will a RON interface with the core network? Understand connectivity to other infrastructures for example, international or federal networks? Network operations, management and measurement across administrative domains? 6/4/2004 8
Addresses: HOPI White Paper http://hopi.internet2.edu Basic Services Definition Node Design Node Location (Abilene/NLR Interconnects) Connector Interface Control Plane Management Text Cases (Experiments) 6/4/2004 9
Lightpath Lightpath from LA to CERN Internet2, CANARIE, GEANT, Starlight, SURFnet Crossed multiple administrative domains at a variety of layers Abilene/Internet2 (MPLS layer2 VPN) Starlight (Ethernet switch, layer2) CANARIE (TDM, layer1) MAN LAN / Internet2 (TDM, layer1) Surfnet (TDM, layer1) GEANT (PIP, layer3) 6/4/2004 10
6/4/2004 11
Control Plane Was bandwidth available, how much? 1 Gbps What path to take? Described above Note that we knew bandwidth was available along the path! If not, then scheduling would have been needed What framing to use? 1 GigE and IP Were interfaces available? Some needed to be installed Configuration of TYCO/IEEAF circuit needed to be changed Was router to router Changed to TDM to TDM 6/4/2004 12
Control Plane What layer2 tagging was involved? Range requirements for the MPLS L2VPN across Abilene Configuration of Starlight switch Host in LA set VLAN tagging for outgoing traffic What layer3 addressing was needed? Whose address space? How was routing to be done across the path? How was it all put together? Manually Roughly 8 hours of conference calls Roughly 500 email messages 6/4/2004 13
References Request for Comment We would like your feedback on the HOPI White Paper! hopi@internet2.edu More Information http://hopi.internet2.edu http://abilene.internet2.edu http://www.nationallambdarail.org heather@internet2.edu 6/4/2004 14
6/4/2004 15