BIND 10 #2786: DHCPv4: domain-name option must be encoded as text and NOT as FQDN

[BIND 10 Development]

#2786: DHCPv4: domain-name option must be encoded as text and NOT as FQDN
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  marcin                             |                Status:  new
                       Type:         |             Milestone:  DHCP
  defect                             |  Outstanding Tasks
                   Priority:  high   |              Keywords:
                  Component:  dhcp4  |             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      |
-------------------------------------+-------------------------------------
 The DHCP standard options are created using option definitions defined in
 the std_option_defs.h. The definition for '''domain-name''' V4 option is
 invalid as it specifies that the option carries the FQDN value while it
 actually carries a string value (RFC2132, section 3.17).

 As a result, the server will encode the domain name as FQDN using
 technique described in section 3.1 of RFC 1035. The client will assume
 that the domain name value was sent as a pure string and will decode it
 that way. This will lead to the invalid domain name value on the client's
 side.

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