2025-06-19 Number Insights

2025-06-19 Number Insights

Community Attendees:

@Ludovic Robert @Cormac Hegarty @Alberto Ramos Monaga @Fernando Prado Cabrillo @Jorge Garcia Hospital

Community Attendees:

LF Staff:

Agenda

The project's Antitrust Policy is linked from the LF and project websites. The policy is important when multiple companies, including potential industry competitors, are participating in meetings. Please review it, and if you have any questions, please contact your company’s legal counsel. Members of the LF may contact Andrew Updegrove at the firm Gesmer Updegrove LLP, which provides legal counsel to the LF.

 

  • Release agenda update

  • OTP

  • SIM Swap

  • Device Swap

  • Number Verification

Minutes

Release agenda update

As of now the M3 is planned for Jun 21, 2025 but TSC this afternoon can delay it.

Aa a reminder a Release Candidate PR must prepared & merged for M3

OTP Validation

  • No update

  • Preparation for Autumn 25 release

    • For commonalities checklist is here: Analysis of Commonalities 0.6.0-alpha.1 changes

      • No subscription

      • Remove AUTHENTICATION_REQUIRED error code - this code was not present

      • Remove 422 IDENTIFIER_MISMATCH error code - this code was not present

      • Update x-correlator format

      • Documented Error Responses info.description section

    • TBD: prepare release candidate

      • Do we have to shift the version from v1.1 to v1.2?

        • OK for the team

SIM Swap

  • Preparation for Autumn 25 release

    • Remove AUTHENTICATION_REQUIRED error code - this code was not present

    • Remove 422 IDENTIFIER_MISMATCH error code - this code was not present

    • Update x-correlator format

    • Documented Error Responses info.description section

    • TBD: prepare release candidate

Device Swap

  • Device swap API is promoted to Incubated status

    • At least one Initial API version released and implemented by one operator.

      Participated in at least one meta-release cycle.

      Aligned with Commonalities and ICM guidelines.

      At least 3 maintainers from 3 different companies in MAINTAINERS.md.

      Issue opened in API Backlog WG for incubation request.

      Approval from TSC.

  • Preparation for Autumn 25 release

    • Remove AUTHENTICATION_REQUIRED error code - this code was not present

    • Remove 422 IDENTIFIER_MISMATCH error code - this code was not present

    • Update x-correlator format

    • Documented Error Responses info.description section

    • TBD: prepare release candidate

  • Request in API backlog: TIM Brazil proposes adding a notification subscription version of the Device Swap API to the GSMA Open Gateway portfolio. The development, aligned with the existing SIM Swap notification model, addresses strong demand from the insurance sector in Brazil (issue #230) and included in scope meta-release fall25. OK from the backlog team.

    • No issue as of now as we will be short for the release

    • Do TIM Brazil will propose a contribution?

      • @Ludovic Robert will re-open the backlog issue to ask if TIM Brazil will contribute.

Number Verification

  • Update x-correlator format

  • Documented Error Responses info.description section

  • TBD: prepare release candidate

  • Links with ICM work - to be checked with @Axel Nennker

  • Add an issue to improve the documentation as of now CIBA is explicitly listed as the only method for the temp token while ICM propose the JWT bearer flow. We need to have a documentation more generic and referring ICM documentation.

Voice Verification

  • @Herbert Damker initialized the git hub and triggered 2 issues that Herbert will solve once @niu-chinauicom accepted the invitation to CAMARA :

Action items

 

@Ludovic Robert will do the PR for the OTP Release candidate
@Fernando Prado Cabrillo will do the PR for the Sim Swap Release candidate
@Ludovic Robert will do the PR for the Device Swap Release candidate
@Fernando Prado Cabrillo will do the PR for the number verification Release candidate
Reach Tim Brazil for Device Swap subscription contribution (@Ludovic Robert )
Identify & reach codeowner for Voice Verification (@Herbert Damker )
Issue in NV documentation (@Ludovic Robert
Issue + PR to improve/align NV test plan (@Fernando Prado Cabrillo