-
Notifications
You must be signed in to change notification settings - Fork 46
API proposal from MTN (IMEI Fraud Check) #64
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
Conversation
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.
Some format improvements and the supportness of Chunghwa Telecom
Co-authored-by: Ricardo Serrano Gutierrez <145554214+TEF-RicardoSerr@users.noreply.github.com>
|
Co-authored-by: Ricardo Serrano Gutierrez <145554214+TEF-RicardoSerr@users.noreply.github.com>
|
@krishvenkatachalam target of this API is to move on as soon as clarified pending issue (see last meeting minutes:
Could you please validate this (with GSMA apparently) and also include EasyCLA validation in this PR? |
|
Hi @krishvenkatachalam, any updates on this proposal? No response since September 6, 2024 on the API backlog WG discussion. The last action points was: Pending from MTN for moving on with this API. Maybe to be included in the Device Identifier family. Any relevant information on that? |
| @@ -5,10 +5,11 @@ IMEI Fraud API submission | |||
| | API name | IMEI Fraud| | |||
| | API owner | MTN - Waseem Amra | | |||
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.
Olajames Akintunde
|
Proposal marked as Frozen due to inactivity e.g. 3 missed WG meetings, no updates in 6+ weeks, or no onboarding after TSC approval; related PRs closed and removed from active agenda.
|

API proposal from MTN (IMEI Fraud Check)
#63
Added API proposal document and swagger