... | ... | @@ -356,6 +356,8 @@ These new values could be populated in the lease's user_context in at least two |
|
|
|
|
|
At this point, regardless of the lease store used, the LeaseX::user_context\_ would contain individual JSON key/value pairs for all of the BLQ query parameters. However, this alone is not enough to allow for efficient querying.
|
|
|
|
|
|
It is important to note that v4 renewals can sent via unicast and thus not convey relay information. The existing logic in AllocEngine::updateLease4ExtendedInfo() accounts for this by only replacing extended data for an existing lease IF the current client query contains it, otherwise the existing info on the lease is retained. This needs to maintained.
|
|
|
|
|
|
### V4 Query time parameters, STOS, and CLTT
|
|
|
|
|
|
From RFC 6926/Sec. 8.2:
|
... | ... | |