Re: TTLs in QTYPE=* caching

["Eric A. Hall" <ehall@ehsco.com>]

Robert Elz wrote:

>     Date:        26 Nov 2003 23:35:40 -0000
>     From:        "D. J. Bernstein" <djb@cr.yp.to>
>     Message-ID:  <20031126233540.37951.qmail@cr.yp.to>
> 
>   | Suppose, for example, that a name has a 3600-second A record and a
>   | 60-second MX record. The cache receives a QTYPE=* query for that name.
>   | Two minutes later, it receives another. What happens?
> 
> Kevin, if you respond to this - also explain what happens when the
> cache receives a QTYPE=* query 30 seconds after the initial query
> (with all of the same config as above).

Easiest approach to making these queries cachable is to synchronize the
TTLs of all the RRs in the response, and set a flag somewhere that a
qtype=* query was made for the owner name. If there's any RRs for that
name in memory, then you've got all of the RRs.

This wouldn't be the first qtype to require extra processing. Being a
little different doesn't mean impossible.

-- 
Eric A. Hall                                        http://www.ehsco.com/
Internet Core Protocols          http://www.oreilly.com/catalog/coreprot/


--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>