Community Attendees:
Ludovic Robert krishna kumar Rafal Artych stefano.falsetto@con.ckhiod.com
Community Attendees:
LF Staff:
Agenda
Antitrust Policy
Any comment on meeting minutes- No comments
Roadmap plan:
- Target to have a decision on one or 2 yaml for meeting
- Target to have a v0.1 yaml merged for aligned with current commonalities (v0.4)
Minutes
- Administrative
Any maintainer/codeowner?- Will close this issue end of the week
- Discussion #11: When device swap occurred?
- Basically the rule is when Timestamp of last MSISDN <-> IMEI pairing change
- What about change of phone number?
- Proposal to keep it simple and consider this as a Device Swap as well
- Team approval
- krishna kumar will check with Rebecca
- stefano.falsetto@con.ckhiod.com agreed
- Proposal to keep it simple and consider this as a Device Swap as well
- What about new subscription?
- Proposal to follow sim swap rule: New subscription is considered as a SIM swap so in our case New subscription is a Device Swap
- Team approval
- krishna kumar will check with Rebecca
- stefano.falsetto@con.ckhiod.com agreed
- Proposal to follow sim swap rule: New subscription is considered as a SIM swap so in our case New subscription is a Device Swap
- What about change of phone number?
- Basically the rule is when Timestamp of last MSISDN <-> IMEI pairing change
- Discussion #10: What is the API behavior for Multi-SIM ?
- No update but not a blocking point.
- API Design - issue #6
- One or Two yaml?
- One yaml is consistent with sim swap and 'simpler' to explain
- Two yaml is more flexible to market and avoid partial implementation question
- Proposal to start with one yaml for SIM Swap consistency
- Comments open till
- krishna kumar will check with Rebecca
- stefano.falsetto@con.ckhiod.com agreed on one yaml approach
- One or Two yaml?