[Enterprise Connectivity Governance API] ConnectivityGovernance

[bishnu-infy]

Description
A network-level policy enforcement API that enables telcos to help enterprise customers control application access, optimize bandwidth usage, boost employee productivity and enforce compliance policies across MPLS, SD-WAN, mobile networks—without requiring device-level software installation.
Unlike traditional device management tools (MDM, content filters) that can be bypassed also brings lots of overhead, this API enforces policies at the network gateway level (PE routers, SD-WAN edges, telco core), making restrictions unpassable and cross-device compatible. Also this could be a sellable proposition can be bundled with enterprise products.

Use cases

1. Restricting access to certain services (Netflix, YouTube) at certain time of the day for an organization/enterprise at the network level rather than at device level. Applicable to Fields related to Secure environments (Banking, Defence, Healthcare), Educational Institutions etc.
2. BYOD - Users can use their personal devices such as laptops to work on such environments instead of creating policies on their local machines ensuring compliance.
   @abd-abhisek @hemantagogoi-infy @vijaymurthyn

[albertoramosmonagas]

Hi @bishnu-infy, thanks for opening this proposal.

I’ve added ConnectivityGovernance (#298) to the agenda of the next API Backlog session (next week).

Before we review the proposal in detail (and pending the PR/spec that supports it), based on the issue description I have a few scope & interoperability questions that would be very helpful to have answered ahead of the meeting:

1. CAMARA scope: As described (policy enforcement at PE routers / SD-WAN edges / telco core), this currently reads closer to an Operate interface than a CAMARA Service Management API.

• Can you clarify the intended API type and consumers (enterprise admin, integrator, app developer)?
• Why wouldn’t this be better positioned as a TM Forum–style operate API, rather than CAMARA?

2. Normative telco capability (operator-agnostic): What is the portable, operator-agnostic capability exposed? Examples like “block Netflix/YouTube” are not interoperable by default.

• What is the normative target resource (e.g., enterprise/site/connection/mobile subscription)?
• How would you define a portable policy model (e.g., categories with a controlled vocabulary) vs app/service names?

If you can share answers before the session, it will make the discussion significantly more productive

Thanks!