| Internet-Draft | mocha-reactions | July 2026 |
| Jennings & Nandakumar | Expires 7 January 2027 | [Page] |
This document specifies reactions for MOCHA (MoQ Open Communication & Hosting Architecture). It supports message-targeted reactions (emoji on a specific chat message) and standalone reactions (engagement signals such as applause or raised hands).¶
This note is to be removed before publishing as an RFC.¶
Status information for this document may be found at https://datatracker.ietf.org/doc/draft-jennings-moq-mocha-reactions/.¶
Discussion of this document takes place on the Media Over QUIC Working Group mailing list (mailto:moq@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/moq/. Subscribe at https://www.ietf.org/mailman/listinfo/moq/.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 7 January 2027.¶
Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
This document specifies how MOCHA enables real-time reaction exchange using MOQT's publish/subscribe model. Two modes are supported:¶
Emoji responses referencing a specific chat message MsgID.¶
Standalone engagement signals (applause, raised hands) directed at the channel as a whole.¶
Both modes use the same track structure.¶
See BCP 14 [RFC2119] [RFC8174].¶
This document uses terminology defined in [MOCHA-ARCH] and MOQT primitives defined in [MoQTransport]. Message identifiers (MsgID) are defined in [MOCHA-CHAT].¶
("mocha_v1", <Provider>, <OrgID>, "reactions", <TeamID>,
<ChannelID>, <HClientID>)
¶
HClientID and HDevID are derived per [MOCHA-IDENTITY], Section "Identifier Derivation".¶
Each device publishes reactions on its own track:¶
react_v1_<HDevID>¶
Within each group, reactions are assigned sequentially increasing Object IDs starting at 0. Each reaction occupies one MOQT object.¶
Reactions are encoded as JSON [JSON] and compressed per the MOCHA_COMPRESSION track property defined in [MOCHA-CHAT].¶
{
"type": 1,
"value": "thumbs-up",
"ts": 1715788800000,
"sender": {
"userId": "<obtained via credential, see MOCHA-IDENTITY>",
"devId": "<obtained via credential, see MOCHA-IDENTITY>"
},
"target": {
"msgId": "a1b2c3...f0a1b2"
},
"ext": {}
}
¶
Integer reaction type. See Section 4.4.¶
String identifying the specific reaction (e.g., "thumbs-up", "fire", "raise").¶
Creation time in milliseconds since Unix epoch.¶
Object with userId and devId fields.¶
Object with msgId field (hex-encoded MsgID per [MOCHA-CHAT]). Present for message-targeted reactions; absent for standalone reactions. {#target-field}¶
Extension fields. Implementations MUST ignore unknown keys.¶
| Value | Name | Description |
|---|---|---|
| 1 | emoji | Emoji reaction (heart, fire, thumbs-up) |
| 2 | vote | Poll or vote response |
| 3 | raise | Raise/lower hand |
| 4 | applause | Applause or cheer |
| 5 | custom | Application-defined reaction |
Extensible via IANA registry.¶
Each reaction type defines integer encodings for its values:¶
Emoji (type 1):¶
| Integer | Value |
|---|---|
| 1 | thumbs-up |
| 2 | thumbs-down |
| 3 | heart |
| 4 | fire |
| 5 | laugh |
| 6 | sad |
| 7 | wow |
| 8 | clap |
| 9 | thinking |
| 10 | eyes |
TODO: The range of emoji values to be supported is not clear at this point and further discussion is needed.¶
Values 11-127 are reserved for future standard emoji. Values 128+ are available for application-defined emoji.¶
Raise (type 3):¶
| Integer | Value |
|---|---|
| 1 | raise |
| 2 | lower |
Vote (type 2) and Applause (type 4) value encodings are application-defined.¶
To retract a reaction, a device publishes an object with the
same type, value, and target, plus "remove": true. The
receiver removes the matching reaction from display.¶
To send a reaction, a device publishes a MOQT object to its track within the reactions namespace.¶
Message-targeted: At most 1 reaction of a given type per message per device (newer replaces older).¶
Standalone: At most 1 reaction per second per device.¶
Relays MAY enforce rate limits and drop excess objects.¶
A participant discovers reaction tracks via SUBSCRIBE_NAMESPACE on the reactions namespace prefix, then subscribes to the announced tracks.¶
TODO¶
TODO¶