BIND 10 #1447: DDNS design document

[BIND 10 Development]

#1447: DDNS design document
-------------------------------------+-------------------------------------
                   Reporter:  jelte  |                 Owner:  jelte
                       Type:  task   |                Status:  reviewing
                   Priority:  major  |             Milestone:
                  Component:         |  Sprint-20111220
  Unclassified                       |            Resolution:
                   Keywords:         |             Sensitive:  0
            Defect Severity:  N/A    |           Sub-Project:  DNS
Feature Depending on Ticket:  DDNS   |  Estimated Difficulty:  6
        Add Hours to Ticket:  0      |           Total Hours:  6
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => jelte
 * status:  accepted => reviewing


Comment:

 Hello

 I'm not sure how exactly we agreed on finishing design tasks. Should
 someone else have a look as well?

 Anyway, the design makes sense mostly. I noticed one thing, in the
 configuration section. The thing you propose doesn't allow DDNS for other
 than IN classes it seems. Not that it would be possible to handle
 different ones currently (as our implementation of the data source API
 doesn't handle it), but having the public configuration interface designed
 so it can't be done seems strange. Should it be two level named set? Like
 ddns/zones/IN/example.org/acl?

 Also, should there be some more interface definition, so parts would be
 done in parallel?

 Are there going to be threads, or will it be single-threaded and blocking
 on the socket where it gets packets?

 Thanks

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