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

Paul Vixie <paul@redbarn.org> Thu, 07 April 2022 18:10 UTC

Return-Path: <paul@redbarn.org>
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 7E6F83A11C4 for <dnsop@ietfa.amsl.com>; Thu, 7 Apr 2022 11:10:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redbarn.org
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 SAI7chKn5PaI for <dnsop@ietfa.amsl.com>; Thu, 7 Apr 2022 11:10:18 -0700 (PDT)
Received: from util.redbarn.org (util.redbarn.org [24.104.150.222]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7AEFA3A1215 for <dnsop@ietf.org>; Thu, 7 Apr 2022 11:10:15 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by util.redbarn.org (Postfix) with ESMTPS id A1E4A1A2423; Thu, 7 Apr 2022 18:10:14 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=redbarn.org; s=util; t=1649355014; bh=S3BF1pAmGup8jVYpOncPL0OFE21+7y5q9cOSTDWCQLY=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=jGFBT6I4+gP66RtESm+1CRv/nM4cKBAI+ULxaCXGKA8xjdPmqy064D9igeEOs69R+ 1VMkKtq/vuYbCilG2jXLBV+IMJGKsd5gvoBj7vmXir4Ejzo7lryL5U16mBfseZGx/1 KcLBHTP4HD64n3tGD7q5YqOy0CSPxKMX0EXAU7OE=
Received: from [24.104.150.147] (dhcp-147.access.rits.tisf.net [24.104.150.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 8704C7597E; Thu, 7 Apr 2022 18:10:14 +0000 (UTC)
To: Hugo Salgado <hsalgado@nic.cl>
Cc: Paul Vixie <paul=40redbarn.org@dmarc.ietf.org>, dnsop@ietf.org
References: <164925410133.8707.7855283268813227906@ietfa.amsl.com> <28d0d9c8-a8a1-0313-0f25-dd8c7dbac087@redbarn.org> <20220407180249.GA164061@pepino>
From: Paul Vixie <paul@redbarn.org>
Message-ID: <1f62c1db-b9d4-f7d5-fdfa-c298541875d4@redbarn.org>
Date: Thu, 07 Apr 2022 11:10:15 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 PostboxApp/7.0.54
MIME-Version: 1.0
In-Reply-To: <20220407180249.GA164061@pepino>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/DBCbvcrCL5lBYt-g1nE5LaMP_Yg>
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:10:25 -0000


Hugo Salgado wrote on 2022-04-07 11:02:
> 
> 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"?
the semantics of an answer are pretty well understood -- the rrset which 
is in the zone containing the qname is easily found. therefore you could 
rename the option code to ZONESERIAL or even SERIAL and it would have an 
unambiguous meaning.

but it seems to me you'd be better off with a zero-length option called 
SERIAL which if set in the query causes the SOA of the answer's zone to 
be added to the authority section (similar to an RFC 2308 negative 
proof) and which option would only be echoed in the answer's OPT if the 
option was supported. you'd want to specify that the SOA in this case is 
not optional and that its truncation would cause the TC bit to be set.

-- 
P Vixie