1. UCLP International transit service Bill St. Arnaud CANARIE Inc – www.canarie.ca Bill.st.arnaud@canarie.ca

2. UCLP Objectives >Allow institutions to integrate wavelengths and fiber from different suppliers and integrate with institution's network management domain – And offer child VPNs to their users >Create discipline specific re-configurable IP networks – Multihomed network which bypasses firewalls with direct connect to servers and routers >Provide layer 1 transit services to 3 rd parties – Provides guaranteed IP throughput and packet priority with no AUP restrictions – Allows international networks to directly peer with each other and control their international peering relationships – Allows for direct Europe, Asia and South America peering without dependency on North American IP networks

3. UCLP partners >Internet2 – Bob Riddle and Shibboleth team >I2Cat – Barcelona – Sergei Figuerola and team – Deployed on I2CAT with Nortel 5200 >Korea – KISTI – Kim Dongyun and team – for deployment on KREOnet >Taiwan – George Yeh and team – for deployment on TANet2 >Canadian Regional networks – ORANO, BCnet, Netera >Canadian Grids – Westgrid, International Grid Testbed >etc

4. International Transit Partners & Policy >Korea – 1Gbe lightpath from Seattle to Chicago >Taiwan – 2 x OC12 lightpath from Seattle to Chicago >Ireland – 1Gbe lightpath from NYC to Chicago >Others under discussion >NO CHARGE for demos or short term lightpath usage to GLIF participants >Cost recovery or swaps for long term lightpaths (e.g. year or longer) – We prefer swaps as much as possible

5. UCLP – version 2.0 >All instruments, sensors, software processes and network elements exposed as WSDL web services >Hardware, software and network services linked together by end user with BPEL – WSDL and BPEL provide for “universal” end to end control plane from application to the network >Elimination of network made up of layers – Every layer a web service that can communicate with other WS >The network topology and architecture and how it interfaces with the application is defined by the end user and not the network engineer

6. UCLP roadmap: Extension of the network into the application Instrument Web service or software process Web service or software process Routing daemon Web service User A User B Single Computer or WS instance of an orchestration Interface Card or port VPN Links VPN extends into computer to specific processes CA*net 4 xxxx:410:0:1 xxxx:410:0:2 xxxx:410:0:3 xxxx:410:0:4 xxxx:410:0:5 yyyy:410:0:1 zzzz:410:0:1

7. UCLP with BPEL: End to end choreography Neptune/ ORION Instrument WS OPenDAP WS OptiPuter, JIT ODIN, GMPLS Bandwidth Reservation WS UCLP WS UCLP WS NeptuneInstrumentServicePT BandwidthReservationPT LightPathConectionPT InstrumentNetworkServicePT Super user BPEL orchestration 1 2 3 4 5 1 2 2 3 3 4 4 5 End user orchestration Neptune admin orchestration OptiPuter, JIT admin orchestration UCLP admin orchestration