BIND 10 #2233: Option Definition Design - V6 Options

[BIND 10 Development]

#2233: Option Definition Design - V6 Options
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  marcin
  stephen                            |                Status:  accepted
                       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      |
-------------------------------------+-------------------------------------

Comment (by marcin):

 These comments refer to both #2232 and #2233.

 The common outline design for DHCPv6 and DHCPv4 options definition had
 been created 9 months ago on BIND10 wiki:
 http://bind10.isc.org/wiki/DhcpOptionDefinition. This document has been
 now slightly extended. The following tasks are proposed to implement
 "Option Definition" for either DHCPv4 or DHCPv6:
 - Implement OptionXDefinition class
 - Extend option factory search mechanism to support searching for options
 using option code or option name. It is possible to use option code now
 but since option codes may overlap we need to add indexing using unique
 option name.
 - Create definitions of standard options - as a proof of concept that
 option definition through .spec file actually works, we may define their
 formats in the .spec file. If later decided, we may move their definition
 to the code. This task involves parsing the option definitions and
 creating the collection of all standard OptionXDefinition objects.
 - Implement OptionCollection in the Subnet class. The OptionCollection
 will hold the read-to-send options for each subnet. This task involves
 creating the parser that reads the option data from the .spec file and
 initializes the OptionCollection.
 - Add support for custom namespaces and addition of options to those
 namespaces. Options that are added to custom namespaces can be
 encapsulated by other options. At this point we need to extend
 OptionXDefinition to parse the options added to custom namespace linked
 with it and create internal list of "supported" sub-options. Other classes
 may query OptionXDefinition object to check if particular option is
 encapsulated or not.

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