BIND 10 #2233: Option Definition Design - V6 Options

[BIND 10 Development]

#2233: Option Definition Design - V6 Options
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  UnAssigned
  stephen                            |                Status:  reviewing
                       Type:  task   |             Milestone:  Sprint-
                   Priority:         |  DHCP-20121004
  medium                             |            Resolution:
                  Component:         |             Sensitive:  0
  dhcpconf                           |           Sub-Project:  DHCP
                   Keywords:         |  Estimated Difficulty:  0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by marcin):

 * owner:  marcin => UnAssigned
 * status:  accepted => reviewing


Comment:

 One task missing on the list above:
 * Create ScopeX classes. Elements of these types will carry scopes and
 vandor spaces defined in the configuration manager.

 There are still a few outstanding questions. Typically:
 * Do we want user to override standard options or not,
 * How do we manage suboptions. Once scope is created we can aggregate
 suboptions with it. We can also point to this scope name in the option
 definition so as the list of sub-options can be extracted from the scope
 and included in the option. However I presume that there may be cases when
 we want to include options based on some condition. This is not yet
 resolved.

 Please review the http://bind10.isc.org/wiki/DhcpOptionDefinition.

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