BIND 10 #2597: DHCP server must store a server ID

[BIND 10 Development]

#2597: DHCP server must store a server ID
-------------------------------------+-------------------------------------
            Reporter:  stephen       |                        Owner:  tomek
                Type:  enhancement   |                       Status:
            Priority:  medium        |  reviewing
           Component:  dhcp          |                    Milestone:
            Keywords:                |  Sprint-DHCP-20130122
           Sensitive:  0             |                   Resolution:
         Sub-Project:  DHCP          |                 CVSS Scoring:
Estimated Difficulty:  0             |              Defect Severity:  N/A
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by stephen):

 * owner:  stephen => tomek


Comment:

 > This code will never be trivial to test, so you may gain just a little
 bit, but not much. As for the minutiae of server ID manipulation, I
 believe it is in exactly the right place. That is part of the server
 duties to manage its own server identifier. Even the identifier name says
 so.
 It's more that the server ID is a component of the server which has its
 own operations associated with it - generate, read and write.  Yes, it is
 part of the server - but does the server logic have to go down to that
 level of detail?  Ideally it should just use the server ID; it should not
 have to worry how it is preserved across restarts.

 However, I'm not dogmatic about it. Please merge.

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