Re: [DNSOP] Question regarding RFC 8499

tjw ietf <tjw.ietf@gmail.com> Thu, 23 July 2020 09:09 UTC

Return-Path: <tjw.ietf@gmail.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 53D393A0AB4 for <dnsop@ietfa.amsl.com>; Thu, 23 Jul 2020 02:09:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 HZY23Ge--c7k for <dnsop@ietfa.amsl.com>; Thu, 23 Jul 2020 02:09:55 -0700 (PDT)
Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F233F3A0AB3 for <dnsop@ietf.org>; Thu, 23 Jul 2020 02:09:54 -0700 (PDT)
Received: by mail-qt1-x82f.google.com with SMTP id w9so3878148qts.6 for <dnsop@ietf.org>; Thu, 23 Jul 2020 02:09:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=5Dih+2PZgnQ5b0jlq6Sa2V7ylOmBkka0TAopuKGcxiA=; b=myVJe+5mFplYsB7gMlb+io4BovIdYB4YGy6BNA5Q5RrxZMBwNjVp+TKpGUqmvTUo6a PTMqcAG5ojkUUmheOsqp6dhUa5DPe6wRrqIcfIDu7A5PJgU6XApzJehh3a/ZzVPRYpRI O1yUhM9hXr5vFq7fZCh5T0pQlLh72X7v1MrAxeuEYz29c9PKvcB8AsQqpgRwh0wABfvl gq0cMhk/d7h5/vRGdcFNmiLvvjed4YODh4+7XDa33gNf1e/s5iJEbqciDWNNKCKkFxmG mIevPxysnXVBOVwHNeboMaeQmDAolWmIQpF+fnlZxV+WYQqBYWT7znN/elnrNP2G+PT7 ajzA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=5Dih+2PZgnQ5b0jlq6Sa2V7ylOmBkka0TAopuKGcxiA=; b=cDjeNvIenShNUkWwIL77uWq5/az6qoMAoKla3FbQ6Wl+Yg/wRqaEb/NGVHvd+5ykOR IeDZPkt4egzGcVgNvSwOTnbRirCGMIo+g78Qlnz1L8E/oZj7hVoYA78+46+dpL1bX+p/ m3I78bZ7XLegCCBv01dO6oZ3tzc0zd1A+qP8eSabi+QWZqi3A6Y7TSLyTqRdvpnMOf2f P4oL0JSevbVhVqRr77F6yWT1SPKexnmm8Mo66DqggKiopa95GHhKcpU5TPro57uw8zkP kp4bCUTddSibEX0mx7DMmZIfQwaht23UxJDCzr6BBYMzPEbjnALMVojevCFUJse9bjLE Bgjg==
X-Gm-Message-State: AOAM531jhn6du4FDBpQrLXmQc7rmddkLg4cVZaqjZULPnPW/yvFbNBb7 vScvlWOrS62eY/PHMvYE1WPQxeg6mMw=
X-Google-Smtp-Source: ABdhPJwSQUbs54RzDP3IdDcCM+8t4NiBykhVdEamxftflnqhdWruavnhTi23rNDChi5bFnmAdumdEw==
X-Received: by 2002:aed:20c2:: with SMTP id 60mr3314227qtb.14.1595495394068; Thu, 23 Jul 2020 02:09:54 -0700 (PDT)
Received: from [192.168.1.89] (184-15-226-75.dsl2.chtn.wv.frontiernet.net. [184.15.226.75]) by smtp.gmail.com with ESMTPSA id e25sm2103584qtc.93.2020.07.23.02.09.53 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 23 Jul 2020 02:09:53 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: tjw ietf <tjw.ietf@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Thu, 23 Jul 2020 05:09:52 -0400
Message-Id: <181146C2-BBA5-458F-8CF8-86A978F928B5@gmail.com>
References: <5303244.dBo8Fx6Cfl@linux-9daj>
Cc: dnsop@ietf.org, Michael De Roover <ctrl@ghnou.su>, "libor.peltan" <libor.peltan@nic.cz>
In-Reply-To: <5303244.dBo8Fx6Cfl@linux-9daj>
To: Paul Vixie <paul@redbarn.org>
X-Mailer: iPhone Mail (17G68)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/5GvCQKNEGZVApN2ijApCGuYlhRs>
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: Thu, 23 Jul 2020 09:09:56 -0000

I’ve had several conversations with one of the 8499 authors a few months back and said that we need to adjust this. I let it drop but the topic was going to be part two f our chairs slides next week. 

The chairs did some reviewing of all Currently adopted documents as well. 

Thanks 
Tim 



Sent from my iPhone

> On Jul 23, 2020, at 05:02, Paul Vixie <paul@redbarn.org> wrote:
> 
> On Thursday, 23 July 2020 08:47:42 UTC libor.peltan wrote:
>> Hi,
>> 
>> just a factual comment.
>> 
>> While primary/secondary = master/slave is indeed a recent transition of
>> terms among DNS community, and I agree that this should be handled
>> carefully when writing new RFCs,
> 
> 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.
> 
>> ...
>> 
>> BR,
>> 
>> Libor
> 
> -- 
> Paul
> 
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop