Skip to content

Latest commit

 

History

History
151 lines (103 loc) · 7.79 KB

TSC-2023-09-21-Meeting-Minutes.md

File metadata and controls

151 lines (103 loc) · 7.79 KB
Raw

Agenda and Minutes of CAMARA Technical Steering Committee (TSC) meeting - 2023-09-21

Invited TSC Participants

  • Herbert Damker - (Deutsche Telekom AG) Active Maintainer, TSC chair
  • Eric Murray - (Vodafone) Active Maintainer, TSC deputy chair
  • Ludovic Robert - (Orange) Active Maintainer, TSC deputy chair
  • Adnan Saleem - (Radisys) End User Council representative
  • Chris Howell - (Vonage) Active Maintainer
  • Diego González Martínez - (Telefónica) Active Maintainer
  • Doug Makishima - (Summit Tech) End User Council representative
  • George Glass - TM Forum representative
  • Mark Cornall - GSMA representative
  • Jan Friman - (Ericsson) Active Maintainer
  • Jose Luis Urien - (Telefonica) Active Maintainer
  • Kevin Smith - (Vodafone) Active Maintainer
  • Mahesh Chapalamadugu - (Verizon) End User Council representative
  • Shilpa Padgaonkar - (Deutsche Telekom AG) Active Maintainer
  • Toshi (Toshiyasu) Wakayama - (KDDI) Active Maintainer

Guest Presenter:

  • Markus Kümmerle (Deutsche Telekom (AG)

Minutes are available within: https://github.com/camaraproject/Governance/tree/main/documentation/MeetingMinutes/TSC

Agenda

  • Introduction
  • Way of working within TSC
  • F2F/hybrid Meeting Oct 19th in London?
  • New API Proposals
    • Click to Dial
    • KYC Match
    • KYC Fill-in
    • Site-to-Cloud VPN
    • WebRTC
  • Notification pattern - request for feedback from Commonalities WG
  • Release Management for CAMARA & Alignment with Open Gateway
  • Request for private repositories (not discussed)
  • Backlog of TSC Topics (not discussed)

Please find material for the agenda points below.

Introduction

  • Check attendance
  • TSC meeting October 19th
    • Room booked in GSMA premise
    • Registration required for on-site participant
    • 2 hours meeting

Updates from Governance Board / Director Fund

Announcement of CAMARA directed fund at LF Open Source Summit. Chair & Treasurer have to be elected for the Governance Board. Next steps is to decide how fund will be used.

New API

Nomination of initial maintainers for the three new sub projects

  • Click to Dial
  • Know Your Customer
  • WebRTC

We have a list of maintainers.

subproject Maintainers
Click-to-Dial
China Mobile is the owner		 Hanbai Wang (@HanbaiWang) for China Mobile
Shuting Qing (@ShutingQing) for Huawei
Dan Xu (@DanXu-ChinaTelecom) for China elecom
Know Your Customer
KDDI is the owner		 Toshi Wakayama (@ToshiWakayama-KDDI) and Tetsuya Chiba (@tcchiba) for KDDI
Gilles Renoux (@GillesInnov35) for Orange
Efthymis Isaakidis (@EfthymisIsaakidis-DTCS) for DT
Fernando Prado (@fernandopradocabrillo) for Telefonica
Dan Xu (@DanXu-ChinaTelecom) for China Telecom
WebRTC
Telefonica is the owner		 Ricardo Serrano (@TEF-RicardoSerr) for Telefonica
Pradeep Achar (@pradeepachar-mavenir) and Sushanth Hegde (@sushanthmavenir) for Mavenir
Benjamin Busvel (git to be created) for Orange
Jesus Pedruelo (@jesus-pb) and Ratna Ratnanandan (@ratnavf) for Vodafone
Deepak Jaiswal (@deepakjaiswal1) for T-Mobile US

[Action for Jan] Ericsson will provide maintainers for Click-to-Dial & WebRTC.

No objection from the TSC for the provided list.

Name for API family with KYC Match and KYC Fill-in as APIs

'Know Your Customer' is the name agreed by the project group & TSC

Situation for Site-to-Cloud proposal

Proposal unchanged but discussion between both CAMARA & TMF proposal occurred in the CAMARA git.

We need to have another round of discussion and in particular a statement of the TM Forum for this API.

Pierre Close (AT&T) explained the scope of the TMF API proposal and ask to be involved in the discussion and will reach AT&T involved (for reference #271)

Private repositories in CAMARA

Scam Signal

Update from GSMA on the request for a private repository for Scam Signal See also #83

  • Mark Cornall explained the decision: The private repo will be hosted under GSMA OPAG or Open Gateway directory with limited access & visibility. A specific 'join-in' process will be triggered to accept people in the group with some legal stuff to agreed.

  • Diego asked if CAMARA design rules will be followed in a GSMA API crafted?

    • Mark answered YES !

General decision about private respositories

Several TSC members raised the point if CAMARA should have private repositories at all. Shilpa thinks this is not a good idea to have private repo in CAMARA as API work will be mentioned in TSC meetings, for example, which are public. George raised same arguments to ease TMF contribution.

Decision taken without objection: there should be no private repositories within CAMARA for API development

Anonymised Subscriber Identifier

Discussion:

  • Eric raised the point about the other private topic which is Anonymised Subscriber Identifier. Should this repo stay in CAMARA?
  • For the API Anonymised Subscriber Identifier the issues is about the name (Anonymised has a sensitive meaning) and the legal impact of this API (people has not to think that Telco are providing identifier without their consent).
  • Decision to be taken at next TSC
  • Action: Open an issue in API backlog. [x]Done by Eric --> camaraproject/WorkingGroups#312
  • [Action for the team] review this proposition and provide feedback for next TSC.

Commonalities

Way of working Commonalities/TSC

  • Shilpa raised the point that we need to find a way to work quickly between Commonalities & TSC.
  • Shilpa proposal for a specific topic is to select people from the subproject to inform the TSC about a that topic. For next Commonalities meeting Shilpa will list the topics where we need participation and bring this list to TSC.
  • Diego asked is vote will still be at subproject level or at TSC level?
    • Update after the meeting: Current governance is not precise on it, but defines TSC as first option, see project charter:
      • "... The TSC is responsible for: [...] discussions, seeking consensus, and where necessary, voting on technical matters relating to the code base that affect multiple projects; [...]"
      • "Technical decisions that span multiple parts of the CAMARA Project should be discussed and made in the Commonalities Working Group. Decisions are usually made by lazy consensus. If no consensus can be reached, the matter may be resolved by majority vote by the TSC, Sub Project or Working Group."

Notification pattern

Almost there - No major points highlighted by Ludovic. Now it's time to review and approve if not blocking point.

Identify & Consent Management (ICM)

  • Way of working ICM/TSC/sub projects
    • especially decisions about Security Schemes

Release Management

  • See this issue for an initial scope of the discussion
    • As of now all projects are v0.x.y
  • Linux Foundation offers Release Management services and trainings – initial presentation in one of following TSC meetings or in a separate meeting?
    • Proposal to have an extra meeting - not a TSC one as it requires 30 minutes.
  • Kevin brings the topic of management of automatic testing for APIs and its role in Release Management. Kevin will prepare a presentation for the next TSC.

Action for all

  • Provide a list of subproject where each TSC member are involved to be sure we have no subproject representation missing. Please send email to Herbert.

Backlog of TSC Topics

Not discussed