IETF Logo Mail Archive

Re: [DNSOP] Terminology: "primary master"

Joe Abley <jabley@hopcount.ca> Thu, 23 November 2017 16:48 UTC

Return-Path: <jabley@hopcount.ca>
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 B5D1C12EBB7 for <dnsop@ietfa.amsl.com>; Thu, 23 Nov 2017 08:48:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hopcount.ca
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 qzkMVCz1S9Id for <dnsop@ietfa.amsl.com>; Thu, 23 Nov 2017 08:48:08 -0800 (PST)
Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (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 0BCD412EBAC for <dnsop@ietf.org>; Thu, 23 Nov 2017 08:48:07 -0800 (PST)
Received: by mail-io0-x235.google.com with SMTP id x63so27113759ioe.6 for <dnsop@ietf.org>; Thu, 23 Nov 2017 08:48:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=iicMTLOeKjbpj78gfqHlCpm60lSZcZObEEzXfZGTaeI=; b=SxZ5O1KgVIVfrSHqXj0CdntZ/qXZp43mnWFtgGUrEcdg6wp71C65KEP9G6Qa52zkws 6RozOmgr1vjoPH7Ns13NLwE5rpM6dlhBpxtR7jKLRC14lcVf1lc3psFNSWcSULgKwsQm xZsx2D8KP5Kt5VG+l5NH1Pi+vY/e4DYk7XZIg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=iicMTLOeKjbpj78gfqHlCpm60lSZcZObEEzXfZGTaeI=; b=keBIjAz4hYWmbuS8BAfG7YZ1OKSmQkVC663645Z990B5pZYY49Qoar+YlWdxWXmIfI 8TmIpfE3C+RiU7coQV+iSr9xrgno0/oVY3kxlyPZerdBGyznGxozBIqXgfp788FoXTti ez/PAR4Sz0FbSiAKHKzyZ2oiGAcDmA0wUw2+RqjhY3fPVK+3k8gUCBWA0DZAICvhynM+ jVS7aSDWhCmNlMcDkKsgDhOXqqA91BCNG+KgoIzrJecZVWGl9HTGYyOKPfkgfiFTgiiM I704IY0H2DXXvx7JCJZUq6A86Sc69jAbLOkCQz9elQEXPPqpauM0WN2FL/pB6f8tDuGm Li6g==
X-Gm-Message-State: AJaThX7jSxuxIEHvwgmCwYIwsQUMoy4U4ZqrMMxqCg5QSRbwtqvNJz2R MLnSxLXrZCb5ow03rPFu0tHsM89khgE=
X-Google-Smtp-Source: AGs4zMaTwVS87OgHhKCJ52v+6C3tWiUqxfYKJ7+mYl05y0DXMYLZjWSt1BqeXrwmNsmMmZAWHY2UcA==
X-Received: by 10.107.84.1 with SMTP id i1mr12074083iob.261.1511455686069; Thu, 23 Nov 2017 08:48:06 -0800 (PST)
Received: from ?IPv6:2607:f2c0:101:3:5d27:93f8:4cd8:b33c? ([2607:f2c0:101:3:5d27:93f8:4cd8:b33c]) by smtp.gmail.com with ESMTPSA id u127sm7894649ioe.28.2017.11.23.08.48.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Nov 2017 08:48:04 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
From: Joe Abley <jabley@hopcount.ca>
X-Mailer: iPad Mail (15B202)
In-Reply-To: <20171123.173640.212705919866092469.he@uninett.no>
Date: Thu, 23 Nov 2017 11:48:03 -0500
Cc: dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <984203DA-C2FA-4971-906D-CD17399698F8@hopcount.ca>
References: <20171123.121943.1115399549648860645.he@uninett.no> <34F896BC-B044-4E46-AC60-8562A8BE782F@hopcount.ca> <20171123.173640.212705919866092469.he@uninett.no>
To: Havard Eidnes <he@uninett.no>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/TvagMGeOKmW1A0WDS3JYkNsKGnI>
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 16:48:10 -0000

Hi Håvard,

On Nov 23, 2017, at 11:36, Havard Eidnes <he@uninett.no> wrote:

>>> 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?
>> 
>> I think the only in-protocol use of the MNAME field is to
>> specify the name to which UPDATE messages are sent.
> 
> Really?  I read the NOTIFY RFC (1996) so that if the MNAME name
> server is included in the NS set, it will by default be excluded
> from receiving NOTIFY messages from the other name servers when
> they reload the zone, ref. the definition of "Notify set" in RFC
> 1996.

Oh, good catch! I did not even know that text was there. I stand corrected!

That doesn't change the wider opinion I was trying to describe, though: in the modern/transfer graph scenario I was painting, NOTIFY configuration is far more nuanced than as described in RFC1996 and in practice (in BIND parlance) is an automatically-managed set of also-notify configuration.


Joe

v2.23.0 | Report a Bug | By Email