BIND 10 #1372: IXFR-out protocol handling: AXFR style IXFR

[BIND 10 Development]

#1372: IXFR-out protocol handling: AXFR style IXFR
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jinmei
  jinmei                             |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:  major  |  Sprint-20111122
                  Component:         |            Resolution:
  xfrout                             |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DNS
            Defect Severity:  N/A    |  Estimated Difficulty:  4
Feature Depending on Ticket:         |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => jinmei


Comment:

 Hello

 Replying to [comment:11 jinmei]:
 > Not necessarily, but I simply couldn't think of a case where these
 > things happen, except, of course, due to a very stupid bug in
 > b10-auth, and I thought that we should rather drop any state and
 > continue (or if it's lightweight even kill it and restart) should this
 > happen than trying to do anything more especially with someone via
 > a network.

 Well, being into philosophy, I'd say that all bugs are stupid. If the bug
 is intelligent, it becomes a feature.

 Anyway, you're right about the fact that this probably will never happen,
 therefore we don't need to spend too much time worrying about it. So leave
 it as it is.

 > Maybe we should discuss this as a general policy project-wide.
 > For this particular case, I'd rather close this ticket faster than
 > continuing the discussion (after all, this event shouldn't happen and
 > wouldn't matter much in practice, until/unless we really introduce a
 > bug in b10-auth).  I've created a diff to change the behavior to
 > returning SERVFAIL (attaching to the ticket).  If you still prefer
 > this behavior and the diff is okay, I'll introduce it and complete the
 > ticket; otherwise, if you rather defer the discussion in a generic
 > context, I'll complete this ticket without applying it.

 OK, discussion is fine. I'll try to remember for the next non-planning
 call.

 This ticket looks OK to merge.

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