Spring26 participation: IoTSIMFraudPrevention

[chenfr2-ChinaTelecom]

We apply for an exception to include the initial public release of IoTSIMFraudPrevention (v0.1.0) in the Spring26 meta-release.

Motivation:

Addresses urgent market need: Provides standardized SIM binding and geo-fencing capabilities for enterprise IoT security.

Feature-complete and stable: Core API functions (bind, unbind, query, subscriptions) are already implemented and stable in our sandbox (v0.1.0-alpha.1).

Commitment to timeline: We are prepared to dedicate resources to meet the tight Spring26 M3/M4 deadlines.

Acknowledgement & Parallel Actions:
We fully understand the Release Management team's recommendation for an independent release first. In parallel to this request, we are acting on that advice by:

Proceeding with preparations for an independent release.

Actively aligning the API with the latest Commonalities/ICM, including migrating our subscriptions to the CloudEvents format.

Supporting Info: The Scope Issue and Release Tracker are prepared. We are working through the API Readiness Checklist.

We request consideration for this exception and are available for any discussion.

[tanjadegroot]

Hi,
thanks for requesting participation in the Spring26 meta-release.

I am happy to share that the TSC yesterday agreed on the Release Management proposal and that all requestors have been allowed to participate.

The API will go through the normal review process, and the final decision will be the M3 milestone (Jan 31, 2026). You can tag release-management_reviewers on the release PR as soon as the team has their API definition(s) ready.

Please make sure to create your API release tracker page(s) ASAP, as sofar this API is not visible in the Spring26 meta-release page.
Make sure the page label is set to spring26.

Happy Spring26 !