2024-03-07 TSC Minutes

Owned by Evan Harrison
Last updated: Apr 04, 2024 by Herbert DamkerVersion comment
5 min read

Attendees & Representation

TSC Members may indicate their attendance by marking an X in the column to the right.

Community members may use @name tag to mark their attendance below the table. 

Representative

Organization

Role

 

Representative

Organization

Role

 

@Herbert Damker 

Deutsche Telekom AG

TSC Chair, Active Maintainer

x

@Shilpa Padgaonkar

Deutsche Telekom AG

Active Maintainer

x

@Jan Friman 

Ericsson

Active Maintainer

x

@Toshi Wakayama

KDDI

Active Maintainer

x

@Ludovic Robert 

Orange

TSC Deputy Chair, Active Maintainer

x

@Adnan Saleem 

Radisys

EUC Representative

 

@Doug Makishima 

Summit Tech

EUC Representative

x

@diego.gonzalezmartinez

Telefonica

Active Maintainer

x

@Jose Luis Urien Pinedo

Telefónica

Active Maintainer

x

@Mahesh Chapalamadugu

Verizon

EUC Representative

 

@Eric Murray 

Vodafone

TSC Deputy Chair

x

@Kevin Smith 

Vodafone

Active Maintainer

x

Chris Howell

Vonage

Active Maintainer

 

George Glass

TM Forum

TM Forum Representative

 

@Olta Vangjeli 

TM Forum

TM Forum Representative

x

@Henry Calvert 

GSMA

GSMA Representative 

x

@Mark Cornall 

GSMA

GSMA Representative

x

@Ramit Chawla 

Airtel

Active Maintainer

 

LF Staff:

Community: @Tanja de Groot @Rafal Artych Lazlo Suto @Markus Kümmerle Ravi Shekar @Nick Venezia @Pierre Close Toyeeb Rehman @Aleksandar Brankovic @Ricardo Serrano Gutierrez @Ramesh Shanmugasundaram Ramit Chawla (airtel)

Agenda

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.

  • Review and approval of previous meeting minutes

  • Action Items Review

  • General Topics

    • CAMARA Project Updates

    • API Backlog

    • Commonalities

    • Identity & Consent Management

    • Release Management

  • Specific Topics

    • GSMA certification of CAMARA APIs

  • Any Other Topics

Minutes

Review and approval of previous meeting minutes

Action Item Review

CAMARA Project Updates (@Herbert Damker & all)

  • Short recap from MWC (@Markus Kümmerle)

    • Slide deck presented by Markus (to be added here)

      • OpenGateway was one of the buzz word

      • Monday Meet & Greet - good to meet even if the room was too far & small.

      • The Tuesday event was great (Thanks to sponsors Red Hat & Telefonica). 100+ people showed up with analyst, application developer, etc...

      • Wednesday DefCon with TMF was also very successful. Markus should be know as the 'Godfather of Camara'. Thanks for the GSMA for the work in Glomo award.

      • Henry added that the majority of DevCon attendee were developers. (around 120 developer for around 240 attendees).

        • 48 developers participated to the hackathon.

        • Henry will send attendance information for DevCon & Hackathon (UPDATE: see Henry's message about MWC Open Gateway TopLine Stats)

  • Status of EasyCLA introduction (@Casey Cain )

API Backlog (@Ricardo Serrano Gutierrez )

Commonalities (@Rafal Artych )

  • Issue #133 Adopt RFC 9457 error response format

    • Slides presented by @Lyle Bertz within Commonalities working group: 20240304-CAMARA-Issue 133 - RFC 9457 URN Option.pdf

    • The issue will be closed with opening 2 more detailed issues for discussion in Commonalities:

      • Adding a parameter to the current response format that would provide link to detailed error documentation

      • Adopting RFC 9457 for error response format →Adopting RFC 9457 for Error Handling · Issue #157 · camaraproject/Commonalities (github.com). This is a 'burning' issue in term of impact on a CAMARA wide release.

        • @Herbert Damker indicated that companies have to interact on these if they want a change to RFC 9457 by expressing their support within Issue #157 thread prior to the next Commonalities meeting [updated based on a suggestion received to clarify the needed action], else the current motion is to keep the current format and improve it gradually

  • Issue #149 Consolidated issue for subscription discussion

    • the list of issues, based on previous discussions in Commonalities and subprojects

    • separated issues will be created to discuss each topic

    • will have impact on all APIs which have or plan to have explicit subscriptions

  • Issue #127 Which error send back when Device Identifier not supported by API Server? includes questions on Device identification:

    • when another identifier is present in Access Token

    • when multiple contradictory identifiers are provided

    • what identifier should be mandatory or optional - Aggregator use case → Should be discussed but we need to have another issue to discuss this.

      • Rename the issue to avoid confusion (@Ludovic Robert ) and continue to explore use cases.

        • @Jose Luis Urien Pinedo reminded that the device model cames from QoD and was not challenged by other projects.

      • Create a new issue about device identifier management/interoperability (@diego.gonzalezmartinez ). @Mark Cornall agrees on the criticality of this point regarding interoperability. 

Identity & Consent Management ( @Axel Nennker )

  • @Herbert Damker provided update on behalf of Axel

  • The working group agreed to concentrate the work on https://github.com/camaraproject/IdentityAndConsentManagement/pull/121

  • Hot topics: Offline Access and Refresh Tokens (under review - planned to get in the profile), Purpose (have a dedicated parameter vs keep it is the scope as of today), Pairwise Pseudonymous Identifiers

    • Other points will be delayed to future release

  • To keep the discussion on PRs more focused the working group agreed to create new issues for controversial discussion points

Release Management (tbc: @Samuel Adeyemo )

  • Initial infos by @Herbert Damker (as Samuel isn't able to join)

    • Release Process 

      • Release process will contain about 17-22 weeks

      • Target to have first meta release in September => we have soon to kick-off

        • Use Open Source Summit event in Vienna (16-18 September 2024) as target to announce the release

        • Good timing to have API implementation available for MWC25

      • First milestones will include definition of Commonalities & ICM releases

      • More details with a review of the release process and milestones within next TSC

    • @Lyle Bertz informed the CAMARA board that TMUS is working on a replacement for @Marouane Balmakhtar as community release manager

    • Looking for (additional) volunteer for the release management project and as Community Release manager

GSMA certification of CAMARA APIs (@Mark Cornall @Toyeeb Rehman )

  •  Certification of 'live' implementations (26 in sum tested)

  • @Toyeeb Rehman presented the major issues faced during certification, including action points requested from TSC and its working groups

  • Need larger diffusion because great work

  • We need to have follow-up & tracking on this

Any Other Topic

  • None due to lack of time

Next Meeting

  • Next TSC Meeting will be on March 21st, 16:00 CET / 15:00 UTC / 07:00 PT

    • @Herbert Damker  will not be available, @Ludovic Robert will moderate

  • Specific agenda topics:

    • Update from TMForum collaboration and how members are working in Catalysts and Operate APIs (as proposed by @Olta Vangjeli within comments)

Action items