IETF Logo Mail Archive

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

Petr Špaček <pspacek@isc.org> Thu, 07 April 2022 15:30 UTC

Return-Path: <pspacek@isc.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 BE7343A0C0B for <dnsop@ietfa.amsl.com>; Thu, 7 Apr 2022 08:30:20 -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_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isc.org header.b=WoRzz5XE; dkim=pass (1024-bit key) header.d=isc.org header.b=LNHIMCSi
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 gZ3CAYNObsdS for <dnsop@ietfa.amsl.com>; Thu, 7 Apr 2022 08:30:16 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 15FB53A0BD8 for <dnsop@ietf.org>; Thu, 7 Apr 2022 08:30:15 -0700 (PDT)
Received: from zimbrang.isc.org (zimbrang.isc.org [149.20.1.12]) (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 mx.pao1.isc.org (Postfix) with ESMTPS id 7A1B43AB026; Thu, 7 Apr 2022 15:30:14 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.10.3 mx.pao1.isc.org 7A1B43AB026
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=isc.org; s=ostpay; t=1649345414; bh=P0y2UI385lCI5ioWYVeCA5WyP8KMd5L3e6ynhouQ/pQ=; h=Date:Subject:To:Cc:References:From:In-Reply-To; b=WoRzz5XEVhLzN9/tdnBsm+c0jC4IE3wi/g72qUWrgivAFRw/CBhKPly9p2xFzswLL FmAbsmMm/BoVOhBl0U92/IAk2A5DQDXn+mX9zrba8f6wKOC5CiPX9aIIzFkFQ/JUg1 zmyrYsHpUDk+5rbqLxRXiC9k53pa5fvjYJv2ON8c=
Received: from zimbrang.isc.org (localhost.localdomain [127.0.0.1]) by zimbrang.isc.org (Postfix) with ESMTPS id 6E60898309F; Thu, 7 Apr 2022 15:30:14 +0000 (UTC)
Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbrang.isc.org (Postfix) with ESMTP id 4654D9830A0; Thu, 7 Apr 2022 15:30:14 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.10.3 zimbrang.isc.org 4654D9830A0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=05DFB016-56A2-11EB-AEC0-15368D323330; t=1649345414; bh=P0y2UI385lCI5ioWYVeCA5WyP8KMd5L3e6ynhouQ/pQ=; h=Message-ID:Date:MIME-Version:To:From; b=LNHIMCSiQqGJMVlIHi11n5rcMMoP9p0VfQZRQZ1LnnJerusNDjdhnUwce4fgH9Zsi 7jEG/UIxYzQFcVpXZnnDkiiduZyFciBH8DuX+Dko7NfQKWFI7gqrF1Cb3rL1B1ZnfF ik5tqik7T26nToUsuZ2tmN5uoKo6betN/rd2jVO0=
Received: from zimbrang.isc.org ([127.0.0.1]) by localhost (zimbrang.isc.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 2rPbxZrcJvKc; Thu, 7 Apr 2022 15:30:14 +0000 (UTC)
Received: from [192.168.0.157] (ip-86-49-254-124.net.upcbroadband.cz [86.49.254.124]) by zimbrang.isc.org (Postfix) with ESMTPSA id A712C98309F; Thu, 7 Apr 2022 15:30:13 +0000 (UTC)
Message-ID: <d12cf167-55d5-066c-eba6-c2611563f5b9@isc.org>
Date: Thu, 07 Apr 2022 17:30:11 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0
Content-Language: en-US
To: Paul Vixie <paul@redbarn.org>
Cc: dnsop@ietf.org
References: <164925410133.8707.7855283268813227906@ietfa.amsl.com> <20220406142614.GD94415@pepino> <2d437493-7f88-5a81-22a9-1bd05081f70a@isc.org> <5fb93410-d751-9c9d-8c25-5a6805f16d68@redbarn.org>
From: Petr Špaček <pspacek@isc.org>
In-Reply-To: <5fb93410-d751-9c9d-8c25-5a6805f16d68@redbarn.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/dpzHVTJoL1i1tnyRoYT9rHDn218>
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 15:30:21 -0000

On 07. 04. 22 15:47, Paul Vixie wrote:
> Petr Špaček wrote on 2022-04-06 23:54:
>> Hello,
>>
>> ...
>>
>>  From my perspective, these systems are not rare, quite the contrary:
>> - PowerDNS with a database backend
>> - Multi-master flavors of BIND
>> - Various "cloud" auths with dynamic backends
>> - Windows DNS with Active Directory (I think)
> 
> because IXFR and NOTIFY and UPDATE use serial numbers, the DNS protocol 
> itself is aware of serial numbers. i hope that any recognition of 
> non-traditional serial numbers will be an optional addition to the 
> RRSERIAL response, and that if a zone has no actual serial number (so, 
> it cannot participate in IXFR, NOTIFY, and UPDATE) the RRSERIAL value 
> will just be a magic number like zero, or just missing altogether.

I fail to understand what you mean, can you elaborate?

I will try to rephrase myself for clarity:

"Let's make this draft _also_ usable for debugging e.g. PowerDNS and 
multi-master BIND."

I cannot see any technical reason not to support it. Moreover this draft 
does not touch notify or transfer protocol in any way - which is why 
your e-mail confuses me.

-- 
Petr Špaček

v2.23.0 | Report a Bug | By Email