Re: [DNSOP] Terminology: "primary master"

Matthew Pounsett <matt@conundrum.com> Thu, 23 November 2017 14:00 UTC

Return-Path: <matt@conundrum.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 57186128DE5 for <dnsop@ietfa.amsl.com>; Thu, 23 Nov 2017 06:00:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=conundrum-com.20150623.gappssmtp.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 0hQJIpT3OI-1 for <dnsop@ietfa.amsl.com>; Thu, 23 Nov 2017 06:00:25 -0800 (PST)
Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (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 A146D128D8B for <dnsop@ietf.org>; Thu, 23 Nov 2017 06:00:25 -0800 (PST)
Received: by mail-io0-x22d.google.com with SMTP id 79so19156584ioi.3 for <dnsop@ietf.org>; Thu, 23 Nov 2017 06:00:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=conundrum-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=OHJU5l5nvOhmGzPDc2ca5EPd2Dm7ots0BYIPWgA005Q=; b=OQoM7AkhZrSj1zc4RepLXZ4LdAE4itSMtWcf5B/0vJSpzmPW+Fg8GtHrQS2Z+buUXx tXW8Ez5tvW5J4FMTo0ovzKj18rJr5gjqnrKbcjxldM4krZXYBTdGmHOT2otRHetUYj6Q AWACoWOXvOl4NcHmPVTkS6BtaBCpTdTlXJaX8Ox0qQz7BQvA/upg5Hm6LMRIGfJVWURS sa0h7MQlroPlyZ+V55gOTLLr16MDubt4HxRTqTUpjMkGVc4/4/KFFTDBUo9MxFaEQFBb 2ipnpnx/RRz2kl/Ofz19IYWVcZL5huwhib/i74Uxuo70byHIvJvqA5V3X2ZgcwnKoEJ/ frTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=OHJU5l5nvOhmGzPDc2ca5EPd2Dm7ots0BYIPWgA005Q=; b=tM2Fo3wRyh/CKKNW5sJZlJMVx34GKeWMdqEcRVscbXAu/aE9UCWwYvLmuVRGlmwMpk pSGvsu2MdQzv9sS3phREvzEe2n1PEu6NAdcRziJgjOoou1pIWNEB/GbVUXHerqFDLk5K ope4Lx9A9HfferOmX9C2JjhKu7vZyodkoVHFlHPHdYByZM/nt3jHy+geArJ+x5YOBv/5 gvf8DTSA5GRJWv0rYlUU9QG94YnzEHuY9FcpUhTH4IP8SSFEf8BxhEmiRhw+wx1kdhmU 7KR84Pt7eUiDQGKA16Kps0XihZLE8Zqj4hQVt9k3lEKgOGdmjKQRClqn4hJ5jizzza1L hd+w==
X-Gm-Message-State: AJaThX5NKy/NSl+6D7FP85NHySUpjlQosVO8yjqAy8DuQaWPY8F0+6dX f6W8w4bgFMVs4s7lKP56vQh2nYuQwn9sGQ4rUhLox4+k
X-Google-Smtp-Source: AGs4zMYjUBFWYWqmwmqJt52oN+A7SqZYNymAKbDSIlyFxrJVWLhUo+j7iO7vOfOmdb1/oYws4QQYZgAJCxkGjN5Ujv8=
X-Received: by 10.107.15.19 with SMTP id x19mr26336933ioi.7.1511445624771; Thu, 23 Nov 2017 06:00:24 -0800 (PST)
MIME-Version: 1.0
Received: by 10.2.181.188 with HTTP; Thu, 23 Nov 2017 06:00:24 -0800 (PST)
In-Reply-To: <20171123.121943.1115399549648860645.he@uninett.no>
References: <20171123.121943.1115399549648860645.he@uninett.no>
From: Matthew Pounsett <matt@conundrum.com>
Date: Thu, 23 Nov 2017 09:00:24 -0500
Message-ID: <CAAiTEH_qNut2XuVF5B3akYG0=3uUeEAwPy_MUYc1qehTSWC1Fg@mail.gmail.com>
To: Havard Eidnes <he@uninett.no>
Cc: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="001a113f1bac8fef67055ea6dbb6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/6CdT9ah_BB_Kj3m4ahTAZihiaHs>
Subject: Re: [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 14:00:28 -0000

On 23 November 2017 at 06:19, Havard Eidnes <he@uninett.no> wrote:

> 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.
>

I think the intent of the text is that an name is only used by the protocol
in RFC 2136.  It is referenced as a concept in RFC 1996, but not used by
the protocol.  But I agree that the text above is confusing, and if that's
the intent then it should be rewritten.


>
> 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?
>

That doesn't make sense to me either.  Perhaps somebody thinks that Update
messages are no longer in use?