BIND 10 #3363: D2UpdateMgr should check both DHCID and IP address when scheduling jobs

[BIND 10 Development]

#3363: D2UpdateMgr should check both DHCID and IP address when scheduling jobs
-------------------------------------+-------------------------------------
            Reporter:  tmark         |                        Owner:  tmark
                Type:  defect        |                       Status:
            Priority:  medium        |  accepted
           Component:  dhcp-ddns     |                    Milestone:  DHCP-
            Keywords:                |  Kea0.9
           Sensitive:  0             |                   Resolution:
         Sub-Project:  DHCP          |                 CVSS Scoring:
Estimated Difficulty:  8             |              Defect Severity:  N/A
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by tmark):

 One potential problem with the above is that it assumes NCRs from a given
 client arrive in the order the client sent them.  I am not certain this is
 reliable behavior. Certainly, the UDP protocol does not garuantee it,
 although in practice I suspect they do.  I would not count on packets from
 different clients arriving in order.

 One possibility would be some sort of client specific sequence number
 within the NCR.
 Suffice to say this requires some  additional thought.

-- 
Ticket URL: <http://bind10.isc.org/ticket/3363#comment:2>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development