[DNSOP] draft-pusateri-dnsop-update-timeout-02.txt

[Tom Pusateri <[e-mail]>]

DNSOP,

Thanks to the great feedback, we were able to update the document to better match the preferences of the working group and address the outstanding concerns.

To summarize the changes:

Add missing reference (Stuart Cheshire)
Modify presentation format of date/time to match RRSIG (Mark Andrews)
Remove HASH as a premature optimization and replace with actual RDATA (Ted Lemon)
Add more motivation for the need of the record (Joe Abley, Paul Wouters).
Allow multiple TIMEOUT records with the same owner name/class and simplify TIMEOUT record format to not include multiple expiry times (partly Tony Finch)

Note: going through the list, I realized that I missed the comment that we need to explain why individual records need cleaned up and not just the whole RRSet. We’ll open an issue for this and handle it in the next version.

Thanks,
Tom


> Begin forwarded message:
> 
> From: [e-mail]
> Subject: New Version Notification for draft-pusateri-dnsop-update-timeout-02.txt
> Date: March 4, 2019 at 7:26:58 PM EST
> To: "Tim Wattenberg" <[e-mail]>, "Tom Pusateri" <[e-mail]>
> 
> 
> A new version of I-D, draft-pusateri-dnsop-update-timeout-02.txt
> has been successfully submitted by Tom Pusateri and posted to the
> IETF repository.
> 
> Name:		draft-pusateri-dnsop-update-timeout
> Revision:	02
> Title:		DNS TIMEOUT Resource Record
> Document date:	2019-03-04
> Group:		Individual Submission
> Pages:		13
> URL:            https://www.ietf.org/internet-drafts/draft-pusateri-dnsop-update-timeout-02.txt
> Status:         https://datatracker.ietf.org/doc/draft-pusateri-dnsop-update-timeout/
> Htmlized:       https://tools.ietf.org/html/draft-pusateri-dnsop-update-timeout-02
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-pusateri-dnsop-update-timeout
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-pusateri-dnsop-update-timeout-02
> 
> Abstract:
>   This specification defines a new DNS TIMEOUT resource record (RR)
>   that associates a lifetime with one or more zone resource records
>   with the same owner name, type, and class.  It is intended to be used
>   to transfer resource record lifetime state between a zone's primary
>   and secondary servers and to store lifetime state during server
>   software restarts.
> 
> 
> 
> 
> 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
>