Opened 4 years ago

Last modified 2 years ago

#3248 new defect

DHCPv6: Set the lease expiration time for the NameChangeRequests

Reported by: marcin Owned by:
Priority: medium Milestone: Outstanding Tasks
Component: dhcp6 Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: Low
Sub-Project: DHCP Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

Currently the DHCPv6 server is generating NameChangeRequests? using the IAADDR options carried in the server's response. This precludes setting the lease expiration time for the NameChangeRequests? to the expiration time set in the lease because the IAADDR doesn't carry this information. We may want to consider generating the NameChangeRequests? based on the lease data (like in the DHCPv4) which would give more flexibility.

Subtickets

Change History (1)

comment:1 Changed 2 years ago by tomek

  • Milestone changed from DHCP Outstanding Tasks to Outstanding Tasks

Milestone renamed

Note: See TracTickets for help on using tickets.