diff --git a/proposals/4296-device-id-mentions.md b/proposals/4296-device-id-mentions.md
new file mode 100644
index 00000000000..6eeaccf757e
--- /dev/null
+++ b/proposals/4296-device-id-mentions.md
@@ -0,0 +1,62 @@
+# MSC4296: Mentions for device IDs
+
+The [`m.mentions`] content property on events allows senders to include an indicator about whether
+the event should trigger a specialised notification for some or all room members. Among others,
+this can be used to direct events at a certain recipient group within the room. It is, however,
+not currently possible to direct events at a certain subset of devices within a room. This can
+be helpful, for instance, in cases where devices with different capabilities are participating
+in the room and the sender wants to provide a hint on which devices the recipient should pick up
+the message. This proposal makes it possible to mention specific devices via the existing
+[`m.mentions`] mechanism.
+
+## Proposal
+
+A new optional property `device_ids` is introduced in [`m.mentions`] to allow specifying device IDs
+to be mentioned by a message. Since device IDs need to be namespaced to user IDs, `device_ids` is a
+a map from user ID to an array of device IDs.
+
+```json5
+"m.mentions": {
+  "device_ids": {
+    "@alice:example.org": ["ABC1234"]
+  }
+}
+```
+
+It is legal for `room` and `user_ids` to be present within `m.mentions` simultaneously to `device_ids`.
+As before, when applying mentions, the different properties inside `m.mentions` are OR'ed. This means
+the following example should mention all of Bob's devices _and_ one of Alice's devices.
+
+```json5
+"m.mentions": {
+  "user_ids": ["@bob:example.org"],
+  "device_ids": {
+    "@alice:example.org": ["ABC1234"]
+  }
+}
+```
+
+## Potential issues
+
+Clients that don't support this proposal will recognise no mentions for their logged in user at all if
+only `device_ids` is specified within `m.mentions`.
+
+## Alternatives
+
+None.
+
+## Security considerations
+
+Device IDs are already disclosed when sending messages in encrypted rooms. Allowing their use within
+`m.mentions` does, therefore, not present an additional metadata leak.
+
+## Unstable prefix
+
+Until this proposal is accepted into the spec, implementations should refer to `device_ids` as
+`de.gematik.msc4296.device_ids`.
+
+## Dependencies
+
+None.
+
+[`m.mentions`]: https://spec.matrix.org/v1.14/client-server-api/#definition-mmentions