3 ms·
I understand your point that the "news" part is that RCS standard now includes E2EE, rather than about Apple's support for said standard. But I don't think it'
by stephenr 2y ago
I understand your point that the "news" part is that RCS standard now includes E2EE, rather than about Apple's support for said standard.
But I don't think it's fair to suggest or imply that this development is unrelated to Apple either.
RCS has been a thing for nearly a decade, and Google's RCS backend has been doing non-standard E2EE for half that time.
Within 8 months of Apple publicly announcing they would adopt RCS and work with GSMA to support standardised E2EE, there is suddenly a standard for it...
- OneDeuxTriSeiGo 2y agoIt is worth noting that the E2EE system they are using (MLS/RFC9420) was only finalised as a standard as of mid 2023 and has had errata from the last few months. They basically added E2EE to RCS more or less as soon as the protocol they are using standardized with IETF.
- hocuspocus 2y agoGoogle has been working on replacing the ad-hoc Signal protocol with MLS since before Apple announced they'd support RCS, it would have happened anyway. It's more likely Apple was made aware of the spec/Jibe/Messages roadmap when they finally got on board, decided not to target the latest UP version for some reason, and realized implementing the current E2EE scheme would be wasted effort given it would need to be revamped within a year. The iOS RCS client is still pretty far from being provisioned worldwide.