Changes between Version 8 and Version 9 of RecursorCacheRequirements


Ignore:
Timestamp:
Dec 20, 2010, 2:06:15 AM (7 years ago)
Author:
zhanglikun
Comment:

Minor fix: change section number error, from "5.4.2" to "5.4.1"

Legend:

Unmodified
Added
Removed
Modified
  • RecursorCacheRequirements

    v8 v9  
    3030Since some local zones need to be coped according the draft draft-ietf-dnsop-default-local-zones, two rrset caches will be needed by recursor, L1 and L2. L1 containing local zones and any authoritative zones we want to server, and L2 containing the transient data.
    3131
    32 The key for one rrset in cache should be "Domain_name + Type + Class". In the value part, besides of the rdata of each rr in the rrset, there should be the signature of rrset(rrsig record), if it has, the authoritative level(for the ranking, see section 5.4.2 in RFC2181), and the security status(dnssec validation result) of rrset.
     32The key for one rrset in cache should be "Domain_name + Type + Class". In the value part, besides of the rdata of each rr in the rrset, there should be the signature of rrset(rrsig record), if it has, the authoritative level(for the ranking, see section 5.4.1 in RFC2181), and the security status(dnssec validation result) of rrset.
    3333
    3434The expiration time for rrsets in cache should be "now + TTL", once one rrset expires, it should never be used again.