Dynamic Network Services In Internet2

1. Dynamic Network Services In Internet2 John Vollbrecht /Dec. 4, 2006 Fall Members Meeting

2. Internet2 Dynamic Services Internet2 Dynamic Circuit Services Presentation Outline • Architecture • Using Dynamic Services • Data Plane and Control Plane • Connecting to other National and International Networks • Initial connections to dynamic services • Potential applications • Possible scheduling models • Role of HOPI

3. Internet2 Dynamic Circuits Core Infrastructure - DWDM layer 1 network Internet2 Network Architecture IP and Dynamic Circuit net overlay of core infrastructure

4. Internet2 Dynamic Circuits MultiService Switching Infrastructure Dynamic Circuit Network Topology

5. Internet2 Dynamic Services Internet2 Dynamic Circuit Deployment • Architecture • Dynamic Circuits infrastructure uses circuits provided by the core infrastructure interconnected with “Multiservice Switching boxes” located at PoPs • Each box has a static circuit to each topologically adjacent box • The Multiservice Switching infrastructure uses circuits from core infrastructure • Circuits between boxes carry multiplexed streams which carry user circuits • Each stream consisits of multiple STS-1s (50 Mbps) • Number of streams limited by total bw of circuit between boxes

6. Internet2 Dynamic Circuits MultiService Switching Box

7. Internet2 Dynamic Circuits MultiService Switching

8. Timing • Project Rollout is in Phases • Phase 1 NY, Chicago, Washington • January • Phase 2 Raleigh, Atlanta, Louisville • April • Phase 3 Kansas City, Baton Rouge, Houston, Seattle • May • Phase 4 Salt Lake City, Seattle, Los Angeles • July

9. Internet2 Dynamic Services Using Dynamic Circuits • Typically Internet2 provides a segment of a point to point circuit between users • Dynamic Circuit Infrastructure connects to other Domains • Regional Networks • Other National and International Networks • Creating circuits dynamically assumes an infrastructure of nodes and links in place over which the dynamic circuit is to be established • Initiating a dynamic circuit is done by making a request to a dynamic circuit controller • Controller may be a person or software- more on this later

10. Internet2 Dynamic Circuits Connecting to Dynamic Circuit Services

11. Internet2 Dynamic Services Data Plane and Control Plane • Data Plane provides the circuit segments that are joined to make an ETE circuit • Control Plane creates ETE circuits by • selecting a path of circuit segments • Controlling switching of segments to create the path • Tear down ETE circuits and return segments • Both are part of dynamic circuit service

12. Internet2 Dynamic Circuits Control and Data Planes

13. Internet2 Dynamic Services Control Plane • Initiating a dynamic circuit is done by making a request to the control plane • Each domain has its own control plane • Control plane may be • NOC taking requests and configuring devices • Control plane software that configures devices • Setting up circuits across domains requires coordination of control planes of each domain • Control plane software for single domains is commercially available • Control plane software that coordinates between domains is a being studied and worked on in standards bodies • HOPI has working code that has a pilot version of cross domain control coordination

14. Internet2 Dynamic Services Connecting to other International and National Networks • The expectation is that there will be an international infrastructure of dynamic circuit providers • Some will interconnect directly to each other • Some will interconnect at well defined exchange points • GLIF uses term GOLE • Global Optical Lambda Exchange

15. International Service Trials

16. Internet2 Dynamic Services Initial Connections to Dynamic Circuit • Initial connection to Internet2 may be by a static VLAN from user • Switching will be done by Internet2 • Control of VLAN creation can be added later • Experimentation with software control of VLANs can be done with HOPI

17. Issues Stitching Ethernets and SONET Finding Paths across multiple domains Controlling circuits across domains Monitoring and debugging Collaborations ESNet and GEANT making cross domain circuits Establishing initial naming conventions Establishing “stitching” rules Many others in various arenas, including Amsterdam, NICT, CANARIE Work in IETF, OGF Connecting between networks

18. HOPI Role Hybrid Optical and Packet Infrastructure • HOPI is a testbed for developing and deploying dynamic circuit services and applications • HOPI has experimental control plane software which may be used by other domains • HOPI can be used to test new applications prior to roll out on persistent dynamic network • HOPI is not for applications that cannot permit having