1 TeraPaths and dynamic circuits  Strong interest to expand testbed to sites connected to Internet2 (especially US ATLAS T2 sites)  Plans started in early 2007  Collaboration workshop at BNL in May 2007  Series of modifications and additions to TeraPaths code to request (through OSCARS) and utilize dynamic circuits  Expansion of testbed to BU through NoX and second (L2) connection to UMich through Merit/MiLR  SC’07 demo in November 2007

2 Using a circuit  Dynamic circuit appears as VLAN connecting end site border routers with single hop  Cannot use flow ID data directly  Flow must be directed to the proper VLAN  WAN admission performed within end site LAN  Select VLAN with Policy Based Routing (PBR) at both ends  Route can be selected on a per-flow basis WAN switch border router

3 End site VLAN setup for L2 TeraPaths-controlled “virtual border” router (directs flows w/PBR) e.g.,1 to X, 2 to Y WAN Site’s Border Router trunked VLAN pass-thru 50 VLAN ids ( ) 3550  X  Y  3599 interfaces trust DSCP TeraPaths-controlled host router #X #Y DSCP-friendly LAN host 1host nhost to X 2 to Y can be the same device Regional Provider’s Router

4 Interoperating with WAN Services  TeraPaths “proxy” servers  Implement interface required by TeraPaths core  Hide WAN service differences  Clients to WAN web services (currently OSCARS / DRAGON)  Close cooperation with ESnet and I2 development teams  Submit reservations for MPLS tunnels or dynamic circuits  Handle security requirements  Handle errors

5 TeraPaths Testbed during SC’07 US ATLAS T2 sites BNL OU UC/IUUMichBU SLAC ESnet UTA I2 NLR NoX StarLight UltraLight MiLR/Merit L2 (dynamic circuit) L3 (MPLS tunnel) L2 and L3

6 Weather Map