Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Attendees & Representation

...

RepresentativeOrganizationRole

Deutsche Telekom AG

TSC Chair, Active Maintainerx

Deutsche Telekom AG

Active Maintainerx

Ericsson

Active Maintainerx

KDDI

Active Maintainerx

Orange

TSC Deputy Chair, Active Maintainerx

Radisys

EUC Representativex

Summit Tech

EUC Representativex

Telefonica

Active Maintainerx

Telefónica

Active Maintainerx

Verizon

EUC Representative

Vodafone

TSC Deputy Chairx

Vodafone

Active Maintainer

Vonage

Active Maintainerx
George Glass

TM Forum

TM Forum Representative

TM Forum

TM Forum Representative

GSMA

GSMA Representativex

GSMA

GSMA Representativex

...

  • Approval request for new repositories (see https://lists.camaraproject.org/g/tsc/message/160)
    • "Most Frequent Location" (see https://lists.camaraproject.org/g/tsc/message/164)
      • Proposed Initial maintainer/codeowner: 
        • Fernando Prado (Telefonica)
        • Fabrizio Moggio (TIM)
      • Will be potentially managed within "Location Insights" family together with "Device Visit Location"
      • Decision: Approved
    • "Best Interconnection" and "Device Visit Location" waiting for Maintainer/Codeowner lists
    • Also ready for creation: "Home Devices - Network Access Management":

      Name

      Company

      Role

      GitHub User

      Christopher Aubut

      Charter Communications

      CODEOWNER

      @caubut-charter

      Randy Levensalor

      CableLabs

      CODEOWNER

      @RandyLevensalor

      Mayur Channegowda

      Vodafone

      CODEOWNER

      @mayur007

      Justin Pace

      Charter Communications

      MAINTAINER

      @justin-pace-charter

      • Decision: Approved

...

  • Draft scope for v0.4 release (relevant for Fall-24 meta-release) for discussion:
  • Proposal to tackle open subscription issues Common proposal to tackle subscription-based open issues. · Issue #185 · camaraproject/Commonalities (github.com) - mains points:
    • Align our subscription model with CloudsEvents subscriptions one
    • Introduce a status attribute in the template as we have fair UCs that can leverage this (Retrieve expired subscriptions for monitoring, deactivate a subscription if an user revoked her/his consent, etc...). API subproject could decide to use it or not.
    • Improve the model to allow consumers to subscribe to more than one event types with a single subscription but at least for the first meta-release we enforce to have only event type per subscription. After this first meta release decision to handle several event types in one subscription request should be discussed at API sub projet level
    • Add filters and it's up to API Project to use it. We recommend to be very cautious as it add complexity so it should be keep for very relevant UC.
    • Add initialEvent in config as well to manage request to get event when current situation of a device corresponds to the subscriptions type. .

Identity & Consent Management (Axel Nennker )

...

  • From past TSC Minutes:
    • We have currently two project without (visible) work within the repositories
      • Device Swap (repository created but no activity over the last 6 months)
      • IMEI Fraud (Attached to device identifier repository but no activity there on this API)
    • Are these APIs still relevant?
      • If, yes, how to find volunteers who will work on them?
      • If no volunteers: Postpone these APIs to a later time?
  • Device Swap seems to be solved: according to messages on the mailing lists there is a contribution in preparation, based on off-line work between MTN and Airtel. Ludovic Robert  will contact Wassem Amra. 
  • IMEI Fraud: Eric was in contact with MTN (proposal owner of IMEI Fraud). API will not be part of target release for Fall-24. If interest to develop will come up, setting up a separate Sub Project recommended. 
    • Action: Eric Murray to inform API Backlog and Helene from GSMA Product Team.

...