BIND 10 #2313: Custom namespaces (including vendor spaces)

[BIND 10 Development]

#2313: Custom namespaces (including vendor spaces)
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  UnAssigned
  marcin                             |                Status:  new
                       Type:  task   |             Milestone:  Sprint-
                   Priority:         |  DHCP-20121018
  medium                             |            Resolution:
                  Component:  dhcp   |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DHCP
            Defect Severity:  N/A    |  Estimated Difficulty:  0
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by stephen):

 * milestone:  DHCP 2012 => Sprint-DHCP-20121018


Old description:

> Custom namespaces play important role when it comes to specification of
> vendor options or options that encapsulate other options. In DHCPv4 the
> pool of available option codes is limited because option code value is
> uint8. For this reason option codes may be not unique and supplementary
> information is needed to identify the particular option - namespace.
> Since namespaces can group options it becomes conevnient to use namespace
> name in the OptionDefinition to point out that the particular option
> encapsulates multiple other options (belonging to the namespace). We need
> a way to specify namespaces through the Configuration Manager. This task
> assumes creation of Namespace class that holds namespace attributes.

New description:

 Custom namespaces play important role when it comes to specification of
 vendor options or options that encapsulate other options. In DHCPv4 the
 pool of available option codes is limited because option code value is
 uint8. For this reason option codes may be not unique and supplementary
 information is needed to identify the particular option - namespace. Since
 namespaces can group options it becomes conevnient to use namespace name
 in the !OptionDefinition to point out that the particular option
 encapsulates multiple other options (belonging to the namespace). We need
 a way to specify namespaces through the Configuration Manager. This task
 assumes creation of Namespace class that holds namespace attributes.

--

-- 
Ticket URL: <https://bind10.isc.org/ticket/2313#comment:1>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development