[nat64] use RLOC16 to check NAT64 prefix publisher (#12028)

This commit removes a misleading TODO comment in the NAT64 prefix
manager.

The TODO suggested changing the NAT64 prefix publisher check to use
the RLOC16 of the entry in the Network Data. However, this approach is
flawed in scenarios with multiple Border Routers.

When multiple BRs publish the same NAT64 prefix with the same
preference, `FindPreferredNat64Prefix()` may return an entry published
by a different BR. An RLOC16 check would then incorrectly cause the
current BR to believe it did not publish the prefix, potentially
leading it to withdraw its entry and cause network instability.
This commit is contained in:
Yang Song
2025-10-14 16:45:53 +02:00
committed by GitHub
parent f19864a2ac
commit d23da65a48
@@ -2503,9 +2503,6 @@ void RoutingManager::Nat64PrefixManager::Evaluate(void)
// by this BR.
// - The preferred NAT64 prefix in Network Data is same as the
// discovered infrastructure prefix.
//
// TODO: change to check RLOC16 to determine if the NAT64 prefix
// was published by this BR.
shouldPublish =
((error == kErrorNotFound) || (netdataPrefixConfig.mPreference < preference) ||