BIND 10 #2772: DHCP4: It should be possible to define options having codes 224-254 in the dhcp4 option space.

[BIND 10 Development]

#2772: DHCP4: It should be possible to define options having codes 224-254 in the
dhcp4 option space.
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  marcin                             |                Status:  new
                       Type:         |             Milestone:  DHCP
  defect                             |  Outstanding Tasks
                   Priority:         |              Keywords:
  medium                             |             Sensitive:  0
                  Component:  dhcp4  |           Sub-Project:  DHCP
               CVSS Scoring:         |  Estimated Difficulty:  0
            Defect Severity:         |           Total Hours:  0
  Medium                             |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 It has been pointed out on the bind10-users mail list:
 https://lists.isc.org/pipermail/bind10-users/2013-February/000442.html

 that it is not possible to define option having code '''252''' in the
 '''dhcp4''' option space. This appears to be a bug in the code because
 this code belongs to the pool of option codes reserved for private use
 (see http://www.iana.org/assignments/bootp-dhcp-parameters/bootp-dhcp-
 parameters.xml).

 In the closer look into the code it appears that this pool is by mistake
 excluded when checking for options in dhcp4 option space which definitions
 can be defined by a user (see src/lib/dhcp/libdhcp++.cc, function
 LibDHCP::isStandardOption).

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