DRAFT
Attendees & Representation
Type @ and your name to indicate your attendance
LF Staff:
Community:
| Verizon Wireless, 5GFF (Chair) | x | |
| Verizon Wireless | x | |
| Vodafone (Minutes) | x | |
Santhi Dharmapalan | Verizon Wireless | x |
Medha Joshi | Verizon Wireless | x |
Rafal Artych | Telefonica | x |
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. |
- Action Items Review
- General Topics
- Any Other Topics
Minutes
PRs
Closed Issues
- #31, #30
Open Issues
- #34, "How is the subscription in connectivity insight explicit?"
- comments in Github issue from Mahesh and Kev, both explaining the view that a synchronous request for a connectivity insight is not necessarily requiring a subscription- Pending response from Shilpa Padgaonkar
- #28, Connectivity Insight YAML does not follow Identity & Consent guidelines
- We can add this to the next PR
Discussion
- #24,
- discussion on whether the terms 'network-monitoring' and 'policy' are appropriate
- thresholds may be more appropriate , but policy may encompass more than these. At a basic level we are talking about the thresholds which (if not met) will harm the user experience
- Suggestion to use network-quality/application-profile
- Kev will make a PR proposing this
AOB
- Discussion on mandatory elements to progress the API (i.e. release management guidelines, and comment from Herbert https://github.com/camaraproject/NumberVerification/issues/33#issuecomment-1703174158 .Meanwhile we will proceed with a 0.x release
API Readiness minimum criteria checklist
PLEASE NOTE: This document is DEPRECATED as the updated API Readiness Checklist is now maintained within the Release Management Working Group.
- Rafal pointed out issue in Commonalities regarding string for Duration, and requested the Connectivity Insights sub-group should contribute to that issue. Proposal to add a standard for defining durations for API Design guidelines · Issue #137 · camaraproject/Commonalities (github.com)
- Our Action is out of date and needs the latest linter files, Rafal will update