BIND 10 #1217: Error in automatically updating TTLs that do not match in an RRset

[BIND 10 Development]

#1217: Error in automatically updating TTLs that do not match in an RRset
-------------------------------------+-------------------------------------
                   Reporter:  jelte  |                 Owner:
                       Type:         |                Status:  new
  defect                             |             Milestone:  New Tasks
                   Priority:  major  |            Resolution:
                  Component:  data   |             Sensitive:  0
  source                             |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [ticket:1217 jelte]:

 > It would be a problem with AXFR out though (or, lower-level, the zone
 iterators). If we want to be as strict as possible, we should look at
 whether the covered types are equal too before modifying the TTL of RRSIG
 RRs. Or not check TTL for RRSIG at all.

 For the iteration case, maybe we should provide an "as is" or "RR"
 (instead of RRset) mode, where the iterator passes RRs of the zone
 in the form of an RRset containing exactly one RDATA, ignoring any
 duplicate, inconsistent TTLs, etc, and lets the caller deal with those.

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