Skip to content

Conversation

@krishvenkatachalam
Copy link

API proposal from MTN (IMEI Fraud Check)
#63

Added API proposal document and swagger

Copy link
Contributor

@TEF-RicardoSerr TEF-RicardoSerr left a 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>
@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Sep 6, 2024

CLA Not Signed

Co-authored-by: Ricardo Serrano Gutierrez <145554214+TEF-RicardoSerr@users.noreply.github.com>
@jgarciahospital
Copy link
Collaborator

@krishvenkatachalam target of this API is to move on as soon as clarified pending issue (see last meeting minutes:

This API was presented already and included in an existing group but no work was done so discontinued. Now Rebecca is presenting the proposal seeking for support

DeviceCheck GSMA proposal overlaps this

IMEI Fraud will offer more information to developers than GSMA Device Check service.

MTN and other supporters should meet with GSMA to discuss if proceeding with this API within CAMARA still makes sense.

Request for meeting already sent by GSMA to MTN

Outcome of meeting awaited before deciding if this API proposal should proceed in CAMARA

MEETING UPDATE:

Pending to be confirmed by MTN, AP to be raised.

Could you please validate this (with GSMA apparently) and also include EasyCLA validation in this PR?
image

@albertoramosmonagas
Copy link
Contributor

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 |
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Olajames Akintunde

@jgarciahospital
Copy link
Collaborator

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.

  • To reactivate: comment mentioning the proposal owner and notify the WG at least 1 week before the next meeting agenda is finalized; otherwise, it may be archived after 6 months.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

New API Proposal from Chenosis : IMEI Fraud Check API

5 participants