Google to Implement IETF's Message Layer Security (MLS) Specification RFC 9420

Re:Google to Implement IETF's Message Layer Security (MLS) S... by jeroenhd on Saturday November 11, 2023 @05:55AM (#38229184)

MLS just handles the encryption part. MIMI should handle decentralisation. Combining the two should allow for E2EE interoperability between all kinds of chat services and servers (hopefully allowing for some decentralised chat services like XMPP becoming relevant again), but just MLS isn't going to cut it.

[ Parent | on HN ]

Re:Google to Implement IETF's Message Layer Security (MLS) S... by Arathorn on Saturday November 11, 2023 @12:51PM (#38232602)

MIMI isn’t decentralised (having just come back from IETF118 i can confirm this firsthand) - much like MLS, each conversation has a hub.

Matrix however is decentralised, and decentralised MLS is live and well and in active development - we need to update arewemlsyet.com.

[ Parent | on HN ]

Re:Google to Implement IETF's Message Layer Security (MLS) S... by 2Gkashmiri on Saturday November 11, 2023 @09:09PM (#38236581)

Hi.

I watched an ietf video of meeting, second last maybe? And they were discussing types of users.

Companies, like Google WhatsApp

Corporates. Govt.

End users with own servers.

The idea was end users should not be part of the decentralized network as you cant ask FB to network with a 1 person server but isnt matrix.org already able to do that? Why take that functionality away when it works without problems? Yes spam but it can be managed

[ Parent | on HN ]