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

Normen Kowalewski <nbkowalewski@gmx.net> Mon, 08 July 2019 09:10 UTC

Return-Path: <nbkowalewski@gmx.net>
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 42F2512011C for <dnsop@ietfa.amsl.com>; Mon, 8 Jul 2019 02:10:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
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 eUIxmXHtawRM for <dnsop@ietfa.amsl.com>; Mon, 8 Jul 2019 02:10:27 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (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 69D801200E7 for <dnsop@ietf.org>; Mon, 8 Jul 2019 02:10:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1562577019; bh=3S3vD1IrQCNlha2byxlEGHM0uGfdhaJfx+bUjUBfre4=; h=X-UI-Sender-Class:Subject:From:In-Reply-To:Date:Cc:References:To; b=JYaPtimHTfA4bf4ro06Leva+bR7SAEFpaQdaE1LRUvF3IjUG1fLuR/gmLYYfHCTyf ciXwKS5v1q1c1RBsbdBMLR6BIR2XH8JiMRELUJ/dHhY74SnIFS9PU6FzgYUtC4X6n6 GV7dYI1Vl8jkqkuwR6MO6F/eYzqmRWqdDTgRbN4U=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.1.233] ([62.225.28.246]) by mail.gmx.com (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MLzFx-1i1nsE3nZR-00HsTv; Mon, 08 Jul 2019 11:05:03 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.0 \(3445.100.39\))
From: Normen Kowalewski <nbkowalewski@gmx.net>
In-Reply-To: <2355.1560275650@localhost>
Date: Mon, 8 Jul 2019 11:05:00 +0200
Cc: homenet@ietf.org, dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <8B6802F9-4260-4DD0-9F92-A19EF6F0AA7C@gmx.net>
References: <2D09D61DDFA73D4C884805CC7865E6114E1C1AFC@GAALPA1MSGUSRBF.ITServices.sbc.com> <27671.1560111738@localhost> <DM6PR15MB3531DD30E46770B1237F1ABDE3130@DM6PR15MB3531.namprd15.prod.outlook.com> <2355.1560275650@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3445.100.39)
X-Provags-ID: V03:K1:fq/S1yGoWSRSEu6oyQDiobbFA1t+RDWgfHSCUkBP1bBSNUP39y+ 8TVK/5mCYIf4doD7QUxKbVdKX4o5d9Kfu7qP1LNLriYinbf+Q0FkjmAZek9Z6/xzgAOjTcb wrrNw87iEdbKIJA5hRmMsUnJ8rs6/a9AAjnD4arEHV8ZXboQEAWqOef+sf6V+FfOxKbxXOg X7a3r0KSandttGJszOPxQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:e0khT1CJjH4=:XhhF1Z6Xn4yyo07aO5j98N CPJKro6/LIQMdtyDCDxl9iw9uswYIYgzt2AK3knaccYWO5Qz3Y5LNh7yMBLEefmyAsa//JWBz Cnomekz9zn8spVDfeeAM/P4urt1C1kN2u0U6gvBJn0jVn0Aa9mOpUQgagGNmSZv0Edy3Hc/Ss +Q3B4N+Ix6ZIiFnpR4SP3HVMD1yUdcgKRZ+L/iNc9TWyeUPGJz2OJlXwHLnNv/rAWCmsgI3a0 nJBx1GBqm2oovk/W645vGtan9ciu1efvSHRCrNY5Iid03FcDKrd8SqR42hAe1DeG3FT5XEKhv NfdFTDlo6mDU8W/k4BeOlTFP7FwUEPhrZE5VcymCW19fGtJTx0Y/XK16RnXcw+PNul5EzBn8a xtR+itQDig1ulByD/TNYTcxxFmiJiPDsKScZgREIqvZX/qSluFnaQAfe7Hu8JouBN10XgL2B2 Q8MicQKSMBFqZRWtfwzSks7P3WfzU9/J7oVMZG0liUuZP0Sla4b01rkNyKcB7A2nTKezQF2nF EnlCCo2rlKWu1ntwDpEbbQ1sT15eLpedj00Rmh3LwDSnfcomjXA8Yx3sWcYObbl4Nxz9EvF/H mBHTf2zdXKyJcv1O/Bac5KtHbPLYw/qUW5CtG6ztgofNMcBTS8JtK+SJ/pIQYBV3VvLlRr77u LJgYuzIg9/dI6TTmjSXoDUKqq/TH540fADG64MnVgHxhIWM95mqeRI7grq9AdhbMIMRishFis Pj0REK9Hp+iZt0ifpZRkjkrKynFw3Bm9RxFKMI3Ey6ZF0taX52XnNGk/G3jJk9p3A6QUj/uEJ UhWTP0ndlvRik7cCThUP4SSzmO8BsyjYEO3IT10HdTccNL+vMwZ34gniaHUGpt5b+EYdxuvw2 v5rnJCXulv6WX3ityabtx9aNE+9tPgDRlpOlna5nSaspW5oIrOhGsQqLief7+bUs+MjCjSsYf 0zt+EcehHKL+gjtax7CwcoqY2fm8+oWNpnzt+Icnmn8aujjbLGtHdvw0vpZhFjdbqbCCzGis3 V/pZXUyS8Beq/MgJ0mznWbFAHorhi6DYA3n8ZetsN50mGySsMVIe49BtDfABai/JbfncC+7e6 36yf4ihAEs+ZiNbi1V3hDMmrmKHAwJmwDaP
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/wi0A-Am4RFn8FTK9qpArOsFw2OM>
Subject: Re: [DNSOP] [homenet] Montreal homenet activities -- front-end-naming
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 08 Jul 2019 09:10:28 -0000

Hi Michael, 

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.

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

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. 

BR, 

Normen Kowalewski

> On 11. Jun 2019, at 19:54, Michael Richardson <mcr+ietf@sandelman.ca>; wrote:
> 
> 
> (context: The HOMENET WG will not meet in Montreal at IETF105)
> 
> The HOMENET front-end-naming design team will spend some unstructure time
> together.   This relates to
> https://datatracker.ietf.org/doc/draft-ietf-homenet-front-end-naming-delegation/
> 
> The exact time is to be determined as the unstructured schedule has yet to be
> determined.  Tentatively, I want to suggest an hour on Tuesday morning.
> 
> We would love to spend some time with people who design and/or operate public
> anycast DNS systems.  We want to make sure that we match any terminology that
> you use, and to learn about practical limitations that we might be unaware
> of.  This in particular relates to the questions at:
>  https://mailarchive.ietf.org/arch/msg/homenet/VcXftoB30feY9PlsPtvEV65JycM
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>;, Sandelman Software Works
> -= IPv6 IoT consulting =-
> 
> 
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop