DNS TIMEOUT Resource Record
draft-pusateri-dnsop-update-timeout-02

Document Type Active Internet-Draft (individual)
Last updated 2019-03-04
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                              T. Pusateri
Internet-Draft                                             T. Wattenberg
Intended status: Standards Track                            Unaffiliated
Expires: September 5, 2019                                 March 4, 2019

                      DNS TIMEOUT Resource Record
                 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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on September 5, 2019.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of

Pusateri & Wattenberg   Expires September 5, 2019               [Page 1]
Internet-Draft           TIMEOUT Resource Record              March 2019

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Sources of TIMEOUT Expiry Time  . . . . . . . . . . . . . . .   3
   4.  Resource Record Composition . . . . . . . . . . . . . . . . .   3
     4.1.  Represented Record Type . . . . . . . . . . . . . . . . .   4
     4.2.  Represented Record Count  . . . . . . . . . . . . . . . .   4
     4.3.  Method Identifiers  . . . . . . . . . . . . . . . . . . .   4
       4.3.1.  Method Identifier 0: NO METHOD  . . . . . . . . . . .   5
       4.3.2.  Method Identifier 1: RDATA  . . . . . . . . . . . . .   5
     4.4.  Expiry Time . . . . . . . . . . . . . . . . . . . . . . .   5
   5.  TIMEOUT RDATA Wire Format . . . . . . . . . . . . . . . . . .   5
   6.  Primary Server Behavior . . . . . . . . . . . . . . . . . . .   7
   7.  Secondary Server Behavior . . . . . . . . . . . . . . . . . .   7
   8.  TIMEOUT RDATA Presentation Format . . . . . . . . . . . . . .   7
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   10. Security Considerations . . . . . . . . . . . . . . . . . . .   9
   11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   9
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     12.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Appendix A.  Example TIMEOUT resource records . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   DNS Update [RFC2136] provides a mechanism to dynamically add/remove
   DNS resource records to/from a zone.  When a resource record is
   dynamically added, it remains in the zone until it is removed
   manually or via a subsequent DNS Update.  A zone administrator may
   want to enforce a default lifetime for dynamic updates (such as the
   DHCP lease lifetime) or the DNS Update may contain a lifetime using
   an EDNS(0) Update Lease option [I-D.sekar-dns-ul].  However, this
   lease lifetime is not communicated to secondary servers and will not
   endure through server software restarts.  Therefore, this
   specification defines a new DNS TIMEOUT resource record that
   associates a lifetime with one or more resource records with the same
   owner name, type, and class that can be transferred to secondary
   servers through normal AXFR [RFC5936], IXFR [RFC1995] transfer
   mechanisms.

   An UPDATE lifetime could be stored in a proprietary database on an
   authoritative primary server but there is an advantage to saving it
Show full document text