mlswg / mls-extensions Goto Github PK

The extensions draft IANA section begins:

This document requests the creation of the following new IANA registries:

• MLS Extension Types ({{extended-mls-extension-types}})
• MLS Proposal Types ({{extended-mls-proposal-types}})

This is contradictory to the clear language in the IANA considerations of the MLS protocol spec (example quoted from Section 17.2):

17.2. MLS Extension Types

This registry lists identifiers for extensions to the MLS protocol. The extension type field is two bytes wide, so valid extension type values are in the range 0x0000 to 0xffff.

New extensions are supposed to be added to the EXISTING IANA registries.

Formatting issue in code block in 2.2.4.2. Authentication with signatures

Context: mlswg/mls-protocol#821

Targeted messages should define their own wire format.

If Alice has multiple MLS clients and wants to leave a group, even with SelfRemove as worded, she still can't remove all her clients in one-shot. Maybe we should modify the semantics of SelfRemove so the ExternalSender is allowed to include other leaf nodes with the same "user" credential?

To be more future-proof, similarly to EncryptWithLabel, I guess we could design a similar function for the HPKE AuthPSK mode?
This would help ensuring future extensions that would be using the AuthPSK mode with leaf HPKE keys don't interfere with each other.

Now that there are IANA registries for those, we must extend them.