Re: [homenet] [DNSOP] Montreal homenet activities -- front-end-naming

Michael Richardson <> Mon, 08 July 2019 19:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 724E4120024; Mon, 8 Jul 2019 12:31:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id LcJ0pngpvTFB; Mon, 8 Jul 2019 12:31:06 -0700 (PDT)
Received: from ( [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id A5F91120019; Mon, 8 Jul 2019 12:31:06 -0700 (PDT)
Received: from (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by (Postfix) with ESMTP id B67653818C; Mon, 8 Jul 2019 15:29:03 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by (Postfix) with ESMTP id B948C264; Mon, 8 Jul 2019 15:31:04 -0400 (EDT)
From: Michael Richardson <>
To: Normen Kowalewski <>
In-Reply-To: <>
References: <> <27671.1560111738@localhost> <> <2355.1560275650@localhost> <>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Mon, 08 Jul 2019 15:31:04 -0400
Message-ID: <4167.1562614264@localhost>
Archived-At: <>
Subject: Re: [homenet] [DNSOP] Montreal homenet activities -- front-end-naming
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Homenet WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 08 Jul 2019 19:31:10 -0000

Normen Kowalewski <> wrote:
    > apologies for this really very late reply, but FAIW it's IMHO not
    > really a "Synchronization Server", because the flow is really
    > hierachical - from home via the to-be-named-entity, and then to the
    > place tha scales out, like the slaves of that entity. I think it is
    > also not really a “Distribution Server", if the collecting
    > to-be-named-entity is a fully grown-up DNS Auth by itself, in which i
    > can/do also manage zones directly.

I never liked "Synchornization Server", and we removed that term.

We settled on Distribution Master, which is usually the stealth primary, and
transfers zones to the public secondaries.

    > When I ran things in a chain like this, it saw the  to-be-named-entity
    > as acting in the capacity of a "DNS intermediary [master]", or "DNS
    > provisioning proxy".

DNS intermediary Master, conveniently could also be abbreviated to "DM" :-)

    > AFAIK already when we starting the early discussions on this (Hi
    > Daniel, Hi Ralf!) for the former expired draft, we had not found a
    > specific terminology for such a use of nn DNS Authorittive Server in a
    > draft/doc anywhere, but i still think it is worth the effort to have a
    > specific term for that.

Michael Richardson <>ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-