Common use of DCN services Clause in Contracts

DCN services. The DCN should allow the following services: • To expose a full resource view, including virtual network topology. • To directly expose the low-level information model. • To expose abstracted views of its resources. This should be done with a specialization of the same information model that exposes full detail. Furthermore, the DCN should allow the following functions for client’s applications: • To allow an application to set and query any attribute or state within the scope of its control. • To allow an application to control traffic forwarding: to select traffic according to a set of criteria, to modify or adapt the traffic if necessary, to forward it to a given set of egress points. Selection criteria may be as simple as an ingress port or as complex as a vector that includes match fields up to and including layer 7, potentially spanning multiple packets of a flow. The type of applicable criteria depends on the node technology, i.e. an OVS instance running in a server, a ToR, an optical switch. • To allow an application to propose a traffic forwarding construct that requires the use of new or existing resources according to specified figures of merit, and to receive one or more offers from the controller. The client may propose and accept in a single request, or may review the offers and accept zero or one of them. • To allow an application to invoke and control standardized functions such as STP, MAC learning, ICMP, BFD/802.1ag, 802.1X, etc. • To allow an application to subscribe to notifications of faults, attribute value changes, state changes and threshold crossing alerts (TCAs). • To allow an application to configure performance monitoring (PM) collection points, with thresholds, and to retrieve current and recent results. • To allow an application to invoke and control traffic-processing functions through exchanges of opaque data blocks.

DCN services. The DCN should allow the following services: •  To expose a full resource view, including virtual network topology. • topology  To directly expose the low-level information model. • model  To expose abstracted views of its resources. This should be done with a specialization of the same information model that exposes full detail. Furthermore, the DCN should allow the following functions for client’s applications: •  To allow an application to set and query any attribute or state within the scope of its control. • control  To allow an application to control traffic forwarding: to select traffic according to a set of criteria, to modify or adapt the traffic if necessary, to forward it to a given set of egress points. Selection criteria may be as simple as an ingress port or as complex as a vector that includes match fields up to and including layer 7, potentially spanning multiple packets of a flow. The type of applicable criteria depends on the node technology, i.e. an OVS instance running in a server, a ToR, an optical switch. • switch  To allow an application to propose a traffic traffic-forwarding construct that requires the use of new or existing resources according to specified figures of merit, and to receive one or more offers from the controller. The client may propose and accept in a single request, or may review the offers and accept zero or one of them. • them  To allow an application to invoke and control standardized functions such as STP, MAC learning, ICMP, BFD/802.1ag, 802.1X, etc. •  To allow an application to subscribe to notifications of faults, attribute value changes, state changes and threshold crossing alerts (TCAs). • )  To allow an application to configure performance monitoring (PM) collection points, with thresholds, and to retrieve current and recent results. • results  To allow an application to invoke and control traffic-processing functions through exchanges of opaque data blocks.