Re: NXDOMAIN and NXRRSET with SOA

[Luis S. <lui...@gm...>]

You are responding to my first or second email?
Regarding the first I think that it might help insert the negative element
inside the SetResponse. Regarding the second, the ttl value must be the
minimum value and not the ttl value from the soa record.

Kind Regards,
Luis

On Mon, Sep 1, 2008 at 6:23 PM, Brian Wellington <bwe...@xb...> wrote:

> On Mon, 1 Sep 2008, Luis Silva wrote:
>
> Hi!
>> Sorry for this last email since I noticed that in this cases you case the
>> negative element with the soa record. But I also noticed that you used the
>> ttl value from the soa record instead of the minimum. According with the
>> rfc
>> 2308 it says that the minimum value is used in these situations:
>>
>> "The remaining of the current meanings, of being the TTL to be used
>>  for negative responses, is the new defined meaning of the SOA minimum
>>  field."
>>
>> you see the opposite in the addNegative method in Cache.java:
>>
>> addNegative(Name name, *int* type, SOARecord soa, *int* cred) {
>> *long* ttl = 0;
>> *if* (soa != *null*)
>> ttl = soa.getTTL();
>> ...
>> }
>> Do you agree?
>>
>
> I don't see a problem here.  The cache is caching the records as
> transmitted, which looks fine.  If a caching server is planning to use the
> records from the cache, it might need to do additional work, just as any
> other caching server would do.
>
> Brian
>