-
Notifications
You must be signed in to change notification settings - Fork 52
[API Proposal] Network Contract Lifecycle Management (N‑CLM) #322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
abd-abhisek
wants to merge
6
commits into
camaraproject:main
Choose a base branch
from
abd-abhisek:feature/n-clm-ppt
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
c51a194
[New API Proposal] - Multi Point VPN #205
abd-abhisek d39d184
Merge pull request #1 from abd-abhisek/abd-abhisek-patch-2
abd-abhisek b5e655c
Merge branch 'camaraproject:main' into main
abd-abhisek 41ec8d8
uploaded spec
abd-abhisek 52c84b9
supporting files added for N-CLM
abd-abhisek 9503066
Remove Network Authenticated Assembly PPTX
abd-abhisek File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,55 @@ | ||
| # API Proposal Template | ||
| This template captures all the information that a partner should fill out when proposing a new API (or API family) to CAMARA. | ||
|
|
||
| ### API family name | ||
| Network Contract Lifecycle Management | ||
|
|
||
| ### API family owner | ||
| Infosys Limited | ||
| *Contributors: @hemantagogoi-infy, @vijaymurthyn | ||
|
|
||
| ### API summary | ||
| N-CLM is a CAMARA API that enables real-time SLA governance for live network services by binding measurable SLA policies to CAMARA service instances (e.g., QoD, Dedicated Networks), continuously evaluating compliance, and triggering instant breach notifications via CloudEvents. | ||
|
|
||
| In-scope examples: | ||
|
|
||
| Low-latency SLA enforcement for fintech apps | ||
| Availability assurance for healthcare/critical systems | ||
| Multi-metric SLA control for autonomous logistics | ||
|
|
||
| ### Technical viability | ||
| Uses CAMARA service binding + operator telemetry (CQM) for real-time evaluation | ||
| Closed-loop lifecycle: bind → evaluate → notify → amend → close | ||
| CloudEvents-based event model (no polling) | ||
| Supports mid-lifecycle SLA updates (PATCH) without reprovisioning | ||
| Cross-operator portable SLA model aligned with CAMARA | ||
|
|
||
|
|
||
| ### Commercial viability | ||
| Built on existing CAMARA APIs (QoD, CQM, Dedicated Networks) → low adoption barrier | ||
| Enables SLA-backed premium network offerings | ||
| Supports API monetization via programmable guarantees & breach events | ||
| CAMARA-aligned → interoperable and open ecosystem | ||
|
|
||
|
|
||
| ### YAML code available? | ||
| NO | ||
| Sequence diagram is available in deck | ||
|
|
||
| ### Validated in lab/productive environments? | ||
| NO. | ||
| NO — Currently in design/proposal phase. Lab validation can be planned as a next step after CAMARA backlog acceptance | ||
|
|
||
| ### Validated with real customers? | ||
| NO. | ||
| NO — Use cases have been validated conceptually | ||
|
|
||
| ### Validated with operators? | ||
| YES | ||
| IN PROGRESS — Validation is currently underway | ||
|
|
||
| ### Supporters in API Backlog Working Group | ||
| List of supporters. | ||
| - Infosys Limited (@abd-abhisek, @bishnu-infy, @hemantagogoi-infy, @vijaymurthyn) | ||
| - BT (Pavan Kumar) | ||
| - Telstra (Shyam) |
Binary file not shown.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please rename the proposal file from N-CLM.md to a self-explanatory name. Using only the abbreviation makes it difficult for participants to understand the proposal from the repository view.
Suggested file name:
network-contract-lifecycle-management.mdIn addition, please avoid using N-CLM as the primary term throughout the document. The full name should be used first, with the abbreviation only introduced afterwards.
Separately, if this proposal progresses to repository/API naming, we should revisit the final API/repository name. Network Contract Lifecycle Management is quite long, and the word contract may suggest BSS/Operate scope. A shorter name such as
network-sla-managementorsla-policy-managementmay better reflect the intended scope, but this should be decided after the functional boundaries are clarified.