Community Attendees:

@Ludovic Robert @Jorge Garcia Hospital @Toshi Wakayama @Surajj Jaggernath @Axel Nennker

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

PR prepared for M4

OTP Validation

• one-time-password-sms has no breaking change - It will be a patch release: from v1.1.0 to v1.1.1

• Release available Release r3.2 · camaraproject/OTPValidation Sep 16, 2025

  • Missing test statement

• 3 easy issues to solve in next release:

  • AuthenticationId example and length suggests UUID but no format constraint, no indication of uniqueness guarantees (https://github.com/camaraproject/OTPValidation/issues/124 )

  • https://github.com/camaraproject/OTPValidation/issues/123

  • https://github.com/camaraproject/OTPValidation/issues/122

SIM Swap

• Public Release merged - tag r3.2

  • it features:

    • sim-swap 2.1.0

    • sim-swap-subscriptions 0.3.0

  • Missing test statement

• Question from GSMA French Market:

  • We have a probable inconsistency in France (discussed in GSMA Market Champion) for the sim swap check behavior alignment.

    Suppose a customer subscribed a new line Sept 1st, 2025.
    An application is performing a sim-swap- check Sept 10th, 2025 with a maxDate set to (1200hours) 50 days

    • Some French operators consider that when no sim swap occurred, activation date is a kind of sim swap and answer TRUE

    • While other only consider real sim swap (change of sim within same operator) and answer FALSE

    (Note: same thing for the case of a portability – not a sim swap for some and a sim swap for other)

  • Response from @Jorge Garcia Hospital Telefonica is supporting current API specification, considering MSISDN activation/portability as a SIM Swap, in fact considered as the original Swap definition of "change of binding between IMSI and MSISDN".

  • @Toshi Wakayama answered for KDDI - @Axel Nennker will check.

    • KPN consider also a new activation as a sim swap

Device swap

• Release available https://github.com/camaraproject/DeviceSwap/releases/tag/3.2

  • it features:

    • device-swap v1.0.0

  • Missing test statement

• Request from TIM Brasil to add Device Swap Subscriptions API

  • No update

• @Axel Nennker requests clarification between SIM Swap & Device Swap.

Number Verification

• Release available https://github.com/camaraproject/NumberVerification/releases/tag/r3.2

  • it features:

    • number-verification 2.1.0

  • Missing test statement

• proposal to close https://github.com/camaraproject/NumberVerification/pull/94

  • Thoughts?

    • @Axel Nennker agreed that it can closed (and diagram should be in mermaid). @Jorge Garcia Hospital agreed.

API clarification

• We discussed the requirements for clarification between few APIs: Device Swap, SIM Swap, Number Recycling, Tenure

  • Probably a whitepaper could be helpful

  • @Jorge Garcia Hospital will prepare a draft.