HOPI / Dynamic Services Update

1. HOPI / Dynamic Services Update Rick Summerhill, Internet2 Director, Network Research, Architecture, and Technologies Tom Lehman, ISI East Jerry Sobieski, Mid Atlantic Crossroads John Vollbrecht, Internet2 Spring Member Meeting April 24, 2007 Alexandria, VA

4. Introduction • Dynamic Circuits work • Intra-domain work focuses on Ciena CoreDirectors • Inter-domain work and collaborations with the International Community • Panel • John Vollbrecht - Summary of Overall Status • Tom Lehman - Control Plane discussion and demo • Jerry Sobieski - DRAGON/HOPI status and Workshops

5. HOPI and Dynamic Circuit Services - Status Summary John Vollbrecht jrv@internet2.edu

6. Session Structure • Present status of Internet2 Dynamic Circuit Capabilities and collaborations with other infrastructure providers • Demonstrate operation of new DCS services in “prototypical” multidomain environment • Describe a way that RONS, campuses and others can participate in multidomain infrastructure

7. Status of Internet2 DCS capabilities • Internet2 has two dynamic circuit infrastructures • HOPI - Hybrid Optical/Packet Infrastructure • DCS - Dynamic Circuit Services being deployed • Both are planned to be maintained for different purposes for the intermediate term • Both use control software “DRAGON” that has been developed by the HOPI Testbed Support Center • Adapted by ISI-East to work with Ciena Infrastructure • Both use Infinera/Level3 infrastructure to provide connectivity between Access Points

8. DCS Infrastructure - status

