Software for DCN

The ideal infrastructure includes “hardened” DCN support code in all domains. In the Internet2 implementation, the control code includes the Ciena code, the DRAGON VLSR, the DRAGON NARB, and the IDC (OSCARS).  Measurement code is perfSONAR that has been modified to support DCN. Additionally, it may include Phoebus as user P2P access code.   

Hardened production code is supported by an operations staff and a 2nd level development/troubleshooting/ engineering staff. Code is maintained in a single repository for each major piece with a single location where compatible versions are kept and where scripts to download compatible code are available. In addition to the testing of each piece, interoperability testing is done and documented between pieces.

Ciena code in production is always a released version of the code. In an ideal world, this would interface with Internet2 code using standard interfaces such as GMPLS and OIF-UNI and ENNI interfaces. This code comes from Ciena; note that if other vendors participate in DCN, then their base control code will be used in place of the Ciena code.

The Internet2 DCN Software Suite ( including the DRAGON NARB, DRAGON VLSR, and the IDC -- aka OSCARS) is integrated into a single package that conforms to some selected set of standards (including DICE control plane, OGF, UNI, ENNI, GMPLS, GLIF). The DCN software suite is open [BSD license] and release managed by Internet2 in collaboration with a larger working group formed to support and develop DCN.

perfSONAR-DCN software is an extension of existing perfSONAR, and includes the ability to monitor and report on dynamic circuits across domain boundaries as well as monitor links within and between domains.  This is supported by an existing collaboration group and structure.  An initial suggestion is that perfSONAR and DCN software share a similar development structure and mechanisms for inter-organizational cooperation.

Phoebus software is orthogonal to DCN and perfSONAR. It provides support for P2P connections and is able to make effective use of networking different types of network infrastructure. Phoebus might be used to 1) limit the impact of congested local networks, 2) use DCN as alternative to sending large streams over the normal IP network, or 3) act as a way to bypass local IP networks for certain applications. While these are potentially very valuable applications, their value needs to be demonstrated. Ideally, there are Phoebus gateways between DCN switches and IP routers at each router site. Other Gateways are in locations where they have value to specific users.

Test capabilities are built into all DCN infrastructures.