From 9e8a23550a9385fba0b52ed518430ad1b2584c34 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jes=C3=BAs=20Poderoso?= <120394830+JesusPoderoso@users.noreply.github.com> Date: Wed, 4 Sep 2024 08:55:11 +0200 Subject: [PATCH] Fix bug in initial peers documentation (#896) * Refs #21443: Fix bug in initial peers documentation Signed-off-by: JesusPoderoso * Refs #21443: Apply rev suggestions Signed-off-by: JesusPoderoso --------- Signed-off-by: JesusPoderoso --- docs/fastdds/discovery/simple.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/fastdds/discovery/simple.rst b/docs/fastdds/discovery/simple.rst index d91787dce..bac2bda3a 100644 --- a/docs/fastdds/discovery/simple.rst +++ b/docs/fastdds/discovery/simple.rst @@ -122,13 +122,13 @@ must listen for incoming Participant Discovery Protocol (PDP) discovery metatraf to a multicast address and another one linked to a unicast address. *Fast DDS* allows for the configuration of an initial peers list which contains one or more such IP-port address pairs corresponding to remote DomainParticipants PDP discovery listening resources, so that the local -DomainParticipant will not only send its PDP traffic to the default multicast address-port specified by its domain, -but also to all the IP-port address pairs specified in the initial peers list. +DomainParticipant will only send its PDP traffic to the IP-port address pairs specified in the initial peers list. A DomainParticipant's initial peers list contains the list of IP-port address pairs of all other DomainParticipants with which it will communicate. -It is a list of addresses that a DomainParticipant will use in the unicast discovery mechanism, together or as an -alternative to multicast discovery. +It is a list of addresses that a DomainParticipant will use in the PDP discovery mechanism, and can hold both multicast +and unicast addresses. +The default multicast address will be used if the list is empty. Therefore, this approach also applies to those scenarios in which multicast functionality is not available. According to the `RTPS standard `_ (Section 9.6.1.1), the RTPSParticipants'