Hi Les,
Thank you very much for adding the LEEF bit into the draft based on the FT
bit for a link. The bit advertised by one end node of the link indicates
whether the link is on the flooding topology.
Would you mind adding the behavior below for checking and handling the
inconsistency of the flooding topology through using this bit?
For a link L between node A and node B, if the LEEF bit for link L advertised
by node A is different from the one advertised by node B, then the flooding
topology is inconsistent, the node receiving the LEEF bit set to one for link L
from the other node adds link L on the flooding topology temporarily.
If one of the two nodes receives the LEEF bit set to one for link L from the
other, but advertises the LEEF bit set to zero for link L for a given time such
as 5 seconds, then a warning is issued or logged.
Best Regards,
Huaimo
-----Original Message-----
From: Lsr [mailto:[email protected]] On Behalf Of Les Ginsberg (ginsberg)
Sent: Tuesday, May 21, 2019 1:56 PM
To: [email protected]
Subject: Re: [Lsr] I-D Action: draft-ietf-lsr-dynamic-flooding-01.txt
Folks -
Major changes in this version include:
1)Added support for LANs as part of the flooding tropology
2)Added support for advertising what links are enabled for flooding at each
node. This is based on a proposal in draft-cc-lsr-flooding-reduction (the FT
bit) but we have defined it to be advertised associated with a link rather than
in hellos. This is to allow management tools to more easily verify correctness
of the flooding topology on each node. It does NOT change operational state in
any way.
3)Added some text around rate limiting temporary flooding when attempting to
repair a partitioned flooding topology.
Les
_______________________________________________
Lsr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lsr
