OSCARS Collaborative Work
Collaborative projects are critical in extending OSCARS developments into new technologies like software-defined networking.
ARCHSTONE (Advanced Resource Computation for Hybrid Service and TOpology NEtworks) Project
ARCHSTONE is a DOE-funded project between collaborators at the University of New Mexico, University of Southern California (USC) Information Sciences Institute (ISI) East, and Energy Sciences Network (ESnet). This collaboration builds technologies that provide next-generation multi-layer network provisioning and computation. The project's Network Service Interface (NSI) is based on an extenstion to the OSCARSv0.6 PCE API.
MEICAN (Management Environment of Inter-domain Circuits for Advanced Networks)
OSCARS collaboration work with Rede Nacional de Ensino e Pesquisa, the Brazilian National Research and Education Network (NREN). Read more.
COMMON (Coordinated Multi-Layer Multi-Domain Optical Network)
DOE-funded project at the University of Massachusetts Dartmouth that is working to expand OSCARS features. Read more.
JGNX Shib Extensions
The JGN-X research team focuses on QoS provisioning in DCN/OSCARS v.6. They propose an explicit QoS framework in which the OSCARS administrator defines QoS policies for the user to select through a web page or API as follows.
Multiple classes of services (CoS): Guarantee (expedited-forwarding) and non-guarantee (best effort) classes are offered.
Multiple path selection policies: The user is able to select the path with the least hop count or the highest availability. The availability of links in the network is calculated as the long-term static value by using data from network failure logs or a network management system (NMS).
In addition, the team also proposes a QoS-based bandwidth allocation policy in which a certain amount of bandwidth is reserved for certain groups of users. They are in process of testing their modified OSCARS in two DCN networks in JGN-X. These two DCN domains are separated from a production DCN network. They will investigate the inconsistent QoS policy problem in the inter-domain DCN. At this stage, they use the OptionalConstraint attributes as the inter-domain QoS attributes for inter-domain QoS provisioning. (Link to this collaboration will come soon.)