5 ms·
An effort is underway to standardize E2E encrypted group messaging in the IETF with the MLS [1] protocol. Open-source participants include Wire and Matrix. Co
by walterbell 8y ago
An effort is underway to standardize E2E encrypted group messaging in the IETF with the MLS [1] protocol. Open-source participants include Wire and Matrix. Commercial participants include Facebook, Cisco, Google and Apple.
[1] https://datatracker.ietf.org/wg/mls/about/ https://datatracker.ietf.org/wg/mls/about/
Wire is open-source today and usable by regular people, with E2E encryption and email-only accounts.
- scruffyherder 8y agoAll the usual suspects. It'll die like the google chat thing(s).
- walterbell 8y agoAlways possible. As a counter-precedent of success, https://www.opus-codec.org https://www.opus-codec.org for WebRTC came from the IETF, Skype and others.
- mtgx 8y agoI'm curious, have you followed those discussions, and have you noticed say Google or Facebook do anything to "nudge" the protocol towards being "more convenient to use" (read: less secure) and less privacy friendly than it was originally intended to be?
- wbl 8y agoWe're all individuals at the IETF. I have seen people agree to changes that make their job harder because it was the right thing to do.
- SamWhited 8y agoHow is Wire developed and funded? This was my biggest problem with Matrix (unsustainable funding model for the protocol and no proper standards body). Why not just use XMPP? Yes, everyone hates XML, but the protocol is well designed, has sustainable funding (via the IETF and XSF), and there's lots of experience out there, and it's flexible enough to develop services like Slack on top of.
- walterbell 8y agoThey are VC funded and sell services (Wire Pro, Wire Red) to large companies.
- SamWhited 8y agoThat seems like enough of a reason not to pick it as a good shared base protocol, even if technically it's good. It's nice that they're funding MLS though; looking forward to the results of that effort.
- walterbell 8y agoCould you give some examples of acceptable funding models?
- blancNoir 8y agoHere's what Moxie Marlinspike has to say about the drawbacks of XMPP. https://signal.org/blog/the-ecosystem-is-moving/ https://signal.org/blog/the-ecosystem-is-moving/ "XMPP is an example of a federated protocol that advertises itself as a “living standard.” Despite its capacity for protocol “extensions,” however, it’s undeniable that XMPP still largely resembles a synchronous protocol with limited support for rich media, which can’t realistically be deployed on mobile devices. If XMPP is so extensible, why haven’t those extensions quickly brought it up to speed with the modern world? Like any federated protocol, extensions don’t mean much unless everyone applies them, and that’s an almost impossible task in a truly federated landscape. What we have instead is a complicated morass of XEPs that aren’t consistently applied anywhere. The implications of that are severe, because someone’s choice to use an XMPP client or server that doesn’t support video or some other arbitrary feature doesn’t only affect them, it affects everyone who tries to communicate with them. It creates a climate of uncertainty, never knowing whether things will work or not. In the consumer space, fractured client support is often worse than no client support at all, because consistency is incredibly important for creating a compelling user experience."
- SamWhited 8y ago
- irq-1 8y ago> It is not a goal of this group to enable interoperability/federation between messaging applications beyond the key establishment, authentication, and confidentiality services. Full interoperability would require alignment at many different layers beyond security, e.g., standard message transport and application semantics. The focus of this work is to develop a messaging security layer that different applications can adapt to their own needs. From your link.