Repository : ssh://git@diktynna/doc

On branches: backup-redmine/2020-07-12,master

commit f7dd4ef8311f72c939c4759d19718814a7952697 Author: Sven Eckelmann sven@narfation.org Date: Sat Jun 20 21:13:21 2020 +0000

doc: batman-adv/Multicast-optimizations-listener-reports

f7dd4ef8311f72c939c4759d19718814a7952697 batman-adv/Multicast-optimizations-listener-reports.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/batman-adv/Multicast-optimizations-listener-reports.textile b/batman-adv/Multicast-optimizations-listener-reports.textile index 86d2427..05ed802 100644 --- a/batman-adv/Multicast-optimizations-listener-reports.textile +++ b/batman-adv/Multicast-optimizations-listener-reports.textile @@ -54,7 +54,7 @@ _Disadvantages:_

h4. Side note 1: Why does the current implementation without bridge support have no such issues?

-There are usually two parties interested in multicast listener reports. For one thing, bridges ("software switches") and snooping switches (enterprise hardware switches). For another thing, multicast routers want IGMP/MLD reports. If the former, a bridge, exists then multicast optimizations are disabled at the moment, so the issue can't occure. For the latter, reports to multicast routers, let's consider the following two cases: +There are usually two parties interested in multicast listener reports. For one thing, bridges ("software switches") and snooping switches (enterprise hardware switches). For another thing, multicast routers want IGMP/MLD reports. If the former, a bridge, exists then multicast optimizations are turned off at the moment, so the issue can't occure. For the latter, reports to multicast routers, let's consider the following two cases:

a) Multicast listeners joining a link-local address b) Multicast listeners joining a non-link-local address