1. OSCARS Overview Path Computation Topology Reachability Contraints Scheduling AAA Availability Provisioning Signalling Security Resiliency/Redundancy OSCARS Guaranteed Bandwidth Virtual Circuit Services

2. Using OSCARS Web-Based User Interface (WBUI) –SSL connection to server –Username and password login SOAP Messages –SSL connection to server –WSDL service description –Signed SOAP messages <wsdl:definitions name="OSCARS" targetNamespace="http://oscars.es.net/OSCARS" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:tns="http://oscars.es.net/OSCARS"> This is WSDL for the OSCARS public reservation interface. These messages must be signed using the following WS-secuirty standards. The message is time stamped and includes the X.509 certificate of the signing entity. The timestamp, certificate and message body are all signed. DRAFT V1.0 Nov 2006 <xsd:schema targetNamespace="http://oscars.es.net/OSCARS" elementFormDefault="qualified" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://oscars.es.net/OSCARS"> …

3. Source Sink MPLS labels are attached onto packets from Source and placed in separate queue to ensure guaranteed bandwidth. Regular production traffic queue. Interface queues SDN IP IP Link SDN Link RSVP, MPLS enabled on internal interfaces standard, best-effort queue high-priority queue LSP between ESnet border routers is determined using topology information from OSPF-TE. Path of LSP is explicitly directed to take SDN network where possible. On the SDN Ethernet switches all traffic is MPLS switched (layer 2.5). Layer 3 VC Service: Packets matching reservation profile IP flow-spec are filtered out (i.e. policy based routing), policed to reserved bandwidth, and injected into an LSP. Layer 2 VC Service: Packets matching reservation profile VLAN ID are filtered out (i.e. L2VPN), policed to reserved bandwidth, and injected into an LSP. Label Switched Path SDN Link The Mechanisms Underlying OSCARS

4. ESnet4 IP + SDN Final Configuration for 2007 Denver Seattle Sunnyvale LA San Diego Chicago Raleigh Jacksonville KC El Paso Albuq. Tulsa Clev. Boise Wash DC Salt Lake City Portland Baton Rouge Houston Pitts. NYC Boston Philadelphia Indianapolis Nashville (1(3)) ESnet IP core (10Gb/s) ESnet Science Data Network core ESnet SDN core, NLR links (existing) Lab supplied link LHC related link Metro Area Network International IP Connections Atlanta OC48 Layer 1 optical nodes at eventual ESnet Points of Presence ESnet IP switch only hubs ESnet IP switch/router hubs ESnet SDN switch hubs Layer 1 optical nodes not currently in ESnet plans Lab site

5. ESnet4 Core networks 50-60 Gbps by 2009-2010 (10Gb/s circuits), 500-600 Gbps by 2011-2012 (100 Gb/s circuits) Cleveland Europe (GEANT) Asia-Pacific New York Chicago Washington DC Atlanta CERN (30+ Gbps) Seattle Albuquerque Australia San Diego LA Denver South America (AMPATH) South America (AMPATH) Canada (CANARIE) CERN (30+ Gbps) Canada (CANARIE) Europe (GEANT) Asia- Pacific Asia Pacific GLORIAD (Russia and China) Boise Houston Jacksonville Tulsa Boston Science Data Network Core IP Core Kansas City Australia Core network fiber path is ~ 14,000 miles / 24,000 km 1625 miles / 2545 km 2700 miles / 4300 km Sunnyvale Production IP core (10Gbps) SDN core (20-30-40-50 Gbps) MANs (20-60 Gbps) or backbone loops for site access International connections IP core hubs Primary DOE Labs SDN hubs High speed cross-connects with Ineternet2/Abilene Possible hubs USLHCNet

6. Today 2008 2009 2010 ESnet Virtual Circuit Service Roadmap Dynamic virtual circuit services for Layer 3 (IP) connections (using MPLS) Dynamic virtual circuit services for Layer 2 (Ethernet VLAN) connections (using MPLS) Dynamic virtual circuit services for Layer 1 (TBD) connections (using GMPLS) Initial production (L2-L3) service Full production service