DDS-SECURITY 1.3b1 RTF Avatar
  1. OMG Issue

DDSSEC13 — Clarify handling of competing same-GUID participant announcements before authentication

  • Key: DDSSEC13-99
  • Status: open  
  • Source: Sun Yat-sen University ( Yixuan Yang)
  • Summary:

    DDSI-RTPS §8.5.3.3.2 keys the SPDP discovery cache by Participant GUID and specifies insertion when no matching key exists, but does not clearly state how a receiver handles an announcement from a different sender claiming a GUID that is already present.

    DDS Security §9.8.3 permits a participant that fails authentication to be matched as Unauthenticated when allow_unauthenticated_participants is TRUE. Table 33 says a participant that later authenticates displaces an unauthenticated participant with the same GUID. It is unclear what processing is required to let the second claimant reach that authentication step.

    In particular, please clarify:

    Must the receiver preserve and process the second claimant’s discovery IdentityToken so that it can attempt authentication, even while a record with the same GUID exists?

    Before either claimant is authenticated, may an announcement from the second sender refresh the first claimant’s GUID-keyed lease without replacing or separately retaining its discovery data?

    Is there a required way to associate an incoming authentication request with the second claimant when the GUID-keyed record currently describes the first?

  • Reported: DDS-SECURITY 1.2 — Mon, 9 Nov 2026 07:45 GMT
  • Updated: Thu, 12 Nov 2026 12:51 GMT