[DNSOP] Fwd: New Version Notification for draft-pusateri-dnsop-update-timeout-00.txt

Tom Pusateri <pusateri@bangj.com> Fri, 24 August 2018 00:53 UTC

Return-Path: <pusateri@bangj.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 8A3AF130F86 for <dnsop@ietfa.amsl.com>; Thu, 23 Aug 2018 17:53:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id rY3c1O9KQpWq for <dnsop@ietfa.amsl.com>; Thu, 23 Aug 2018 17:53:54 -0700 (PDT)
Received: from oj.bangj.com (amt0.gin.ntt.net []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9813130F84 for <dnsop@ietf.org>; Thu, 23 Aug 2018 17:53:53 -0700 (PDT)
Received: from [] (unknown []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id 26BB32DC4 for <dnsop@ietf.org>; Thu, 23 Aug 2018 20:49:42 -0400 (EDT)
From: Tom Pusateri <pusateri@bangj.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_61986937-3310-4042-9298-3B6C9D6A608C"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Message-Id: <AFB90F6F-5D99-4403-AAB6-1123727973E6@bangj.com>
References: <153507165910.12116.7113196606839876181.idtracker@ietfa.amsl.com>
To: dnsop WG <dnsop@ietf.org>
Date: Thu, 23 Aug 2018 20:53:51 -0400
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/alrsMgYMrmdZVFUCnhzs_CurMgc>
Subject: [DNSOP] Fwd: New Version Notification for draft-pusateri-dnsop-update-timeout-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Aug 2018 00:53:56 -0000

This is a new draft for your review.

It is aimed at authoritative servers that handle DNS Update messages. It provides a way for the authoritative server to put a bounds on the lifetime of the added records and a way to share that lifetime with secondary servers.

If you run an Update server, we would love to have your feedback as to the usefulness of this new record type. If you maintain authoritative server software, we would love to have your feedback on whether this is something you would consider implementing or taking a pull request for.

Tom & Tim

> Begin forwarded message:
> From: internet-drafts@ietf.org
> Subject: New Version Notification for draft-pusateri-dnsop-update-timeout-00.txt
> Date: August 23, 2018 at 8:47:39 PM EDT
> To: "Tim Wattenberg" <mail@timwattenberg.de>de>, "Tom Pusateri" <pusateri@bangj.com>
> A new version of I-D, draft-pusateri-dnsop-update-timeout-00.txt
> has been successfully submitted by Tom Pusateri and posted to the
> IETF repository.
> Name:		draft-pusateri-dnsop-update-timeout
> Revision:	00
> Title:		DNS TIMEOUT Resource Record
> Document date:	2018-08-23
> Group:		Individual Submission
> Pages:		10
> URL:            https://www.ietf.org/internet-drafts/draft-pusateri-dnsop-update-timeout-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-pusateri-dnsop-update-timeout/
> Htmlized:       https://tools.ietf.org/html/draft-pusateri-dnsop-update-timeout-00
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-pusateri-dnsop-update-timeout
> 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 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