Download UCLP International transit service

UCLP International transit service
Bill St. Arnaud
CANARIE Inc – www.canarie.ca
[email protected]
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 3rd 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
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
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
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
UCLP roadmap:
Extension of the network into the application
Single Computer or
WS instance of an orchestration
VPN extends into computer
to specific processes
zzzz:410:0:1
Instrument
Web service or
software process
User A
xxxx:410:0:1
xxxx:410:0:4
xxxx:410:0:2
CA*net 4
Routing daemon
Web service
xxxx:410:0:3
xxxx:410:0:5
Web service or
software process
Interface Card or port
yyyy:410:0:1
VPN Links
User B
UCLP with BPEL: End to end
choreography
OptiPuter, JIT admin orchestration UCLP admin orchestration
2
OptiPuter, JIT
ODIN, GMPLS
Bandwidth
Reservation
WS
UCLP
WS
2
UCLP
WS
3
4
4
3
1
2
3
LightPathConectionPT
LightPathConectionPT
BandwidthReservationPT
Neptune/
ORION
Instrument
WS
5
4
OPenDAP
WS
InstrumentNetworkServicePT
NeptuneInstrumentServicePT
1
Neptune admin orchestration
Super user BPEL orchestration
5
End user orchestration