The "RRSERIAL" EDNS option for the SOA serial of a RR's zone
draft-salgado-rrserial-00

Document Type Active Internet-Draft (individual)
Last updated 2019-07-30
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                               H. Salgado
Internet-Draft                                                 NIC Chile
Intended status: Informational                             July 30, 2019
Expires: January 31, 2020

      The "RRSERIAL" EDNS option for the SOA serial of a RR's zone
                       draft-salgado-rrserial-00

Abstract

   The "RRSERIAL" EDNS option allows a DNS querier to ask a DNS
   authoritative server to add a EDNS option in the answer of such query
   with the SOA serial number field of the origin zone which contains
   the answered resource record.

   This "RRSERIAL" data allows to debug problems and diagnosis by
   helping to recognize the origin of an answer, associating this answer
   with a respective zone version.

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 January 31, 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

Salgado                 Expires January 31, 2020                [Page 1]
Internet-Draft          The RRSERIAL EDNS option               July 2019

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  The RRSERIAL Option . . . . . . . . . . . . . . . . . . . . .   3
   3.  RRSERIAL Processing . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Querier . . . . . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  Responder . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Example usage . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  DNS EDNS0 Option Code Registration  . . . . . . . . . . .   4
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
   Appendix A.  Implementation References  . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   The "RRSERIAL" EDNS option [RFC6891] allows a DNS querier to ask a
   DNS authoritative server to add a EDNS option in the answer of such
   query with the SOA serial number field of the zone which contains the
   answered resource record.

   This "RRSERIAL" data allows to debugging helping to recognize the
   origin of an answer, associating this answer with a respective zone
   version.

   The DNS data is of loose coherent nature, meaning that a record
   obtained by a response could be out-of-sync with other authoritative
   sources of the same data.  This makes it difficult to debug the
   responses because you'd need to couple an answer with the version of
   the zone used to obtain such data.  Even when you could use a
   separate question to ask for the SOA RR of the zone to ask for its
   serial, this separate question is in another time and could even
   arrive to another authoritative source, so it's not directly
   correlated with another query.

   This EDNS option is aimed only to authorative servers for a zone.
   Resolvers and forwarders should ignore the option.  It's only
   intended for hop-to-hop communication (not transitive).

Salgado                 Expires January 31, 2020                [Page 2]
Internet-Draft          The RRSERIAL EDNS option               July 2019

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].

2.  The RRSERIAL Option
Show full document text