Message identifier for deduplication.

[jimmarino]

Discussed in #257

^{Originally posted by ndr-brt May 6, 2026}
In the current version, there's no messageId attributed in the messages.

Such property could be used to accomplish message deduplication: if for any reason, as timeout retry, a participant agent is sending a message multiple times, the counter party should be able to ignore another message that has been already processed or it's still in processing.

What's the group take on this?

[jimmarino]

This is an issue. My proposal is to create a DSP profile that adds support for reliable quality of service to the base protocol.

This Reliable Messaging profile will add the following property to every message type:

• messageId: A unique uuid.

The profile can be added to the best practices document or included as a note to the specification. This is not a technical change to the specification, as it is an overlay to the existing protocol.