Agenda

Antitrust Policy

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

• Action Items Review

  • Review of previous meeting minutes (Jun 27th)

    • If no comment remove Draft 

  • Open item will be review below for each API

  • Other topics 

Minutes

OTP Validation

New

• User story (PR#71): need review

  • @Jorge Garcia Hospital will take a look.

• New PR#70 to track Readiness Checklist (not to be merged for now)

Ongoing

Need approval for:

• Test definition (PR#61)

  • Review from @Fernando Prado Cabrillo 

    • fixed

  • Review from @Toyeeb Rehman

    • fixed

SIM Swap

New

• We have several 'administrative' issues to prepare the release:

  • (#123)Provide readiness checklist

  •  (#122)Scope of SimSwap for Fall24 CAMARA Release

    •  

      • As of now only sim_swap is candidate for a stable release

    • We are not pushing for sim-swap-notification-subscription for this release.

      • Any request from the team to add this API for this meta-release?

        • @Jorge Garcia Hospital will check for Telefonica

        • No push from @Huub Appelboom 

  • (#121) Provide user story

    • Check if any volunteer to contribute - to be checked with @Fernando Prado Cabrillo 

      • @Jorge Garcia Hospital  sync with Fernando to provide them.

•  (#118) Request body is required but all properties are optional

  •  

    • We have 2 options:

      1. Leave it as required and force the client to send an empty body -> {}

      2. Remove the requirement and let the client send a POST without body

    • As of now option 1. Check if any objection. 

    • Topic for commonalities

• Extracting phoneNumber from the 3-legg access token (#117) 

  • From initial @Gregory Lindner request we are covered: phone number is optional + we have 403 INVALID_TOKEN_CONTEX

  • Gregory adds an additional request on documentation. 

    • Remove the phoneNumber - probably to be considered in future

    • 403 or 422.

      • 422 "DEVICE_IDENTIFIERS_MISMATCH" is not relevant in our context as it used if consumer provide several identifiers not identifying same device - not possible in our API. 

      • Only 403 has valid scenario (till we have the phoneNumber in the request)

Ongoing

Need approval for:

• Update sim-swap-notification-subscription.yaml (PR111)

  • First review from @Maximilian Laue 

    • fixed

  • Need other approval

    • @Jorge Garcia Hospital will check in Telefonica to get approval.

  • Fix issue #113 Swap Notification example list phoneNumber value without quotes

• Test Case proposal (PR#70)

  • Proposed by @Fernando Prado Cabrillo - reviews from @Toyeeb Rehman and @Ludovic Robert 

    • Fernando has to consider Toyeeb comments.

    • Other feedback welcome.

• Revisit Defined Error (#119)

  • We must add a 403 definition (403 - INVALID_TOKEN_CONTEXT) as specified in commonalities

    • Urgent issue because yaml must be ready for M3

    • To be check with @Fernando Prado Cabrillo 

Number Verification

New

• Add user story (PR#118)

  • Ready to be merged?

  • @Jorge Garcia Hospital will takea look.

  • @Cormac Hegarty  will take a look.

• We have several 'administrative' issues to prepare the release:

  • (#120)Provide readiness checklist

  •  (#119)Scope of Number Verification for Fall24 CAMARA Release

  • (#117/118) Provide user story

• (#116) The UML flows do not show an aggregator / channel partner (@Cormac Hegarty )

  • We can add a note in the yaml documentation part with a link to the aggregator E2E as defined in ICM. 

  • Suggest that we first try to close PR94 Added sequence diagrams with RFC 9101

    • @Fernando Prado Cabrillo has provided comments to @Ming Hui Foo proposal - need to be solved

    • Then we can add an additional scenario

    • This is definitely good information but not a on critical path for the release 

    • As this is probably not closed in ICM proposal to put in hold for now and reopen the discussion after the meta release

Ongoing

• Test definition (issue104)

  • Check with @Axel Nennker is willing to do it