Versions Compared

Old Version 8

changes.mady.by.user Herbert Damker

Saved on

compared with

New Version 9

changes.mady.by.user Axel Nennker

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: ICM section

DRAFT AGENDA

Attendees & Representation

...

RepresentativeOrganizationRole

Herbert Damker 

Deutsche Telekom AG

TSC Chair, Active Maintainer

Shilpa Padgaonkar

Deutsche Telekom AG

Active Maintainer

Jan Friman 

Ericsson

Active Maintainer

Toshi Wakayama

KDDI

Active Maintainer

Ludovic Robert 

Orange

TSC Deputy Chair, Active Maintainer

Adnan Saleem 

Radisys

EUC Representative

Doug Makishima 

Summit Tech

EUC Representative

diego.gonzalezmartinez

Telefonica

Active Maintainer

Jose Luis Urien Pinedo

Telefónica

Active Maintainer

Mahesh Chapalamadugu

Verizon

EUC Representative

Eric Murray 

Vodafone

TSC Deputy Chair

Kevin Smith 

Vodafone

Active Maintainer
Chris Howell

Vonage

Active Maintainer
George Glass

TM Forum

TM Forum Representative

Olta Vangjeli 

TM Forum

TM Forum Representative

Henry Calvert 

GSMA

GSMA Representative

Mark Cornall 

GSMA

GSMA Representative

...

  • 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 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 )

  • Working on getting https://github.com/camaraproject/IdentityAndConsentManagement/pull/121 merged.
    • Still some discussion on how to specify purpose
  • Hoping to convince participants that the current version is a working compromise on what we can  agree on
  • Some new issues for after the merge e.g.: ICM examples
  • Some old issues for after the merge e.g.: DPoP
  • First discussions/issues on operator token and how to support them in ICM and Camara APIs


Release Management (Tanja de Groot Samuel Adeyemo )

...

  • 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: according to messages on the mailing lists there is a contribution in preparation, based on off-line work between MTN and Airtel.
    • ...

...