[DNSOP] Terminology: "primary master"

Havard Eidnes <he@uninett.no> Thu, 23 November 2017 11:19 UTC

Return-Path: <he@uninett.no>
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 D0BE51287A5 for <dnsop@ietfa.amsl.com>; Thu, 23 Nov 2017 03:19:49 -0800 (PST)
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 oyPBGwZd1dm8 for <dnsop@ietfa.amsl.com>; Thu, 23 Nov 2017 03:19:47 -0800 (PST)
Received: from smistad.uninett.no (smistad.uninett.no [IPv6:2001:700:1:0:eeb1:d7ff:fe59:fbaa]) by ietfa.amsl.com (Postfix) with ESMTP id D380C12878D for <dnsop@ietf.org>; Thu, 23 Nov 2017 03:19:46 -0800 (PST)
Received: from smistad.uninett.no (smistad.uninett.no [158.38.62.77]) by smistad.uninett.no (Postfix) with ESMTP id C999843E9D3 for <dnsop@ietf.org>; Thu, 23 Nov 2017 12:19:43 +0100 (CET)
Date: Thu, 23 Nov 2017 12:19:43 +0100
Message-Id: <20171123.121943.1115399549648860645.he@uninett.no>
To: dnsop@ietf.org
From: Havard Eidnes <he@uninett.no>
X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/_DPDO_Bsxs6iXxoRZ8zuEmojlyg>
Subject: [DNSOP] Terminology: "primary master"
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
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 Nov 2017 11:19:50 -0000

Hi,

draft 07 says:

   Primary master:  "The primary master is named in the zone's SOA MNAME
      field and optionally by an NS RR".  (Quoted from [RFC1996],
      Section 2.1).  [RFC2136] defines "primary master" as "Master
      server at the root of the AXFR/IXFR dependency graph.  The primary
      master is named in the zone's SOA MNAME field and optionally by an
      NS RR.  There is by definition only one primary master server per
      zone."  The idea of a primary master is only used by [RFC2136],
      and is considered archaic in other parts of the DNS.

First: the last sentence's claim that the idea of a "primary
master" is only used by RFC 2136 is surely incorrect.  It is also
used in RFC 1996, where the first quote is taken from.

Secondly: can someone please explain to me why the idea of a
"primary master" where the zone data originates from and where
updates are performed is considered archaic?

Best regards,

- Håvard