List of bandwidth contracts keyed by DPI application name and traffic direction.
Each entry maps a specific application (e.g. facebook, youtube, zoom) to a
bandwidth contract for either upstream or downstream traffic. The application
name must be a valid DPI application type and the direction must be specified.
Bandwidth limits are configured via the bwc-units and bit-rate leaves.

List of bandwidth contracts keyed by DPI application category and traffic direction.
Each entry maps a broad application category (e.g. STREAMING, GAMING,
SOCIAL-NETWORKING) to a bandwidth contract for either upstream or downstream
traffic. This allows bandwidth policies to be applied at the category level
rather than per individual application. Bandwidth limits are configured via
the bwc-units and bit-rate leaves.

List of bandwidth contracts keyed by WebCC category and traffic direction.
WebCC classifies web destinations into categories (e.g. BUSINESS-ECONOMY,
GAMES, EDUCATIONAL-INSTITUTIONS, SOCIAL-NETWORKING). Each entry maps one
WebCC category to a bandwidth contract for either upstream or downstream
traffic, enabling bandwidth policies based on the type of web content being
accessed. There can be at most one contract per category per direction.

List of bandwidth contracts keyed by WebCC reputation score range and traffic
direction. WebCC assigns a reputation score to each URL upon classification and
groups scores into the following risk levels: TRUSTWORTHY (81-100),
LOW_RISK (61-80), MODERATE_RISK (41-60), SUSPICIOUS (21-40), and
HIGH_RISK (1-20). Each entry maps one risk level to a bandwidth contract for
either upstream or downstream traffic, allowing differentiated bandwidth
treatment based on the trustworthiness of web destinations. There can be at
most one contract per risk level per direction.