Re: [dnssd] Example Use Cases (was Re: Rechartering)

Ted Lemon <> Mon, 23 July 2018 16:16 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 91CBA130EF9 for <>; Mon, 23 Jul 2018 09:16:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Status: No, score=-1.91 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_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 4beUk07xvfGw for <>; Mon, 23 Jul 2018 09:16:05 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4001:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D50D3130DCB for <>; Mon, 23 Jul 2018 09:16:04 -0700 (PDT)
Received: by with SMTP id g11-v6so1001894ioq.9 for <>; Mon, 23 Jul 2018 09:16:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=PEBIdwv2Whtpk0X2PKEN3jOrZcUJRFRT/1s5J1S0qSo=; b=JsLyJob/p/a7Ojad8RapDMPJE5XRVfrxXkNjOfCX12U4OGITMgmP0G7tegQlHB8vO0 otXRSmpD2RqUzK17vTbyE2zVKNvgcFTeuuxGHEGzEZU0o66ITxpJHhAnvXT3MR7VNjMb 6hIUFTEcNGzHkPU8IHfGkf9lv4GJB9SJK6nn/2F6keiSJN9Cc+1by13i75jbKoGOj6og 30YdDLoEyEX1TPjiy1rNLkB4r6zdp/ZBH78j7EB+ZY8Dhr8bUYUWt+Gj3rpnQdOJr67z ft7X9P6N0SBdIXuZZFII7BDiSg4d5IDPD2Mi95EXqaBx9lz7vQSdVPr/4VQxG8WIQTOX CRhQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=PEBIdwv2Whtpk0X2PKEN3jOrZcUJRFRT/1s5J1S0qSo=; b=GpJTYVXkY26/L0eQ5VxufcrUlfLGV/NauXkgn0Af0CRjPJ42jlVLTw8ti+QOU1TZcM ucSWFSLSAkof9rLhdnpjXKE9BncSWfkfHKNFRXI6DZ0sinZl8NpLCrQR7junlmbxA/uQ HyV4vkXbWiSVqzSbiMB8KNlBj9yEAYKGyhxdtE1WbmB0Fc3EiZXwW7HZyT0vtisIKyc/ GuM+LKRrbw4H+kduOIH+MNPm0GCbLIR7eBvCjim/SZSWdy5zBjWMsIGdAdHZHksbvYiG 5HZS5ioWckVaLNI24hruN2VJFWnM2Kr7z9+qS7gUGkYMPmS1ivuu645CIaujfFz4WyqN 3WNA==
X-Gm-Message-State: AOUpUlE++p9iPjsAHQzxO8+Bf4Uibk9bDdZ1nSv+ZBFFC68kaQlsx+w1 LE87viyFb3BJjboVA9prEyHgVTMcbFG7sx06DDmMxg==
X-Google-Smtp-Source: AAOMgpdH1hs4kdPVvLurRir5MeZkJ4BiEHZYlqLSkGzFjinmpo07Z7gm6ZW1aojZ8CNkuZKTluS3RRFgVl8js69wkkA=
X-Received: by 2002:a6b:dd01:: with SMTP id f1-v6mr10571393ioc.45.1532362564077; Mon, 23 Jul 2018 09:16:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:b442:0:0:0:0:0 with HTTP; Mon, 23 Jul 2018 09:15:23 -0700 (PDT)
In-Reply-To: <>
References: <> <7001.1532128071@localhost> <> <> <>
From: Ted Lemon <>
Date: Mon, 23 Jul 2018 12:15:23 -0400
Message-ID: <>
To: "R. Atkinson" <>
Cc: dnssd <>
Content-Type: multipart/alternative; boundary="0000000000004c98130571acf698"
Archived-At: <>
Subject: Re: [dnssd] Example Use Cases (was Re: Rechartering)
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 23 Jul 2018 16:16:09 -0000

ISTM means "It seems to me."

I think a global-scope FQDN for the local network that includes the
corporation's domain name is quite unlikely, but it's easy to imagine that
if it were *useful*, an ISP or a third party might offer it as a service
(as with, but delegating a zone rather than just allowing a name
to be updated).  The benefit for this is simply external reachability of
services, so it may be that a better solution would just be a DoH tunnel or
VPN tunnel that you could access with the right credentials that would
allow you to query   It would be nice if this sort of thing
could be more automatic, with less user IT fu required.

On Mon, Jul 23, 2018 at 11:11 AM, R. Atkinson <> wrote:

> From what I am seeing, I think the big barrier to local server deployment
> is the knowledge required to correctly deploy a local server.  This is a
> big
> issue whether its a DNS server or some other kind of server (e.g.
> Some company could make good money by creating an IT server that
> is MUCH MUCH easier to deploy, configure, and update/maintain.

We've seen devices like this—they just aren't typical.   Your printer is
like this.   If you have an Apple Time Machine or Homekit, it's like this.
 Making devices findable in this way isn't that hard, and enrollment really
isn't that hard either.   The issue is that right now for most use cases
nobody's making devices that work this way.   I think that's the barrier to
adoption.   I don't think that the level of knowledge in the deployment
environment is going to up.   I hope that the level of knowledge required
to deploy will go down.