| InterDomain Dynamic Circuit Network Demo |
| Joint Techs - Hawaii Jan 2008 | |
| John Vollbrecht, Internet2 | |
| jrv@internet2.edu |
| Interdomain Dynamic Circuit Network |
| Global network that allows dynamic ckts to be created across multiple circuit networks | |
| Internet2, ESnet and Dante have worked in the DICE control plane working group | |
| Developed and continue to develop IDC protocol | |
| Interdomain dynamic circuit infrastructure is in place and being enhanced | |
| Additional Collaboration with Nortel and University of Amsterdam |
| Agenda |
| SC07 presentation overview | |
| Infrastructure at time of SC07 | |
| Weather Map of DCN today | |
| Quick overview of applications on weathermap | |
| GOLEs in DCN | |
| IDC architecture | |
| Connecting a Campus User | |
| DCN software suite | |
| DCN status |
| Global DCN
Infrastructure at SC07 timeframe |
| Physical Infrastructure at SC time |
| Current Infrastructure of DCN |
| LHC applications on DCN |
| Phoebus and DCN |
| Phoebus breaks tcp connections into pieces to improve performance http://e2epi.internet2.edu/phoebus.html | |
| Phoebus has the ability to create and use DCN a piece of the connection | |
| Phoebus gateways are in place in Salt Lake and Syracuse NY now, being used | |
| Other Phoebus gateway have been used in Ireland, Greece, and Poland, and more are being deployed in US now. |
| DCN GOLEs Exchange Points for Dynamic Circuits |
| GOLE policy issues |
| Individual DCN GOLE is policy free | ||
| GOLE is non blocking | ||
| If both links agree path between them is made | ||
| This is initial demo being done at here and at JT | ||
| When GOLEs connect to each other | ||
| Link between GOLEs is limited resource | ||
| Now have to have policy that determines what is allowed on inter GOLE link | ||
| GOLE role :) may be | ||
| ÒsuperdomainÓ aggregating info on other domains | ||
| Part of GOLE domain that consists of only GOLES, administered by some standards body | ||
| GLIF role in defining DCN GOLE? | ||
| IDC role in DCN |
| IDC is what allows DCNs in different domains communicate | ||
| IDC communicates with user and with other domains | ||
| IDC requests services from its Domain Controller | ||
| Different implementations from | ||
| Internet2, Esnet, GEANT, Nortel | ||
| IDC Architecture |
| RONs and Campuses connecting to DCN |
| DCN Software Suite |
| Suite combines DC and IDC software | ||
| DC - DRAGON | ||
| IDC - OSCARS | ||
| Suite is a Òmatched pairÓ of software | ||
| Version 0.1 released Jan 2, 2008 | ||
| Version 0.2 Jan 18, 2008 | ||
| Small changes and documentation update | ||
| Version 0.3 planned for April 2008 | ||
| Software suite matches what is running in Internet2 DCN and ESNet SDN | ||
| Monitoring Dynamic Circuits |
| Monitor plane - both sides can monitor and deploy | ||
| Monitor links for infrastructure status and activity | ||
| Monitor ETE circuits 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 circuits make naming and syntax standards imperative | ||
| Work with operations to define what is needed - especially between domains | ||
| Operational State of DCN |
| Internet2 and ESNet are dynamic circuits are in ÒdevelopmentalÓ state | ||
| Good availability, ready to work with applications developing capabilities on network | ||
| Want to tune functions and policy to meet needs of real users | ||
| Support mainly from developers, starting to work with operations staff to transfer operational tasks to them - probably 6-12 months away | ||
| Support not 24/7, expect to respond to problems in 24 hours during work week. Often better. | ||
| Monitoring and debugging in development | ||
| Other DCN networks are in earlier stages | ||
| Summary |