1. Interdomain Dynamic Circuits
Comments-
Interdomain international network connections
Independent networks with 4 different implementations of DICE IDC protocol
implementations [Internet2, Esnet (common but with differnces), GEANT and Nortel]
I2 and Esnet are “developmental” - ready to support development of programs, will remain operational after SC
GEANT2/AutoBAHN will be up experimentatlly for about a year after SC
UvA - continue collaboration on development
Nortel - plans to continue collaborations
Apps - shown in future slides
End of demo show how a laptop can connect to a remote host over DNC
Before proceeding show weathermap and activity on actual net
Also Aaron’s link map if available
DCN showfloor setup
MAC Mini connected to DCN for Nortel, DVTS to AA
MM or Laptop
-Adobe/ PP
-Weathermap -- DCN (jarda)
Lambda Station map (aaron) -Web service request
Need and IP Port for debugging
Need Laptop port for calling AA
WeatherMap

2. Physical Infrastructure at SC time
At this point it is good to introduce Jarda’s map of Internet2 and show what a domain looks like and how links go up and down, extend of the I2 network and compare to other networks on this physical infrastructure

3. Internet2 DCN and Esnet SDN Interoperation
This is in my mind the really big application -
-- shows how LHC community can intecommunicate sharing L2 dynamic infrastructure of I2 and Esnet
Thes apps are going to continue after the show
Can show ongoing apps on weathermap and on LS sequence
. Show LambdaStation web page
Point out magnitude of traffic

4. GEANT2/AutoBAHN Interoperation with Internet2 and ESnet
This is important long term - it is extending DCN to Europe. Europe has not made a permanent commitment to this, but I believe the infrastructure will come up in an expermental way in early 2008 and stay up for a year. Probably will be renewed, but who knows.
ESNet is shown for 2 reasons =
1) traffic between NY and Chi on the path from Europe to Salt Lake could take either I2 or Esnet
2) In long term we expect that there will be Esnet traffic to Europe independent of Internet2
the application using this is phoebus - see the phoebus DCN description later

5. Phoebus over Dynamic Circuits
Phoebus “network”
Phoebus infrastructure on DCS
Phoebus over dynamic ckts - this shows how phoebus acts as a network betweeh host in different locations
- host wanting to connect to each other go thru phoebus gateway locally to phoebus gateway remote.
- phoebus makes a dynamic connection between phoebus gateways - using DCN
Phoebus demo booth behind us

6. University of Amsterdam connection for experimental development
This is last Interdomain stuff to be made to work. As of Saturday before SC it still is not working, although we hope to make at least some of it work before the show
This is an example of experimental protocol development using the IDC protocal as a base
This is an EU Phosphorous project - using what is a GRID framework for setting up calls, - it uses IDC protocol
CineGrid content sent from Amsterdam to SC
Experimental demo show use of token between reservation and ckt setup sequences

7. Nortel Interaction with Interdomain Dynamic Circuits
This is an example of commercial company collaborating on development of IDC protocol
expect to continue collaboration to enhance the protocol after SC
Nortel implements IDC protocol as a “wrapper” over its DRAC controller
Uses IDC to setup ckts between Ottawa and showfloor to send Video And between Nortel and Internet2 booths to do Grid File Transfer

8. SCO7 Dynamic Circuit infrastructure
This shows how the show floor is connected -- might talk about what is going on at booth -
Video from Nortel,
Video from AA
Connection to host in AA by laptop

9. Monitoring Dynamic Circuits
Monitor plane - both sides can monitor and deploy
Monitor links for infrastructure status and activity
Monitor ETE Ckts for user status, traffic and debugging
Ongoing development and standards activity in this area
perfSONAR is our choice of tool - will be enhanced to add additional support
Dynamic ckts make naming and syntax stds imperative
This is a next step for dynamic ckt. perfSONAR is a good story, but doesn’t do the job right just yet. Not sure of when a version that supports this better will be available, but hopefully soon.
A similar slide for AAA that goes beyond the domain to domain authentication could be deployed, but it is harder to explain quickly

10. Future Development
DICE IDC Protocol development will continue, perhaps with expanded group
Will collaborate with groups developing protocols being developed in other standards groups
IETF, IEEE, OIF, ITU, OGF and others
GLIF control plane development
Some major areas of future development
Monitoring interdomain dynamic ckts
Managing interdomain reservations and guarantees
Sharing authorization between reservation and scheduling step and ckt setup step
Dynamic scheduling of ckts using different technologies
Topology description and sharing between domains
AAA between domains
GRID model vs Network model infractures
There are more areas - for most people this is probably just a list. Some may suggest additional items - would be good to keep track of them.

11. Making a connection from Showfloor
I suggest showing this slide, and pointing out that this is what can be done from anywhere, not just the show floor as long as the user is authorized to do ti
Point out on weather map the connection to be make
Bring up web page and ask for voluteer to make a connection or use local laptop
The demo here allow a user to plug a laptop into a port on the floor and then go to a web page and request a circuit to a host in AA.
This user is a demo user and the only connection allowed is a 150Mb connection from the show floor to AA
Might want to point out what happens when connection is requested -
-request goest to IDC I2.SC07.internet2.edu,
- forwarded to IDC dcn.internet2.edu
Similar to what would happen if one made a connection from a regional to a host on Internet2
Note that connection is simple because infrastructure is in place.

12. The End
Questions?

13. Steps to adding a regional
Connect a host to I2 DCN
using static connection thru a switch
request dynamic connection across I2 from I2 IDC
When second host want to connect thru same switch and share ckt bw from DCN to switch
implement dynamic control on the regional switch using “dynamic control suite”
request dynamic connection from regional IDC
use Lookup service to map host name to L2 link-id
Moving from step 1 to step 2
change Lookup Service to use
regional link-id associated instead of I2 DCN link-id
- user changes nothing