Repository : ssh://git@diktynna/doc

On branches: backup-redmine/2023-01-14,main

commit 62fecea0137e663379673d40967eda7c0fa52f72 Author: Linus L��ssing linus.luessing@c0d3.blue Date: Mon Dec 26 17:06:21 2022 +0000

doc: batman-adv/Multicast-Packet-Type

62fecea0137e663379673d40967eda7c0fa52f72 batman-adv/Multicast-Packet-Type.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/batman-adv/Multicast-Packet-Type.textile b/batman-adv/Multicast-Packet-Type.textile index 69bdf686..4a720d4f 100644 --- a/batman-adv/Multicast-Packet-Type.textile +++ b/batman-adv/Multicast-Packet-Type.textile @@ -150,7 +150,7 @@ h3. -Fragmentation / MTUs:-

h3. -Adding a sequence number? / How to avoid loops with tracker marking later?-

--When later implementing a split control <-> data plane as originally envisioned, by allowing to send a multicast packet with only the tracker TVLV, without data. And caching this information to fill a multicast routing table. And then allowing to send a multicast packet without the tracker TVLV afterwards, there is the following issue:- +-When later implementing a split control <=> data plane as originally envisioned, by allowing to send a multicast packet with only the tracker TVLV, without data. And caching this information to fill a multicast routing table. And then allowing to send a multicast packet without the tracker TVLV afterwards, there is the following issue:-

-When first a path is marked through the tracker TVLV, then paths change due to OGM updates. And then a tracker packet marks such new paths then the merger of both the old and newly tracker marked paths could create routing loops, as the old path is not automatically invalidated.-