BIND 10 #3201: Options with no data fields and containing sub options are not parsed correctly

[BIND 10 Development]

#3201: Options with no data fields and containing sub options are not parsed
correctly
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  marcin                             |                Status:  new
                       Type:         |             Milestone:  Sprint-
  defect                             |  DHCP-20131016
                   Priority:  high   |              Keywords:
                  Component:  dhcp4  |             Sensitive:  0
               CVSS Scoring:         |           Sub-Project:  DHCP
            Defect Severity:  High   |  Estimated Difficulty:  0
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 Options which contain no data fields but containing sub options only are
 defined as !''empty!'' options which encapsulate certain option space.
 Unfortunately, the !''empty!'' options do not assume any sub options.
 Therefore, sub options in options such as RAI are not parsed at all. We
 should either have a dedicated class to represent such options or leverage
 some other existing class (like OptionCustom) to encapsulate such options
 (and guarantee that sub options are unpacked).

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