2024-04-09 CFS Minutes
Attendees & Representation
Type @ and your name to indicate your attendance
LF Staff:
Community:
Name | Organization | Present |
---|---|---|
Fabrizio Moggio (Chair) | TIM | X |
Robert Ludovic | INNOV/NET | X |
Fan Yang | China Unicom | ย |
Rafalย Artych | T-Mobile | X |
Enlai Chu | ย | |
ย | ย | ย |
ย
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. |
Last Meeting Report Approval
UseCase-3 (Call FWD Verification)
User Story for UseCase-1 (Bank Frauds)
Open Discussions
Destination Phone Number as Output
Conditional/Unconditional
Next Steps
ย
Minutes
LFย Policies
Agendaย approval
UseCase-3 (Call FWD Verification)
ORANGE has some doubt about the validity of the Use Case considering it not for Developer but for Operators.ย
A better understanding of the Use Case is neededย
The User Story can be anyway helpful to move forward the discussion
as general note a User Story can be merged only when compatible with the YAML
User Story for UseCase-1:
it is approved to use this user story as template to produce the next User Stories
Destination Phone Number as Output: it was agreed toย close the Discussion.
Conditional/Unconditional:
ย
there is still no agreement on the value for providing this information with respect to the added complexity to the API implementation by the Operator and usage by the Developer.
More discussion is needed
Next Steps:
ย
First priority is to complete the YAML and the documentation
A Specific Documentation file is not required to be compliant with the CAMARA Readiness Checklist
The work on the Test Definition will start when the YAML will be stable.
Next call: on the 23rd of April
Task report
The work is proceeding smoothly. Some discussion is still ongoing on the scope of the API, if the scope is just around anti-fraud use cases or if to open it up also to other scenarios.