9. Global Dynamic Circuit Infrastructure Many organizations are developing Circuit Services - sometimes called Waves or Lambdas • Internet2, ESnet /SDN, NLR, GEANT, CANARIE, JGN2, others Internet2 collaborates with several group managing/describing dynamic circuit services - DCS • DICE [Dante(GEANT), Internet2, CANARIE and Esnet • GLIF [Global Lambda Integrated Facility]

10. GEANT

11. Sapporo USA (Chicago) Sendai Thailand (Bangkok) Kanazawa Nagano Singapore Kitakyushu NICT Tsukuba Research Center Hiroshima Osaka NICT Koganei Headquarters Fukuoka Okayama Akihabara Nagoya Kochi NICT Keihanna Branch Tokyo Naha Outline of JGN2 Network February 15, 2007 *IX: Internet eXchange AP: Access Point

12. GLIF MAP August 2005

13. Standards Bodies • OGF Open Grid Forum • IETF (CCAMP) • IEEE (PTB) • OIF (ASON)

14. Dynamic Circuit Exchange Points • International networks interconnect • Currently Exchange Points provide ability to switch connections from one provider to another • In future the expectation is that these will provide the ability to switch under program control • For Exchange points that do L1 or L2 GLIF has coined the name GOLE • At Exchange points where switching (which may be single interconnection) providers must exchange information that allows interconnection under program control

15. GOLES listed on GLIF web page • * AMPATH - Miami • * CERN - Geneva • * CzechLight - Prague • * HKOEP - Hong Kong • * KRLight - Daejoen • * MAN LAN - New York • * MoscowLight - Moscow • * NetherLight - Amsterdam • * NGIX-East - Washington D.C. • * NorthernLight - Stockholm • * Pacific Wave (Los Angeles) - Los Angeles • * Pacific Wave (Seattle) - Seattle • * Pacific Wave (Sunnyvale) - Sunnyvale • * StarLight - Chicago • * T-LEX - Tokyo • * UKLight - London

16. Interernet2 Dynamic Circuit Connectors • HOPI and DCS provide access to Dynamic Circuits in logically identical ways • Access ports allow circuits to be multiplexed over backbone to other access circuits • Access may include control plane interaction • Connector locations are shown on map in previous slide

17. Global Dynamic Circuits

18. Specific Projects • Implement basic DRAGON control plane to run on Ciena infrastructure • See demo • Testing of Ethernet paths • Testing with Spirent has been completed, will be documented in next few weeks • Working to test ethernet between different hardware, at 10G and 1G.

19. Projects • Work with ESnet to create common module that runs with both ESnet and DRAGON to support authentication of users and trust between domain controllers • Authentication, Authorization, Scheduling • Status- • demonstrated interoperability at control level • Demonstrated ability to make Ethernet path that extends through HOPI(dynamic) and ESNet(static) • Expect to be entirely dynamic in next week or so • Plan is to integrate this into DRAGON • Hope to make this code generally available

20. OSCARS

21. SC07 protocol demo plans • University of Amsterdam • Plan to collaborate on developing specific capabilities in DRAGON • Will establish permanent connection between HOPI and UvA • Will do SC07 demo together • Token signaling • Topology sharing

22. Collaborations DICE • “Stitching” project to describe data layer interconnections between segments of a PTP path • Topology exchange • Reviewing schemas GLIF • Collaborating on developing control plane interoperation between domains

23. DVTS

24. TeraPaths • TeraPath sites use QoS within site • Between Sites they may create special path for some flows • MPLS path added over IP • Or create dynamic ckt between routers • Looking into how TeraPaths controllers can configure routers to send specific flows over newly created ckt

25. Issues in finding and authorizing Segments for dynamic interdomain PTP circuits • Networked topology • Topology exchange, path computation • Types of exchange - OSPF/BGP • Grid/ VO approach • Resource allocation that includes computation, storage and networking Implementation approach is to create “InterDomain Contoller” that can participate in either approach

26. Status Summary • Making progress in developing and deploying core infrastructure • Collaborating with dynamic circuit community on how it will develop • Working to get users / RONS/ Campuses connected to core • Currently we are at the start of an operational global infrastructure • future is being worked out • users and user needs will shape future development

27. Dynamic Circuit Services Control Plane Overview April 24, 2007Internet2 Member MeetingArlington, Virginia Tom Lehman University of Southern California Information Sciences Institute (USC/ISI) Chris Tracy University of Maryland Mid-Atlantic Crossroads (MAX)

28. Outline • Internet 2 Dynamic Circuit Services Architecture • Control Plane Overview • Control Plane Messaging Example • I2 DCS Demonstration

29. I2 DCS Control Plane Objectives • Multi-Service, Multi-Domain, Multi-Layer, Multi-Vendor Provisioning • Basic capability is the provision of a “circuit” in above environment • In addition, need control plane features for: • AAA • Scheduling • Easy APIs which combine multiple individual control plane actions into an application specific configuration (i.e., application specific topologies)

30. Multi-Domain Control PlaneThe (near-term) big picture • Multi-Domain Provisioning • Interdomain ENNI (Web Service and OIF/GMPLS) • Multi-domain, multi-stage path computation process • AAA • Scheduling GEANT TDM Internet2 Network RON RON Dynamic Ethernet Dynamic Ethernet TDM Domain Controller ESNet Ctrl Element Ethernet Data Plane SONET Switch Control Plane Adjacency IP Network (MPLS, L2VPN) LSP Router

31. Internet2 Dynamic Circuit Services (DCS) I2 DCS: Ciena CoreDirector I2 HOPI: Force10 E600 10 Gigabit Ethernet 10 Gigabit Ethernet 10 Gigabit Ethernet OC192 SONET/SDH 1 Gigabit Ethernet or SONET/SDH 1 Gigabit Ethernet

32. Force10 E600 HOPI Ethernet Switch Ciena Core Director SONET Switch Raptor ER-1010 Ethernet Switch DCS Demonstration Actual Topology • HOPI Network Partitioned to mimic RONS connected to edge of Internet2 DCS • Provisioning across subset of currently deployed Ciena CoreDirectors HOPI East Internet2 DCS NEWY WASH CHIC HOPI Central CHIC NEWY CLEV Internet2 Office DRAGON MCLN Ann Arbor PITT PHIL ARLG WASH

33. Client “Service” ViewIntraDomain Service Request Source Address Destination Address Bandwidth (50 Mbps increments) VLAN TAG (None | Any | Number) User Identification (certificate) Schedule Dynamically Provisioned Dedicated Resource Path (“Circuit”) Domain Controller b 1 csa 2 CSA can run on the client or in a separate machine (proxy mode) csa a Client B Ethernet Mapped SONET or SONET Circuits VLSR Client A Domain Controller Switch Fabric Internet2 DCS • Items 1,2 represent service request/approval • Items a,b represent service instantiation (signaling)

34. What is the Internet2 DCS Service? • Physical Connection: • 1 or 10 Gigabit Ethernet • OC192 SONET • Circuit Service: • Point to Point Ethernet (VLAN) Framed SONET Circuit • Point to Point SONET Circuit • Bandwidth provisioning available in 50 Mbps increments • How do Clients Request? • Client must specify [VLAN ID|ANY ID|Untagged], SRC Address, DST Address, Bandwidth • Request mechanism options are GMPLS Peer Mode, GMPLS UNI Mode, Web Services, phone call, email • Application Specific Topology is an XML request for one or more individual circuits • What is the definition of a Client? • Anyone who connects to an ethernet or SONET port on an Ciena Core Director; could be RONS, GIgaPops, other wide area networks, end systems

35. InterDomain • From a client perspective, an InterDomain provisioning is no different than IntraDomain • However, additional work for Domain Controllers Domain Controller Domain Controller Domain Controller CSA CSA RON Dynamic Infrastructure Ethernet VLAN RON Dynamic Infrastructure Ethernet VLAN Internet2 DCS Ethernet Mapped SONET

36. Need more work on AAA, Scheduling AAA AAA AAA A A A A 3 3 1 2 5 Provisioning Flow Domain Controller Domain Controller Domain Controller GUI AST Flexible Edge Mappings (port(s), tag, untag) XML 4 NARB VLSR RON Dynamic Infrastructure Ethernet VLAN RON Dynamic Infrastructure Ethernet VLAN Internet2 DCS Ethernet Mapped SONET 1. Service Request 2. Path Computation Request 3. Recursive Per Domain Path Computation/Scheduling Processing 4. Path Computation/Scheduling Response (loose hop route object returned) 5. Service Instantiation (Signaling) (includes loose hop expansion at domain boundaries) A. Abstracted topology exchange

37. VLSR(Virtual Label Switching Router) • GMPLS Proxy • (OSPF-TE, RSVP-TE) • Local control channel • CLI,TL1, SNMP, others • Used primarily for ethernet switches CLI Interface One NARB per Domain • Provisioning requests via CLI, XML, or ASTB

38. VLSR uni-subnet LSR downstream LSR upstream Integration Core Director Domain into the End-to-End Signaling signaling flow uni, tl1 uni, tl1 data flow Ciena Region CD_a CD_z subnet signaling flow • Signaling is performed in contiguous mode. • Single RSVP signaling session (main session) for end-to-end circuit. • Subnet path is created via a separate RSVP-UNI session (subnet session), similar to using SNMP/CLI to create VLAN on an Ethernet switch. • The simplest case: one VLSR covers the whole UNI subnet. • VLSR is both the source and destination UNI clients. • This VLSR is control-plane ‘home VLSR’ for both CD_a and CD_z. • UNI client is implemented as embedded module using KOM-RSVP API.

39. Internet2 DCS RON Central RON East DRAGON Ann Arbor DCS Demonstration Logical Topology TDM Switch Ethernet Switch End System

40. Internet2 DCS RON Central RON East DRAGON Ann Arbor Dedicated Layer 2 NetworkSite to Site • Dynamically set up Site to Site dedicated layer 2 networks • End Sites attachment is flexible: • One Port (untagged or tagged) • Multiple Ports (untagged or tagged)

41. Internet2 DCS RON Central RON East DRAGON Ann Arbor Dedicated Layer 2 NetworkSystem to System Service Connections • Dynamically set up dedicated layer 2 host to host connection • End System termination point is flexible: • One “circuit” (untagged or tagged) • Multiple “circuits” (tagged) • reflected as multiple virtual interfaces on the end system

42. Internet2 DCS RON Central RON East DRAGON Ann Arbor Application Specific Topology Example • Application specific topologies refer to the: • automatic set up of multiple provisioned paths and • coordinated end system application control • The above example show three systems connecting to a single “server/processing node” as might be required for: • data repository access • content distribution infrastructure • data streaming to a centralized processing center

43. Demo • Ciena Core Director • “NodeManager” • Graphical User Interface • Monitoring and Control Timeslot Map Network Utilization Monitor

44. Force10 E600 HOPI Ethernet Switch Ciena Core Director SONET Switch Raptor ER-1010 Ethernet Switch DCS Demonstration Actual Topology • HOPI Network Partitioned to mimic RONS connected to edge of Internet2 DCS • Provisioning across subset of currently deployed Ciena CoreDirectors HOPI East Internet2 DCS NEWY WASH CHIC HOPI Central CHIC NEWY CLEV Internet2 Office DRAGON MCLN Ann Arbor PITT PHIL ARLG WASH

45. Internet2 DCS RON Central RON East DRAGON Ann Arbor Dedicated Layer 2 NetworkSite to Site • Dynamically set up Site to Site dedicated layer 2 networks • End Sites attachment is flexible: • One Port (untagged or tagged) • Multiple Ports (untagged or tagged)

46. Site to Site Provision RequestDRAGON ARLG to Ann Arbor

48. Thank You

49. extras

50. DRAGON Control PlaneKey Components • Network Aware Resource Broker – NARB • Intradomain listener, Path Computation, Interdomain Routing • Virtual Label Swapping Router – VLSR • Open source protocols running on PC act as GMPLS network element (OSPF-TE, RSVP-TE) • Control PCs participate in protocol exchanges and provisions covered switch according to protocol events (PATH setup, PATH tear down, state query, etc) • Client System Agent – CSA • End system or client software for signaling into network (UNI or peer mode) • Application Specific Topology Builder – ASTB • User Interface and processing which build topologies on behalf of users • Topologies are a user specific configuration of multiple LSPs