Handle multi-prefixes in Reply message properly.
Per RFC8415 section 18.2.10.1, client should properly handle Reply
message in response to Renew/Rebind message:
- if Reply message has any new prefix in the client bindings, client
should accept it, e.g. due to renumbering events.
- if Reply message doesn't include any request prefix of client
binding due to server cannot extend the prefix lifetime, client
should just keep it as-is, and stop sending renew/rebind message
for these prefixes, which results in these prefixes expire eventually.
Bug: 260934173
Test: atest NetworkStackIntegraitonTests
Change-Id: I399117d553f0a7ab7a633a6d4cec83a696bb261e
2 files changed