BIND 10 #1279: IXFR to AXFR fallback

[BIND 10 Development]

#1279: IXFR to AXFR fallback
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  task          |                       Status:  new
            Priority:  major         |                    Milestone:  Next-
           Component:  xfrin         |  Sprint-Proposed
           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
-------------------------------------+-------------------------------------
 This is a deferred task about IXFR-in.

 We need to handle various cases of IXFR failure and subsequent
 fallback to AXFR.  See the discussion in #1261.

 Note that there are several types of fallback:
 - fallback from IXFR to AXFR in the same TCP connection
 - fallback to AXFR after completing the IXFR session.  This may be
   further broken down into two cases: immediate fallback after failure
   and scheduling a next xfr at the zonemgr indicating this should be AXFR.

 See also BIND 9's xfrin_recv_done() (lib/dns/xfrin.c).  It covers
 some fallback scenario.

-- 
Ticket URL: <http://bind10.isc.org/ticket/1279>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development