Skip to content

Conversation

@uhoreg
Copy link
Member

@uhoreg uhoreg commented Nov 27, 2020

@uhoreg uhoreg added the proposal A matrix spec change proposal label Nov 27, 2020
@uhoreg uhoreg changed the title MSCxxxx: [WIP] Matrix-flavoured MLS MSC2883: [WIP] Matrix-flavoured MLS Nov 27, 2020
@turt2live turt2live added the kind:core MSC which is critical to the protocol's success label Nov 28, 2020
@uhoreg uhoreg added the e2e label Dec 31, 2020
@turt2live turt2live added the needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. label Jun 8, 2021
a `|`, as that is how identity is represented (see the Credentials section
above).\] If the base epoch is the initial epoch, then the `commit_event`
property should be set to the event ID of the `m.room.create` event.
* send to-device messages to all new devices with type `m.room.encrypted`
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Welcome messages could also be sent to room, rather than as to-device messages. We need to figure out which one is better.


```json
{
"algorithm": "m.mls.v1.welcome.[ciphersuite]",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"algorithm": "m.mls.v1.welcome.[ciphersuite]",
"algorithm": "m.dmls.v1.welcome.[ciphersuite]",


\[TODO: In MLS, a group is identified by a <256-byte string. Matrix does not
have a limit on the length of room IDs. We should probably set a length limit
as other identifiers have a length limit. We could also use a hash of the room
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In 1.11 room IDs are now explicitly limited to 255 bytes: https://spec.matrix.org/v1.11/appendices/#room-ids

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

e2e kind:core MSC which is critical to the protocol's success needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants