Page Comparison

DRAFT MINUTES

Attendees

 Agenda Proposal

• Antitrust Policy

• Approval of minutes of last conf. call

• Recent Updates & Recap

• Review of Action Points

• Discussion

  • New APIs Proposals:  #35 (5G New Calling),  #50 (Device Management), #63 (IMEI Fraud), #17 (Consent and Measurement),  #23 (Carrier Wholesale Pricing),  #24 (Steering of Roaming Information), #95 (IoT SIM Status Mgmt API), #96 (IoT SIM Fraud Prevention API), #97 (IoT SMS send API), #115 (SIM Historical Information), #121 (User Account Spend Count), #122 (Number Of Cards Under User's ID), #126 (Facial Recognition), #127 (Network Health Assessment), #128 (Network Traffic Analysis)

  • Out of Agenda: #136 (eSIM Remote Management), #141 (Energy Footprint Notification), #143 (IoT Data Transfer Activation)

  • API Enhancements Proposals: #109 (Support application resource requirements in application profiles)

  • Governance: N/A

• Closing Issues

  • #22 (Capability and Runtime Restrictions), #18 (Receive SMS),   #41 (Telco Scoring), #20 (Best Interconnection), #68 (Consent URL), #83 #85 #86 #87 (Model as a Service), #91 (Fixed lines in Device Location APIs), #93 (Line Eligibility for Carrier Billing API), #89 (IP High-throughput Elastic Network)

• AoB

• Q&A

...

1. To close the agenda SEVEN DAYS BEFORE the conf. call.

   • In case a WG participant wants to include a point in the agenda (e.g., present a new API proposal), this participant shall ensure the corresponding issue is opened in Github by then.

   • Exceptional situations will be treated separately.

2. New schedule of conf. calls **The meetings are to be held by Linux Foundation (Links available at GitHub and Confluence Backlog front pages)

   • 2nd Thursday of the month (9-10:30 UTC)

   • 4th Thursday of the month (15-16:30 UTC)

3.  Send agenda to TSC mail list, to encourage more TSC member companies to join the call and provide comments when they identify APIs which are of interest for them. 

4. New API proposals are included in backlog table when template PR is created, linking to the pending PR

5. PR will be merged as soon as ready for TSC, and should be merged before TSC review

6. API enhancements requires existing group’s validation. TSC is informed accordingly to validate

7. Link and status in backlog table will be updated accordingly

8. Issue to track API onboarding will be opened once new API is confirmed in TSC.

Approval of minutes of last conf. call

...