Hello Bess WG members and Authors of draft-ietf-bess-evpn-umr-mobility draft-ietf-bess-evpn-umr-mobility specifies, in Section 5.2, that a gateway confirming a host has left every local PE resets its intra data center MAC mobility counter to zero and then propagates that fact onward. The document has no failure handling section, and does not state what a gateway does if it restarts after performing the local reset but before the withdrawal reaches remote gateways.
https://datatracker.ietf.org/doc/draft-dikshit-bess-evpn-mobility-crdt/ models the per gateway mobility sequence state as a Last Writer Wins Register. This is a Conflict Free Replicated Data Type with a convergence guarantee. The guarantee holds under message delay and loss, and duplicate messages are also taken care of. The recovery behavior in this case therefore follows from the data type's themselves, instead of requiring a new procedure. Kindly review https://datatracker.ietf.org/doc/draft-dikshit-bess-evpn-mobility-crdt/ and provide your inputs. Best Regards, Saumya
_______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
