BIND 10 #2892: blank client_id/server_id don't causes DHCPv6 server to discard messages

[BIND 10 Development]

#2892: blank client_id/server_id don't causes DHCPv6 server to discard messages
-------------------------------------+-------------------------------------
            Reporter:  wlodekwencel  |                         Type:
              Status:  new           |  defect
           Milestone:  New Tasks     |                     Priority:
            Keywords:  dhcp,         |  medium
  client_id, server_id               |                    Component:  dhcp6
           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
-------------------------------------+-------------------------------------
 Attached files are wireshark sessions.
 It looks like that DHCP (bind10-1.0.0/src/bin/dhcp6/dhcp6_srv.cc) checks
 only presence of client_id/server_id in messages not it's content.

 file:
 all_with_blank_client_id refers to
 RFC 3315 Section 15.2
 "Servers MUST discard any Solicit messages that do not include a Client
 Identifier option" and 15.4, 15.5, 15.6, 15.7, 15.8,

 file:
 request_wrong_server_id refers to
 RFC 3315 Section 15.4
 "Servers MUST discard any received Request message that meet any of the
 following conditions:
    -  the contents of the Server Identifier option do not match the
       server's DUID" and probably to: 15.6, 15.8, 15.9 (not tested)

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