[DNSOP] Was: RRSERIAL (Re: I-D Action: draft-ietf-dnsop-zoneversion-00.txt)

Hugo Salgado <hsalgado@nic.cl> Thu, 21 April 2022 14:49 UTC

Return-Path: <hsalgado@nic.cl>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1E103A1779 for <dnsop@ietfa.amsl.com>; Thu, 21 Apr 2022 07:49:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id atK8IMD5PvbO for <dnsop@ietfa.amsl.com>; Thu, 21 Apr 2022 07:49:35 -0700 (PDT)
Received: from mail.nic.cl (mail.nic.cl [IPv6:2001:1398:1::6008]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E8283A1832 for <dnsop@ietf.org>; Thu, 21 Apr 2022 07:49:32 -0700 (PDT)
Received: from mail.nic.cl (localhost [127.0.0.1]) by mail.nic.cl (Postfix) with ESMTP id 8A589195D5C7C for <dnsop@ietf.org>; Thu, 21 Apr 2022 10:49:28 -0400 (-04)
Received: from pepino (unknown [IPv6:2800:150:126:65:4a3d:968a:4938:f63c]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.nic.cl (Postfix) with ESMTPSA id 74170195D5B75 for <dnsop@ietf.org>; Thu, 21 Apr 2022 10:49:28 -0400 (-04)
Date: Thu, 21 Apr 2022 10:49:27 -0400
From: Hugo Salgado <hsalgado@nic.cl>
To: dnsop@ietf.org
Message-ID: <20220421144927.GE135809@pepino>
References: <165055235578.9397.9041977703812636023@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="hwvH6HDNit2nSK4j"
Content-Disposition: inline
In-Reply-To: <165055235578.9397.9041977703812636023@ietfa.amsl.com>
X-Virus-Scanned: ClamAV using ClamSMTP on Thu Apr 21 10:49:28 2022 -0400 (-04) (mail.nic.cl)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/agAAjkB9cKJSYnoJXbIZdkCX7JQ>
Subject: [DNSOP] Was: RRSERIAL (Re: I-D Action: draft-ietf-dnsop-zoneversion-00.txt)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 21 Apr 2022 14:49:38 -0000

Dear DNSOP group.
We've been working on a new version of the rrserial draft, this time
with some pretty substantive changes, including a name change to the
extension: ZONEVERSION.

This new draft expands the original meaning of the extension from
"a copy of the SOA serial", to "a zone version identifier", the first
and only identifier so far being the same as rrserial, but with a flag
and a registry that allows its future expansion.

So a summary of the changes is:

 - new name ZONEVERSION;
 - OPTION-DATA now has a flag, length and data;
 - relaxed the RCODEs requirements. Before, NXDOMAIN was left out
   because the SOA is included completely, but now with the new meaning
   we cannot assume that the version is included in some existing RR;
 - a first and only flag: SOA-SERIAL;
 - a registry for flags (Specification Required).

Best,

The Editors.


On 07:45 21/04, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Domain Name System Operations WG of the IETF.
> 
>         Title           : The "ZONEVERSION" EDNS option for the version token of a RR's zone
>         Authors         : Hugo Salgado
>                           Mauricio Vergara Ereche
> 	Filename        : draft-ietf-dnsop-zoneversion-00.txt
> 	Pages           : 9
> 	Date            : 2022-04-21
> 
> Abstract:
>    The "ZONEVERSION" EDNS option allows a DNS querier to request a DNS
>    authoritative server to add an EDNS option in the answer of such
>    query with a token field representing the version of the zone which
>    contains the answered Resource Record, such as the SOA serial field
>    in zones when this number corresponds to the zone version.
> 
>    This "ZONEVERSION" data allows to debug and diagnose problems by
>    helping to recognize the data source of an answer in an atomic single
>    query, by associating the response with a respective zone version.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-zoneversion/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-dnsop-zoneversion-00.html
> 
> 
> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
> 
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>