Re: [DNSOP] Question regarding RFC 8499

Michael De Roover <ietf@nixmagic.com> Tue, 04 August 2020 23:11 UTC

Return-Path: <ietf@nixmagic.com>
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 53C603A10D6 for <dnsop@ietfa.amsl.com>; Tue, 4 Aug 2020 16:11:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 YhsRPlkZVNid for <dnsop@ietfa.amsl.com>; Tue, 4 Aug 2020 16:11:37 -0700 (PDT)
Received: from nixmagic.com (e3.nixmagic.com [212.237.5.239]) by ietfa.amsl.com (Postfix) with ESMTP id 6CB773A10C5 for <dnsop@ietf.org>; Tue, 4 Aug 2020 16:11:36 -0700 (PDT)
Received: from tp.lan (tp.lan [192.168.10.23]) by nixmagic.com (Postfix) with ESMTPS id 1074311A26; Tue, 4 Aug 2020 23:11:35 +0000 (UTC)
Message-ID: <c535e2eba885a82fb4fd6e967884498473b6c099.camel@nixmagic.com>
From: Michael De Roover <ietf@nixmagic.com>
To: Paul Vixie <paul@redbarn.org>, dnsop@ietf.org
Date: Wed, 05 Aug 2020 01:11:34 +0200
In-Reply-To: <5303244.dBo8Fx6Cfl@linux-9daj>
References: <86c18e80-88ab-5503-f63c-f788766a2675@ghnou.su> <98d1a954-db22-2a2e-490e-0a9b1208843a@nic.cz> <5303244.dBo8Fx6Cfl@linux-9daj>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.30.5-1.1
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/SZNLvW7hSVlwwgE3yw9BF71yp2o>
Subject: Re: [DNSOP] Question regarding RFC 8499
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: Tue, 04 Aug 2020 23:11:39 -0000

Hello,

Sorry for the late reply.
I feel concerned about using the term "responder" for a zone transfer
target. Instinctively it makes me think of a DNS server responding to a
regular query. In a non-DNS context it would make me think of a first
responder in e.g. health services. Wouldn't it be unintuitive to use
this term for a zone transfer?

On Thu, 2020-07-23 at 08:50 +0000, Paul Vixie wrote:
> i introduced the master/slave terminology in rfc 2136, because i
> needed names 
> for the roles in an AXFR/IXFR transaction, and the zone transfer
> hierarchy 
> could be more than one layer deep, such that a server might initiate
> some 
> AXFR/IXFR's to the "primary master" but then respond to AXFR/IXFR's
> from other 
> servers. in retrospect i should have chosen the terms, "transfer
> initiator" 
> and "transfer responder". however, the hydraulic brake and clutch
> systems in 
> my car had "master cylinders" and "slave cylinders", and so i did not
> think i 
> was either inventing a new use for the words "master" and "slave", or
> that my 
> use of them for this purpose would be controversial. i was naive, and
> i 
> suggest that we revisit the terminology we use in all our distributed
> systems, 
> starting with DNS zone transfer roles.
-- 
Met vriendelijke groet / Best regards,
Michael De Roover