BIND 10 #3103: Kea IPv4 fails ANVL test 2.4 ("A DHCP server always returns its own address in the 'server identifier' option")

[BIND 10 Development]

#3103: Kea IPv4 fails ANVL test 2.4 ("A DHCP server always returns its own address
in the 'server identifier' option")
-------------------------------------+-------------------------------------
            Reporter:  jwright       |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  medium        |                    Milestone:  DHCP-
           Component:  dhcp4         |  QA Defects
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         Sub-Project:  DHCP          |              Defect Severity:
Estimated Difficulty:  0             |  Medium
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by tomek):

 Interesting test. Section 4.1 of RFC2131 says:
 {{{
    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. To accommodate potentially incomplete network
    connectivity, a server MUST choose an address as a 'server
    identifier' that, to the best of the server's knowledge, is reachable
    from the client.  For example, if the DHCP server and the DHCP client
    are connected to the same subnet (i.e., the 'giaddr' field in the
    message from the client is zero), the server SHOULD select the IP
    address the server is using for communication on that subnet as the
    'server identifier'.
 }}}

 Kea uses just a single server-identifier, which is an IP address taken
 from the first interface that is up, running, is not loopback and has
 global IPv4 address assigned.

 We will need to keep the current ability to force specific server-id, but
 it must be optional. We need to implement a way to have dynamic server-id,
 so the server will pick server-id depending on the interface over which
 communication occurs.

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