Greetings again. draft-ietf-dnsop-serve-stale has a few places where it suggest
ranges for values, but these suggestions are vague. I propose that the
suggestions be made stronger so that resolver implementers know what to do
while giving operators choices.
Section 4:
Values SHOULD
be capped on the orders of days to weeks, with a recommended cap
of 604,800 seconds.
Could be:
Values SHOULD
be capped to 604,800 seconds, and implementations SHOULD allow
lower values to be configured by operators.
Section 4:
When returning a response containing stale records, the recursive
resolver MUST set the TTL of each expired record in the message to a
value greater than 0, with 30 seconds RECOMMENDED.
Could be:
When returning a response containing stale records, the recursive
resolver MUST set the TTL of each expired record in the message to a
value greater than 0, with 30 seconds RECOMMENDED. Implementations
SHOULD allow values above 0, but SHOULD NOT allow values greater
than 600 seconds.
Section 5:
The maximum stale timer should be
configurable, and defines the length of time after a record expires
that it should be retained in the cache. The suggested value is
between 1 and 3 days.
Could be:
The maximum stale timer should be
configurable, and defines the length of time after a record expires
that it should be retained in the cache. The value SHOULD be
one day, and SHOULD NOT be longer than 3 days.
--Paul Hoffman
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
