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

Document Type Active Internet-Draft (individual)
Last updated 2018-08-23
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: February 24, 2019                               August 23, 2018

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

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.

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 February 24, 2019.

Copyright Notice

   Copyright (c) 2018 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 February 24, 2019               [Page 1]
Internet-Draft           TIMEOUT Resource Record             August 2018

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  TIMEOUT Resource Record Properties  . . . . . . . . . . . . .   3
   3.  Secondary Server Behavior . . . . . . . . . . . . . . . . . .   3
   4.  Sources of TIMEOUT Expiry Time  . . . . . . . . . . . . . . .   4
   5.  Resource Record Composition . . . . . . . . . . . . . . . . .   4
     5.1.  Hash Count  . . . . . . . . . . . . . . . . . . . . . . .   5
     5.2.  Hash Algorithm Index  . . . . . . . . . . . . . . . . . .   5
     5.3.  Expiry Time . . . . . . . . . . . . . . . . . . . . . . .   5
     5.4.  Cryptographic Hashes  . . . . . . . . . . . . . . . . . .   6
   6.  Cryptographic Hash Requirements . . . . . . . . . . . . . . .   6
     6.1.  REQUIRED Cryptographic Hash Algorithm . . . . . . . . . .   6
   7.  TIMEOUT RR RDATA Wire Format  . . . . . . . . . . . . . . . .   6
   8.  TIMEOUT RR RDATA Presentation Format  . . . . . . . . . . . .   8
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   10. Security Considerations . . . . . . . . . . . . . . . . . . .   8
   11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   9
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     12.1.  Normative References . . . . . . . . . . . . . . . . . .   9
     12.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

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].  This lease
   lifetime is not communicated to secondary servers and will not endure
   through server software restarts.  This specification defines a new
   DNS TIMEOUT resource record that associates a lifetime with one or
   more resource records with the same owner name and class that can be
   transferred to secondary servers through normal AXFR [RFC5936], IXFR
   [RFC1995] transfer mechanisms.

1.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [RFC2119].
Show full document text