[MLS] AEAD data in messages

Peter Slatala <psla@google.com> Mon, 12 August 2019 22:36 UTC

MIME-Version: 1.0
From: Peter Slatala <psla@google.com>
Date: Mon, 12 Aug 2019 12:06:42 -0700
Message-ID: <CAJ1bmR=T031ZPXz2iUAvxcRfTg8e-C0-WtFS=GH0+KSbU4phTA@mail.gmail.com>
To: mls@ietf.org
Cc: Benjamin Beurdouche <benjamin.beurdouche@inria.fr>
Content-Type: multipart/alternative; boundary="00000000000004ceab058ff03ba9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mls/-wlRMMQblM3VjmmcbeFQfaV8PBI>
Subject: [MLS] AEAD data in messages
Precedence: list

Hello!
I was wondering if you considered allowing additional plaintext but
authenticated data in MLS messages.

While I can't think of immediate, compelling use cases right now, I am
wondering if such extensibility wouldn't be desired. For example, in
encrypted video calls, resolution, framerate, or audio volume can be put in
plaintext so that the selective forwarding unit can decide which streams to
forward to the group members (and the recipient also uses this data).

Here are some use-cases for MLS that I can think of:
* sending a 'sending device identifier' in case if delivery service can't
differentiate different user devices from each other.
* sending 'message type' that server can act upon. For example, delivery
report sent by the recipient to the sender, which also acts as an ACK to
the server that the message was persisted.
* authenticating message id (but make it visible to server to avoid
redelivery),
* other use cases that I can't think of right now.

Have you considered supporting AEAD, or is it already supported and I
missed it?

Thanks,
Peter

[MLS] AEAD data in messages Peter Slatala