Inconsistent TTL after Lookup operation after lease expiry.

[NikhilReddy-2]

Sometimes the LOOKUP operation on an expired lease gives out the following output with the TTL set to some value instead of '0'

  1 {
  2  "Request": {
  3   "Client": "529fc41a-a770-11ed-a40b-3a0bc855fd65",
  4   "Resource": "52638892-a770-11ed-bcf8-3a0bc855fd65",
  5   "Operation": "LOOKUP"
  6  },
  7  "Response": {
  8   "Client": "529fc41a-a770-11ed-a40b-3a0bc855fd65",
  9   "Resource": "52638892-a770-11ed-bcf8-3a0bc855fd65",
 10   "Status": "Success",
 11   "LeaseState": "EXPIRED",
 12   "TTL": 56,
 13   "TimeStamp": {
 14    "LeaderTerm": 1,
 15    "LeaderTime": 1146
 16   }
 17  }
 18 }

[00pauln00]

Nikhil, what is the expected value of the TTL here? Also, how does this relate to the discussion we had regarding the calculation of the TTL (and placement into the reply) by the lease issuer? IMO, the TTL should not be here - only the lease state and the time stamp.