On 9 September 2017 at 00:32, Tony Finch <d...@dotat.at> wrote:

> Paul Vixie <p...@redbarn.org> wrote:
> >
> > if they really need this, they should provide a method by which i can
> specify
> > both a TTL and an Expiry, and i will consider publishing both values,
> and if i
> > do, then they can use them the way i intend them.
>
> RRSIG sort-of does that?
>
>
Perhaps there's value in looking at HTTP's Cache-Control frankenbeast,
particularly RFC 5861. Being able to specify stale-on-error /
stale-while-revalidate (or explicitly *not*) alongside a hard TTL could be
useful.

Cheers
-- 
  Matthew Kerwin
  http://matthew.kerwin.net.au/
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop

Reply via email to