1. Phoebus Network cyberinfrastructure to improve end-to-end performance
Uses adaptation points in the network to break TCP connections into a series of shorter connections

2. Phoebus How applications can use Phoebus
Modified to call the Phoebus client library
Use a transparent wrapper library to allow the application to use Phoebus without changes
Have an adaptation point in the network proxy the application’s TCP connections

3. Phoebus
Why DCN?
Circuits allow the use of better transport protocols than TCP over more of the end-to-end connection
Dynamic circuits are a good fit for Phoebus due to the possibility of needing to connect to any of a wide variety of adaptation points.

4. Phoebus Converting our service to use DCN
Current: Can allocate circuits effectively for short or known duration connections
Required 2-3 days to enable our service to request circuits
Future: Does not effectively handle arbitrary length connections
Differences between the Phoebus model and the OSCARS model

5. Phoebus Sample Usage Deployment Plans
Being used regularly by a researcher at Syracuse University to retrieve data from the LIGO Project
Deployment Plans
Current Adaptation Points:
Salt Lake City
New York
Expanding the Phoebus service to the all 9 POPs in the Internet2 network