[DNSOP] Terminology: primary, secondary, master, slave

Paul Hoffman <paul.hoffman@vpnc.org> Fri, 24 April 2015 18:33 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCF111B3111 for <dnsop@ietfa.amsl.com>; Fri, 24 Apr 2015 11:33:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.053
X-Spam-Level:
X-Spam-Status: No, score=0.053 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_MISMATCH_COM=0.553] autolearn=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 o4Pi9nRxPt5U for <dnsop@ietfa.amsl.com>; Fri, 24 Apr 2015 11:33:33 -0700 (PDT)
Received: from proper.com (Opus1.Proper.COM [207.182.41.91]) (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 755391ACE39 for <dnsop@ietf.org>; Fri, 24 Apr 2015 11:33:25 -0700 (PDT)
Received: from [10.20.30.101] (50-1-98-218.dsl.dynamic.fusionbroadband.com [50.1.98.218]) (authenticated bits=0) by proper.com (8.15.1/8.14.9) with ESMTPSA id t3OIXO1x099571 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <dnsop@ietf.org>; Fri, 24 Apr 2015 11:33:24 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: proper.com: Host 50-1-98-218.dsl.dynamic.fusionbroadband.com [50.1.98.218] claimed to be [10.20.30.101]
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <B261195B-7592-4B67-94E6-9741E853AD4A@vpnc.org>
Date: Fri, 24 Apr 2015 11:33:23 -0700
To: "dnsop@ietf.org WG" <dnsop@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/_2jgGrA3dXZ8p3NXYTWuRP3vZ0I>
Subject: [DNSOP] Terminology: primary, secondary, master, slave
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 24 Apr 2015 18:33:33 -0000

Greetings again. Based on Casey's proposal, I would like to make the following changes. Thoughts?

--Paul Hoffman

CURRENT:

Primary servers and secondary servers --- These are synonyms for "master server" and "slave server",
which were the terms used in the early DNS RFCs, and defined below. The current common usage has
shifted to "primary" and "secondary".

Slave server --- An authoritative server which uses zone transfer to retrieve the zone.
(Quoted from {{RFC1996}}, section 2.1)
{{RFC2182}} describes slave servers in detail.

Master --- Any authoritative server configured to be the source of zone transfer
for one or more slave servers. (Quoted from {{RFC1996}}, section 2.1)
{{RFC2136}} defines "master" as "an authoritative server configured to be the source of AXFR or IXFR
data for one or more slave servers".

================================

PROPOSED:

Secondary server --- "An authoritative server which uses zone transfer to retrieve the
zone" (quoted from {{RFC1996}}, section 2.1).  {{RFC2182}} describes secondary servers in
detail.  Although early DNS RFCs such as {{RFC1996}} referred to this as a "slave", the
current common usage has shifted to calling it a "secondary".

Slave server --- See secondary server.

Primary server --- "Any authoritative server configured to be the source of zone transfer
for one or more [secondary] servers" (quoted from {{RFC1996}}, section 2.1) or, more
specifically, "an authoritative server configured to be the source of AXFR or IXFR data
for one or more [secondary] servers" (quoted from {{RFC2136}}).  Although early DNS RFCs
such as {{RFC1996}} referred to this as a "master", the current common usage has shifted
to "primary".

Master server --- See primary server.