Changes between Initial Version and Version 3 of Ticket #4038


Ignore:
Timestamp:
Sep 16, 2015, 10:13:57 PM (4 years ago)
Author:
sar
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #4038

    • Property Summary changed from Allow for very leases with long lifetimes to Allow for leases with very long lifetimes
    • Property Milestone changed from Kea-proposed to DHCP Outstanding Tasks
  • Ticket #4038 – Description

    initial v3  
    11Kea should be able to support leases with long life times.  There are several issues and potential workarounds
    221) The biggest issue is probably if the time value gets treated as a 32 bit signed integer somewhere either in the code or when being written to or read from storage.  When using an epoch of 1970 this will mean the values wrap in 2038 which for longer leases could be a problem.
    3 2) The best solution would be to try and ensure that any lease time value will work but this may not be doable if somebody insists on putting in maximal values (2g-1, 4g-1 2^^64 -1 etc).
     32) The best solution would be to try and ensure that any lease time value will work but this may not be doable if somebody insists on putting in maximal values (2g-1, 4g-1 2 to 64th -1 etc).
    443) Adding a token indicating an infinite value (for example INFINITE or NEVER).   This would need to be properly handled throughout any processing of the life time including storing and retrieving the lease from storage.
    554) Adjust the code to put a limit on the values used when processing a life time.
    665) Change the configuration to limit what values can be used for lifetimes such that they won't be able to wrap.
    7 
    8 
    9 
    10 Likely the biggest issue will be if the time value is treated as a 32 bit signed integer somewhere - using the standard epoch of 1970 leases with a