BIND 10 #1262: AXFR-style IXFR-in protocol handling

[BIND 10 Development]

#1262: AXFR-style IXFR-in protocol handling
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  vorner
  jinmei                             |                Status:  accepted
                       Type:  task   |             Milestone:
                   Priority:         |  Sprint-20111011
  blocker                            |            Resolution:
                  Component:  xfrin  |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DNS
            Defect Severity:  N/A    |  Estimated Difficulty:  0
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Assuming this is relatively an easy and small task, I'd suggest
 adding one small feature: deciding AXFR vs IXFR.

 For example, BIND 9 decides it as follows:

 1. If the zone doesn't have a corresponding DB, use AXFR.
 2. Otherwise, if it's a result of 'rndc retransfer', use AXFR.
 3. Otherwise, if it's known IXFR hasn't worked for the zone in previous
    attempts, use AXFR.
 4. Otherwise, decide IXFR vs AXFR based on the server configuration
    (per server and per zone basis)  (It basically defaults to IXFR).

 Right now, we partially do 4.  We may also emulate 2, if it's a result
 of the 'retransfer' command via bindctl.  1 would be necessary for the
 very first transfer (unless some copy of the zone is manually
 installed).

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