BIND 10 #2985: rfc 2131 vs monitoring network interfaces

[BIND 10 Development]

#2985: rfc 2131 vs monitoring network interfaces
----------------------------------+--------------------------------------
            Reporter:  jankowsr   |                         Type:  defect
              Status:  new        |                     Priority:  low
           Milestone:  New Tasks  |                    Component:  dhcp4
            Keywords:  dhcpv4     |                 CVSS Scoring:
           Sensitive:  0          |              Defect Severity:  Low
         Sub-Project:  DHCP       |  Feature Depending on Ticket:
Estimated Difficulty:  0          |          Add Hours to Ticket:  0
         Total Hours:  0          |                    Internal?:  0
----------------------------------+--------------------------------------
 As of now kea does not monitor the state of network interfaces. It does
 not utilize network interfaces started after b10-dhcp4 module
 initialization. This means it's not quite compliant with the following
 part of RFC 2131:

    "The 'server identifier' field is used both to identify a DHCP server
    in a DHCP message and as a destination address from clients to
    servers.  A server with multiple network addresses MUST be prepared
    to to accept any of its network addresses as identifying that server
    in a DHCP message."

 How to reproduce:
          config add Init/components b10-dhcp4
          config set Init/components/b10-dhcp4/kind dispensable
          config commit

 start new network interface
 send DHCP discover to this new interface

 Expected Result:
 server should respond to DHCPDISCOVER

 Actual Result:
 server will discard DHCPDISCOVER

-- 
Ticket URL: <http://bind10.isc.org/ticket/2985>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development