IETF Logo Mail Archive

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

Hugo Salgado <hsalgado@nic.cl> Thu, 07 April 2022 18:02 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 AA2A43A11CD for <dnsop@ietfa.amsl.com>; Thu, 7 Apr 2022 11:02:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 7yH1P6POjgl2 for <dnsop@ietfa.amsl.com>; Thu, 7 Apr 2022 11:02:54 -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 3A5113A11CE for <dnsop@ietf.org>; Thu, 7 Apr 2022 11:02:53 -0700 (PDT)
Received: from mail.nic.cl (localhost [127.0.0.1]) by mail.nic.cl (Postfix) with ESMTP id 02E2B195D62EE; Thu, 7 Apr 2022 14:02:51 -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 DEB61195D6287; Thu, 7 Apr 2022 14:02:50 -0400 (-04)
Date: Thu, 07 Apr 2022 14:02:49 -0400
From: Hugo Salgado <hsalgado@nic.cl>
To: Paul Vixie <paul=40redbarn.org@dmarc.ietf.org>
Cc: dnsop@ietf.org
Message-ID: <20220407180249.GA164061@pepino>
References: <164925410133.8707.7855283268813227906@ietfa.amsl.com> <28d0d9c8-a8a1-0313-0f25-dd8c7dbac087@redbarn.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="5vNYLRcllDrimb99"
Content-Disposition: inline
In-Reply-To: <28d0d9c8-a8a1-0313-0f25-dd8c7dbac087@redbarn.org>
X-Virus-Scanned: ClamAV using ClamSMTP on Thu Apr 7 14:02:51 2022 -0400 (-04) (mail.nic.cl)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/sc2gFROsn4vc-BYNWJN8k4-kV8w>
Subject: Re: [DNSOP] I-D Action: draft-ietf-dnsop-rrserial-01.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, 07 Apr 2022 18:02:56 -0000

On 06:42 07/04, Paul Vixie wrote:
> hugo, mauricio,
> 
> i hope you will change your nomenclature. a zone serial applies to an rrset
> not just to an rr. answers contain rrsets not merely rrs. other than this,
> your proposal looks solid to me.
> 

Thank you very much Paul, agree with specifying that it is a set.

However it's not clear to me what you mean by *nomenclature*. Is it
about changing the name of RRSERIAL to RRSETSERIAL? (Or RRS-SERIAL?)
Or will it be enough to clarify it in the introduction and change the
references from "resource record" to "resource record set"?

Hugo

v2.23.0 | Report a Bug | By Email