BIND 10 #2668: DATASRC_DATABASE_FIND_TTL_MISMATCH (BIND 9 is different from BIND 10)

[BIND 10 Development]

#2668: DATASRC_DATABASE_FIND_TTL_MISMATCH  (BIND 9 is different from BIND 10)
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  medium        |                    Milestone:  New
           Component:  data source   |  Tasks
            Keywords:                |                   Resolution:
           Sensitive:  0             |                 CVSS Scoring:
         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):

 Replying to [comment:2 jreed]:
 > RFC2181:5.2
 >
 > A bug in BIND 9 to serve it?
 >
 > Looks like BIND 10 did right thing by setting to the value of the lowest
 TTL in the RRSet.

 No, BIND 9 is correct (if this is what I guessed).  It looks like a
 bug of BIND 10.  See the last para of Section 3 of RFC4034.
 {{{
    The TTL value of an RRSIG RR MUST match the TTL value of the RRset it
    covers.  This is an exception to the [RFC2181] rules for TTL values
    of individual RRs within a RRset: individual RRSIG RRs with the same
    owner name will have different TTL values if the RRsets they cover
    have different TTL values.
 }}}

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