The thread sub-device is powered off and restarted, and it takes a long time to communicate after the srp update is successful

[luyou-tuya]

After the sub-device is powered off for a long time, it is restarted. After the srp update is successful, it can resolve to the Off mesh local ipv6 address of the sub-device. At this time, the app establishes a matter case session, and the sent data packet otbr is directly discarded. What is the reason? , is there no routing information?

I think the possible reason is that the EID-to-RLOC cache of otbr is invalid, so that the RLOC cannot be resolved. At this time, the thread address resolution timeout has reached the maximum default timeout time of 120s. After 120s, an address query is sent, and the communication can only be performed when the address query response is received. I don't know if this is the real reason.

We expect to be able to communicate after the srp update is successful. How should we solve this problem?