Re: [DNSOP] I-D Action: draft-ietf-dnsop-rrserial-00.txt

Hugo Salgado <hsalgado@nic.cl> Mon, 14 June 2021 14:03 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 E85373A25B2 for <dnsop@ietfa.amsl.com>; Mon, 14 Jun 2021 07:03:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=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 oEM_zFRZir6b for <dnsop@ietfa.amsl.com>; Mon, 14 Jun 2021 07:03:29 -0700 (PDT)
Received: from mail.nic.cl (mail.nic.cl [200.1.123.8]) (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 338D23A25D8 for <dnsop@ietf.org>; Mon, 14 Jun 2021 07:03:26 -0700 (PDT)
Received: from mail.nic.cl (localhost [127.0.0.1]) by mail.nic.cl (Postfix) with ESMTP id 9AB2A195D5CEF; Mon, 14 Jun 2021 10:03:23 -0400 (-04)
Received: from pepino (unknown [190.163.103.228]) (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 81607195D5B41; Mon, 14 Jun 2021 10:03:23 -0400 (-04)
Date: Mon, 14 Jun 2021 10:03:22 -0400
From: Hugo Salgado <hsalgado@nic.cl>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Cc: dnsop@ietf.org
Message-ID: <20210614140322.GA3276@pepino>
References: <162342216090.6059.5920585323129043595@ietfa.amsl.com> <20210613161540.GA14433@sources.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="AhhlLboLdkugWU4S"
Content-Disposition: inline
In-Reply-To: <20210613161540.GA14433@sources.org>
X-Virus-Scanned: ClamAV using ClamSMTP on Mon Jun 14 10:03:23 2021 -0400 (-04) (mail.nic.cl)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/C9Pt7rfAS9oHhpGsHWC-BGWKoyE>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-rrserial-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: Mon, 14 Jun 2021 14:03:40 -0000

On 18:15 13/06, Stephane Bortzmeyer wrote:
> On Fri, Jun 11, 2021 at 07:36:00AM -0700,
>  internet-drafts@ietf.org <internet-drafts@ietf.org> wrote 
>  a message of 39 lines which said:
> 
> >         Title           : The "RRSERIAL" EDNS option for the SOA serial of a RR's zone
> >         Authors         : Hugo Salgado
> >                           Mauricio Vergara Ereche
> > 	Filename        : draft-ietf-dnsop-rrserial-00.txt
> 
> I do not understand why the RRSERIAL EDNS is not added for NXDOMAIN
> responses (section 3.2). Specially since it is added for SERVFAIL,
> which is surprising.
> 

Originally it was specified only for NOERROR, but after a suggestion in
the list it was seen that it could have value for some cases of SERVFAIL
where there are problems with certain RRs but it is possible to return
the RRSERIAL of the queried zone, which can help debugging.

In the case of NXDOMAIN, the reason for not adding RRSERIAL is because
the response already has the SOA in the AUTHORITY, which would make it
redundant.

Hugo