BIND 10 #3210: Kea4 must not echo back client-id

[BIND 10 Development]

#3210: Kea4 must not echo back client-id
-------------------------------------+-------------------------------------
            Reporter:  tomek         |                        Owner:
                Type:  defect        |  UnAssigned
            Priority:  very high     |                       Status:
           Component:  dhcp4         |  reviewing
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-DHCP-20131016
         Sub-Project:  DHCP          |                   Resolution:
Estimated Difficulty:  0             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  Low
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by tomek):

 * owner:   => UnAssigned
 * status:  new => reviewing


Comment:

 Again, the issues became more complex after a closer look. There's RFC6842
 that changes the behaviour:

 pre-RFC6842 (or vanilla RFC2131): MUST NOT send client-id
 updated RFC2131 (RFC682 changes): MUST send client-id

 Since we need both behaviours, a new flag to control this was needed :(
 Yay for parser updates.

 Oh well. So be it. The code is ready for review.

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