Hi Tony,
A possible enhancement on LSDB re-synchronization is described below for
discussions.
The current method: Whenever an existing link/adjacency L is added to the
flooding topology (FT for short), a full LSDB re-synchronization is requested
and executed over link L. Even though the adjacency between two end nodes over
link L is already there and their LSDBs are the same in most of situations, the
full LSDB re-synchronization is executed, which consumes the power for
processing IGP messages and the link bandwidth for transferring IGP messages.
This may cause some issues if some links are added to the FT frequently.
Considering the cases where the LSDBs may be out of synchronization around
the time period from a link on the current FT down to link L added to the FT
for some reason such as a new FT computation. This period should be short in
general.
Method A: Let one end node of link L send the other end node the LSP/LSAs
that are changed during the time period.
In general, the LSDBs are mostly synchronized among some nodes (i.e., the
number of LSP/LSAs changed is mostly zero) when link L not on the FT is added
to the FT. In this case, Method A almost does nothing, i.e., there is no link
state with changes that needs the end node to send its adjacent node over link
L.
Method B: Combine the current method with Method A. If the number of
LSP/LSAs that are changed is small, then use Method A; otherwise, use the
current method.
Best Regards,
Huaimo
_______________________________________________
Lsr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/lsr
