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

Document Type Active Internet-Draft (individual)
Last updated 2019-11-04
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized 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.J. Pusateri
Internet-Draft                                             T. Wattenberg
Intended status: Standards Track                            Unaffiliated
Expires: 7 May 2020                                      4 November 2019

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

Abstract

   This specification defines a new DNS TIMEOUT resource record (RR)
   that associates a lifetime with one or more zone resource records.
   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 7 May 2020.

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 the Trust Legal Provisions and are
   provided without warranty as described in the Simplified BSD License.

Pusateri & Wattenberg      Expires 7 May 2020                   [Page 1]
Internet-Draft           TIMEOUT Resource Record           November 2019

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   3
   3.  Sources of TIMEOUT Expiry Time  . . . . . . . . . . . . . . .   3
   4.  Common Usage Patterns . . . . . . . . . . . . . . . . . . . .   4
     4.1.  TIMEOUT records vs. Update Leases . . . . . . . . . . . .   5
     4.2.  Testing for TIMEOUT . . . . . . . . . . . . . . . . . . .   6
   5.  Resource Record Composition . . . . . . . . . . . . . . . . .   6
     5.1.  Represented Record Type . . . . . . . . . . . . . . . . .   6
     5.2.  Represented Record Count  . . . . . . . . . . . . . . . .   7
     5.3.  Method Identifiers  . . . . . . . . . . . . . . . . . . .   7
       5.3.1.  Method Identifier 0: NO METHOD  . . . . . . . . . . .   8
       5.3.2.  Method Identifier 1: MD-SHA256-128  . . . . . . . . .   8
     5.4.  Expiry Time . . . . . . . . . . . . . . . . . . . . . . .   8
   6.  TIMEOUT RDATA Wire Format . . . . . . . . . . . . . . . . . .   8
   7.  Server Behavior . . . . . . . . . . . . . . . . . . . . . . .  10
     7.1.  Primary Server Behavior . . . . . . . . . . . . . . . . .  10
     7.2.  Secondary Server Behavior . . . . . . . . . . . . . . . .  10
   8.  TIMEOUT RDATA Presentation Format . . . . . . . . . . . . . .  10
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  12
   11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  13
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .  13
     12.1.  Normative References . . . . . . . . . . . . . . . . . .  13
     12.2.  Informative References . . . . . . . . . . . . . . . . .  14
   Appendix A.  Example TIMEOUT resource records . . . . . . . . . .  14
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17

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.  The context of a dynamic
   update may provide lifetime hints for the updated records (such as
   the EDNS(0) Update Lease option [I-D.sekar-dns-ul]), however, this
   lifetime is not communicated to secondary servers and will not
   necessarily endure through server software restarts.  This
   specification defines a new DNS TIMEOUT resource record that
   associates lifetimes 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
Show full document text