BIND 10 #2013: DDNS config and initial request handling

[BIND 10 Development]

#2013: DDNS config and initial request handling
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jinmei
  jinmei                             |                Status:  accepted
                       Type:  task   |             Milestone:
                   Priority:         |  Sprint-20120612
  medium                             |            Resolution:
                  Component:  DDNS   |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DNS
            Defect Severity:  N/A    |  Estimated Difficulty:  0
Feature Depending on Ticket:  DDNS   |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 This subtask is ready for review at branch "trac1458-2" (note:
 it's not derived from the ticket number, 2013).

 It turned out to be bigger than I originally thought due to various
 small miscellaneous things to complete it.  I hope the amount of diff
 is still acceptable, but since it includes several independent things
 it may require a bit harder effort for review.  If the branch seems to
 do too many things, we can discuss dividing the branch into several
 reviewable pieces.

 Some notes that may help understand the branch organization:
 - it first merges the original trac1458 branch, which should be
   excluded for review.  The part to be reviewed are commits after
   0adb4d2 (not including this one)
 - 6e9fb84 is an independent bug fix to libdns++, which was needed for
   this task.
 - e347a00 and 15340a2 are one major part of the branch, which handles
   update requests
 - 80ea487, e3cef1f, and a44b085 are changes to support necessary
   configuration, not only for ACLs, but also for (an ad hoc version
   of) data source configuration.
 - others are relatively minor small changes or documentation updates

 There are still some things that I originally intended to do in this
 task but decided to skip as it got bigger:

 - list of secondary zone is currently not configurable.  My intent is
   to populate it from zonemgr's secondary configuration.  For now, an
   empty list is always used (in practice it's not that bad, because
   the default ACL is reject-all, so requests to secondary zones will
   normally be rejected anyway).
 - `ZoneConfig` object is created for each request.  My original intent
   is to maintain it in the ddns object, but partly because the
   secondary list is undone, I chose to skip that part, too.
 - Error message for bad configuration update is not very friendly.
 - Duplicate zone configuration is currently ignored.  It's probably
   better to reject it or at least make a local log a message.

 I plan to create a separate ticket for this (I guess one ticket is
 okay, but separating them may be better), and complete it either at
 the later stage of this sprint or in the hardening sprint.  Even
 without these, the server should be able to work at a reasonable
 level.

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