BIND 10 #3036: Modify DHCP6 to generate NameChangeRequest

[BIND 10 Development]

#3036: Modify DHCP6 to generate NameChangeRequest
-------------------------------------+-------------------------------------
            Reporter:  marcin        |                        Owner:
                Type:  enhancement   |  UnAssigned
            Priority:  medium        |                       Status:
           Component:  dhcp-ddns     |  reviewing
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-DHCP-20130731
         Sub-Project:  DHCP          |                   Resolution:
Estimated Difficulty:  0             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by marcin):

 * owner:   => UnAssigned
 * status:  new => reviewing


Comment:

 Implemented the new Option6ClientFqdn class which encapsulates the DHCPv6
 Client FQDN Option. Server now processes this option sent by client and
 generates the response. The server behaviour with respect to the FQDN
 Option is not configurable at the moment. This will be implemented in the
 next turn. When client sends the FQDN option server will generate
 !NameChangeRequests which are added to the FIFO queue. This queue is not
 processed at the moment and all requests stored there are dropped. In the
 future, it is planned to implement the logic which will passed requests
 from this queue to the !NameChangeSender to send them to bind10-d2 module
 for processing.

 Also, added a section in the developer's guide that describes how the FQDN
 option is processed.

 Proposed !ChangeLog entry:
 {{{
 6XX.    [func]          marcin
         bind10-dhcp6: Server processes the DHCPv6 Client FQDN Option
         sent by a client and generates the response. The DHCPv6 Client
         FQDN Option is represented by the new class in the libdhcp++.
         As a result of FQDN Option processing, the server generates
         NameChangeRequests which represent changes to DNS mappings for
         a particular lease (addition or removal of DNS mappings).
         Currently all generated NameChangeRequests are dropped. Sending
         them to bind10-d2 will be implemented with the future tickets.
         (Trac #3036, git abc)
 }}}

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