Re: [dnssd] Setting device friendly names

Ted Lemon <mellon@fugue.com> Wed, 20 July 2016 13:32 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CB2212D626 for <dnssd@ietfa.amsl.com>; Wed, 20 Jul 2016 06:32:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-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 owKXiBumsugg for <dnssd@ietfa.amsl.com>; Wed, 20 Jul 2016 06:32:09 -0700 (PDT)
Received: from mail-lf0-x231.google.com (mail-lf0-x231.google.com [IPv6:2a00:1450:4010:c07::231]) (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 1571D12D643 for <dnssd@ietf.org>; Wed, 20 Jul 2016 06:32:09 -0700 (PDT)
Received: by mail-lf0-x231.google.com with SMTP id f93so38419953lfi.2 for <dnssd@ietf.org>; Wed, 20 Jul 2016 06:32:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=JSvrLmaqFS0ItnPPYxYdZfOGQsQkzUm+YtsA0pgBo68=; b=V7sU0JogwaahwpljtoNgoU2JM9lbHxdek5yLJQ0e3uiQyLdwe1WQIkEIyfbcjW1SLc L3jujRNq/fcwgF6EBJ9ejqqyb1/ohuVV7dMXatO8AaHiVeU8x+LfQHv/pghCvec2TX91 lSh4sIU+OvUfNUfcvadROvMnhoZUi2iTai6PPAH4fmdNBHeB2Q3mi5ZXoemKqo1iqTey iAVY8NT5jXHqlkMBa9xuKZfxOBs1xWH+9RoDjBXuMZMzCG6ai3ueW7CtqdXSIUSMc0LV lNDoHkhuLzZ9k/y+/3WiybDwsP+I/CpjOxLHrcDCHJWIlN92DTupAnun8kWWWjGIiaGD D/kg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=JSvrLmaqFS0ItnPPYxYdZfOGQsQkzUm+YtsA0pgBo68=; b=XOTM4HAWuDIFJwx6GSs+fc5ow8BFUiXPBm0iy/Z3QYG4cPCIaPUQ0Erlfw/eDgThBB gec+eCdOfqOIxg+7qoZ6Z2oXm58JYJbPjwWNFpenw+j8pwEJmTjXrSwIyq4yyu788oQm GIG/OIVo6NqJ2Lv4nMxyfBacP0+8HANPPuPwLnn1XHzXW1MUCkjPal/XJkBfg5MbPKC6 Vt9FM9tEyl0YzYtyiKaoIqsT6hKsc5Mbw35StrNEfKINCm6OxjB9hqqfMagqXbl114br 7RuQ9Yn/Sh9uYDGC5eKiUGKSIUK6rYN7phm1wC7SVLrMwlu5/MkgFPmIZoPWtd7ZTF7l sUYA==
X-Gm-Message-State: ALyK8tJMv12cL+cMZ3Wbob0Ki9WQ7HgPLVSyQHwcbpQrryXYeZyUZYBUZMPWoq6CyuicwndT9/fVeK0Juzbw1w==
X-Received: by 10.25.159.10 with SMTP id i10mr9679173lfe.131.1469021527248; Wed, 20 Jul 2016 06:32:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.219 with HTTP; Wed, 20 Jul 2016 06:31:27 -0700 (PDT)
In-Reply-To: <2040EE15-81F8-47EB-BF8D-DA544564C304@att.com>
References: <2040EE15-81F8-47EB-BF8D-DA544564C304@att.com>
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 20 Jul 2016 15:31:27 +0200
Message-ID: <CAPt1N1mxx=gPY_RtXaDVBXiT750Aq=YiyiOD4mj+CEh0MCT5qw@mail.gmail.com>
To: "STARK, BARBARA H" <bs7652@att.com>
Content-Type: multipart/alternative; boundary="001a11411c424caacd0538113a4e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/oEdhe2R5hNmY6vCBjgYir_XrjWs>
Cc: "dnssd@ietf.org" <dnssd@ietf.org>
Subject: Re: [dnssd] Setting device friendly names
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnssd/>
List-Post: <mailto:dnssd@ietf.org>
List-Help: <mailto:dnssd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnssd>, <mailto:dnssd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jul 2016 13:32:11 -0000

Can you talk more about this UPnP thing?   Bear in mind that UPnP is not a
standard, AFAIK, although its follow-on, PCP, is.   I don't know that PCP
has this feature.

The fact that some devices have UIs that users may or may not be able to
find does not mean that there needn't be a standard way to do it.   Maybe
we don't need it, but if we don't, that's not the reason.

On Wed, Jul 20, 2016 at 3:22 PM, STARK, BARBARA H <bs7652@att.com> wrote:

> In my experience, many devices already support mechanisms for friendly
> name acquisition. Many devices, including PCs, ask for names during setup.
> Others support UPnP friendly name service. Others have UIs to allow naming.
> What I really want (as a user) is for the device to have the same name in
> all contexts. So if it's been named, through whatever means, use that name.
> Which to me says we don't need a new standard for remote naming that all
> devices must support.
> Barbara
> _______________________________________________
> dnssd mailing list
> dnssd@ietf.org
> https://www.ietf.org/mailman/listinfo/dnssd
>