DDS-SECURITY 1.3b1 RTF Avatar
  1. OMG Issue

DDSSEC13 — Clarify sender identity validation for DCPSParticipantsSecure dispose and unregister samples

  • Key: DDSSEC13-98
  • Status: open   Implementation work Blocked
  • Source: Sun Yat-sen University ( Yixuan Yang)
  • Summary:

    DDS Security 1.2 ยง7.5.1.6 requires a participant, after authenticating a remote participant, to process participant status changes (dispose or unregister) through DCPSParticipantsSecure rather than the ordinary DCPSParticipants topic.

    Consider authenticated participants B and C. C sends a cryptographically valid DCPSParticipantsSecure dispose sample whose GUID identifies B. Does the specification require the receiver to reject the sample because its authenticated sending participant or built-in writer is C, while the disposed participant instance is B?

    Please clarify the required relationship between the authenticated source, the secure built-in writer, and the participant GUID identified by a dispose or unregister sample. If the sample must be rejected, please state the validation rule and where it applies, including when discovery protection is configured as NONE.

  • Reported: DDS-SECURITY 1.2 — Mon, 26 Oct 2026 06:18 GMT
  • Updated: Tue, 27 Oct 2026 13:15 GMT