Hi all, I have just submitted "Stretching DNS TTLs" (draft-wkumari-dnsop-ttl-stretching-00).
The very high level overview is: If you are doing something like HAMMER / pre-fetch, and cannot reach the authoritative server when trying to refresh a record, you may continue to use a record past the TTL. This is working on the theory that stale bread is better than no bread. This is a strawman doc / idea, I'm expecting much discussion on if the above is true. NOTE: I believe that there may be (non-Google) IP associated with this. A lawyer will be filing the IPR disclosure later today (time zone differences, etc). W ---------- Forwarded message ---------- From: <internet-dra...@ietf.org> Date: Mon, Nov 14, 2016 at 1:55 PM Subject: New Version Notification for draft-wkumari-dnsop-ttl-stretching-00.txt To: Warren Kumari <war...@kumari.net> A new version of I-D, draft-wkumari-dnsop-ttl-stretching-00.txt has been successfully submitted by Warren Kumari and posted to the IETF repository. Name: draft-wkumari-dnsop-ttl-stretching Revision: 00 Title: Stretching DNS TTLs Document date: 2016-11-14 Group: Individual Submission Pages: 4 URL: https://www.ietf.org/internet-drafts/draft-wkumari-dnsop-ttl-stretching-00.txt Status: https://datatracker.ietf.org/doc/draft-wkumari-dnsop-ttl-stretching/ Htmlized: https://tools.ietf.org/html/draft-wkumari-dnsop-ttl-stretching-00 Abstract: The TTL of a DNS Resource Record expresses how long a record may be cached before it should be discarded. This document discusses the possibility of "stretching TTLS" (using them past their expiration) if they cannot be refreshed. This works on the assumption that stale data may be better than no data. PLEASE NOTE: This document is a strawman to drive discussion. It may or may not be a good idea; this document documents the idea so that there is something concrete to throw tomatoes at. [ Ed note: Text inside square brackets ([]) is additional background information, answers to frequently asked questions, general musings, etc. They will be removed before publication. This document is being collaborated on in Github at: https://github.com/wkumari/draft- wkumari-dnsop-ttl-stretching. The most recent version of the document, open issues, etc should all be available here. The authors (gratefully) accept pull requests ] Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat -- I don't think the execution is relevant when it was obviously a bad idea in the first place. This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants. ---maf _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
