New proposal for Network Outage API

[mohdafzalbt]

What type of PR is this?

enhancement/feature

What this PR does / why we need it:

New proposal for network outage API

Which issue(s) this PR fixes:

Fixes #327

Special notes for reviewers:

Changelog input

 release-note

Additional documentation

This section can be blank.

docs

[linux-foundation-easycla]

• ❌ - login: @mohdafzalbt / name: Mohammed Afzal. The commit (9a32ec1, e7ea0bd) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

[albertoramosmonagas]

Hi @mohdafzalbt,

Thanks for the YAML. Before this can move forward, three things are needed:

1. Process — blocking:
API proposal template still missing (PR must include it, not just the YAML): https://github.com/camaraproject/APIBacklog/blob/main/documentation/API-proposal-template.md
EasyCLA check is failing on the PR — please sign: https://github.com/camaraproject/.github/blob/main/CONTRIBUTING.md#easycla (or check the EasyCLA bot comment on the PR for the signing link)
Presentation slides for the Backlog WG session are also required: https://github.com/camaraproject/Marketing/blob/main/documentation/MarketingMaterial/CAMARA%20Master%20Template.potx

2. Design — needs rework before review
Two endpoints (/tac/{trackingAreaCode} and the plmn filter) expose internal 3GPP network parameters (Tracking Area Code, PLMN) directly to the API consumer. These are not northbound-portable identifiers — a developer has no way to obtain a TAC, and exposing it leaks internal network topology, which goes against CAMARA's abstraction principle. Please redesign around a developer-facing identifier: device object or phoneNumber (per CAMARA_common.yaml) for the device-centric use case, and a standard geographic area object for the location-centric use case.

3. Other Commonalities gaps
No security scheme defined (securitySchemes/security) — needed before ICM/personal-data review can even start
Subscription model (/subscribe, /subscriptions/{id}) doesn't follow the CAMARA event subscription pattern (CloudEvents / CAMARA_event_common.yaml) — should be aligned to it

Once the template, CLA, and slides are in place, and the TAC/PLMN exposure is resolved, happy to do a full layer-by-layer review of the spec.

[mohdafzalbt]

/easycla