Aijun,
> On Feb 26, 2026, at 22:49, Aijun Wang <[email protected]> wrote: > New Definition: > "Overload VPN routes process method (1 bit): if the value is set to 0, it > means all overload VPN routes on the sender of VPN Prefix ORF message SHOULD > be withdrawn and the receiver of such message SHOULD withdraw the overload > VPN routes matching the ORF's type-specific part, defined below". > if the value is set to 1, it means the sender of VPN Prefix ORF message > refuse to receive new overload VPN routes and the receiver of such message > should filter the newly arrived matched VPN routes. Slight change suggested: "If the value is set to 1, it means the sender of the VPN Prefix ORF message will refuse to accept new overload VPN routes and that the receiver of the VPN Prefix ORF message SHOULD NOT announce new overload VPN routes". The change is to reflect that this is a filter on the receiver's Adj-Rib-Out to the sender. > And, based on your discussions, should we change back the term "EntryID" to > "Sequence"? It seems will be helpful in some situations. That would be my suggestion. It's why I suggested waiting on resolution of this issue before recommending text changes. Having come to conclusion that sequence is relevant due to the behavior of the overload bit, I have further thoughts on the default deny behavior that is the last lingering issue. I'll try to propose some text later today. -- Jeff _______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
