1. The HOPI Project Rick Summerhill
Associate Director, Network Infrastructure
Joint-Techs Meeting
Columbus, OH
23 February 2019

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 – see
Implement testbed over the next year
Coordinate and experiment with other similar projects
Design Team
2/23/2019

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
2/23/2019

4. HOPI Resources
The Abilene Network – MPLS tunnels and the packet switched network
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, DRAGON, etc.)
2/23/2019

5. MAN LAN Ethernet Switch ONS Cisco 15454
Layer2 Interconnectivity – Classic exchange point
VLANs between connectors
ONS Cisco 15454
TYCO/IEEAF Circuit moved to experimental facility
Circuit was router to router, now is ONS to ONS
Ability to map circuits to Abilene or for other experimental reasons
OC-192s: CANARIE, Surfnet, Abilene
Experiments with the international community
2/23/2019

6. Abilene/NLR Map
2/23/2019

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?
2/23/2019

8. HOPI Basic Service
Given the available resources, we cannot use multiple waves to study new architectures – have only a limited number of waves
Instead we’ll model waves using lower bandwidth “deterministic” paths – paths that resemble circuits – “lightpaths”
Basic service – A 1 or 10 GigE unidirectional point-to-point path with reasonable jitter, latency, and loss characteristics
Access – Direct to HOPI node or an MPLS L2VPN tunnel through Abilene
2/23/2019

9. HOPI Node A fiber cross-connect switch
Ability to switch the entire NLR wave to Abilene, to a RON, or to pass through the wave
An Ethernet switch device to partition the wave into 1 GigE paths when necessary
Control devices
Ad hoc control plane computer
Measurement computer
Experimental computer
Control and data planes must be disjoint
Out of band access
2/23/2019

10. HOPI Node
2/23/2019

11. Connector Interface
A 1 or 10 GigE connection to the FXC, either dark fiber or a provisioned service, including NLR
An MPLS L2VPN service through Abilene to the Ethernet switch or TDM device
Provides immediate connection to the Internet2 NLR wave from Abilene
2/23/2019

12. Control Plane Phase 1 – Manual Configuration
Ad hoc control of devices that don’t support control plane protocols
Understand control plane ideas
Phase 2 – Intra-domain Configuration
Automate software control of setup
Investigate temporal and topological extent of paths
Phase 3 – Inter-domain Configuration
May require extensions to standards based protocols
2/23/2019

13. Experiments Planned Experiments – 15 to 20 initial experiments
Dynamic Provisioning
Deterministic Paths
Applications Based
Miscellaneous
Encourage use by the community for experimentation – both operational and research communities
Can start in near future by using MPLS tunnels from Abilene
2/23/2019

14. Recent Activities
Have formed the HOPI Corporate Advisory Team (HOPI CAT)
Bring the considerable mindshare from the corporate community into the project.
Currently looking at partnership opportunities.
Close to making a decision on locations for the first 3 – 5 HOPI nodes
Seattle, Chicago, New York – interact with the international community in accessible locations
Los Angeles – CalTech and HENP
Washington DC – MAX and DRAGON experiments
2/23/2019

15. HOPI CAT Avici Ciena Cisco Comcast Force10 Global Crossing Infinera
Juniper
Movaz
Nortel
Qwest
WilTel
2/23/2019

16. 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)
2/23/2019

17. 2/23/2019

18. Control Plane Was bandwidth available, how much? What path to take?
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
2/23/2019

19. 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 messages
Will provide report in the near future
2/23/2019

20. References
Request for Comment – We would like your feedback on the HOPI testbed
More Information
2/23/2019

21. 2/23/2019