Re: [dnssd] Setting device friendly names

Ted Lemon <mellon@fugue.com> Thu, 21 July 2016 10:53 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 0F29112DCF7 for <dnssd@ietfa.amsl.com>; Thu, 21 Jul 2016 03:53:30 -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 sQZdieKOmQRn for <dnssd@ietfa.amsl.com>; Thu, 21 Jul 2016 03:53:27 -0700 (PDT)
Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (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 67FC312DD7C for <dnssd@ietf.org>; Thu, 21 Jul 2016 03:51:51 -0700 (PDT)
Received: by mail-lf0-x22d.google.com with SMTP id b199so58382364lfe.0 for <dnssd@ietf.org>; Thu, 21 Jul 2016 03:51:51 -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:date:message-id:subject:from:to :cc; bh=n0njfVB9kE+W5rGmm/zd13Sxyu2ZCPSUw2/Qvg4Sius=; b=Ok6mrUFjssqN4jtz/5TbAlck75aP9BxMyueFDT7bxijk99Rve/WB4d+5mDw1zE9mUn nqHUuDG8Jp/y8ySE0pDIKMa8ddfAW7jhH1ITT4rzIcnFqWVzALp6O9KqhP6Dos2fRK8o xy0pgy1UT1Y2BmjhVURoG1+ehmfLGlFf/NaOqeRlZOotmgPF2EOrG2PrU/wLti1afI5L svOU4Ju9TqCLSjqA8iNDUQE/A1+5GlXvv46mG0igX3fSC9wWTWgLc4JGduIZorq5Ef7G voHmgR+0sneWK2UPNFIUjli5flfEXR73W8sOUFR4kX1Mn7mFhP5qLv5XKkXjg4ZJKQmg KznQ==
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:date :message-id:subject:from:to:cc; bh=n0njfVB9kE+W5rGmm/zd13Sxyu2ZCPSUw2/Qvg4Sius=; b=eGSZt5nqhVwlAesBGUyaRtZecQMvo7x5Z6/5z2nmNTls+SuNQzNV5/stFGL1WBNFoy 4+9IvbTYxttXWvbxfK3XS2rP2gKvad0b7ZxTrwgfnbX+pBcTEG2YxFEsrHI4aZOV/16t xKClrIVC4iwCnWgz2RHWl5u3hWqgUGkxdqSVz+8wCFPxWdu39fCEH3tdkvq1aUMbrEgL 7btN/dg5c6Fi2pLPusT38FV9aHX9tfExs+zFYTCgOwNNwXO7IPYJK2UzgCmQ/vxKZ8zP zkUEBcV+EWMCOXa8e3dkY0E0cnZLXMzxJUqnTMJdwmEvxQwbD4CzyJPhj7uB6y1Bzwct W56Q==
X-Gm-Message-State: ALyK8tKTZCu+0Pf3LgBZNMaynNS3MTVFW3oGxJHqwRygpLiGBy7cSWSgHOCjv/Ay1qwFl8dn/bwySXYUJn5plg==
MIME-Version: 1.0
X-Received: by 10.25.152.135 with SMTP id a129mr20628985lfe.226.1469098309475; Thu, 21 Jul 2016 03:51:49 -0700 (PDT)
Received: by 10.25.217.93 with HTTP; Thu, 21 Jul 2016 03:51:49 -0700 (PDT)
Received: by 10.25.217.93 with HTTP; Thu, 21 Jul 2016 03:51:49 -0700 (PDT)
In-Reply-To: <B18D9771-8828-42D6-8F89-AC000531C85F@apple.com>
References: <2040EE15-81F8-47EB-BF8D-DA544564C304@att.com> <CAPt1N1mxx=gPY_RtXaDVBXiT750Aq=YiyiOD4mj+CEh0MCT5qw@mail.gmail.com> <AD1ED147-37F0-4276-BC3B-E70072F97EBD@att.com> <B18D9771-8828-42D6-8F89-AC000531C85F@apple.com>
Date: Thu, 21 Jul 2016 12:51:49 +0200
Message-ID: <CAPt1N1nPkM2XBi5EapzP7RQmOYNwTWmRuSuD1Y3=JWXmTQcu7w@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
To: Stuart Cheshire <cheshire@apple.com>
Content-Type: multipart/alternative; boundary="001a114035e2e074d10538231ad5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/mRcMHXACqAW7qO8qRhSvqIUxwxE>
Cc: dnssd@ietf.org, "STARK, BARBARA H" <bs7652@att.com>
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: Thu, 21 Jul 2016 10:53:30 -0000

I think the point Barbara is making about consistency is right, and that we
may be in violent agreement. :)

In general there are devices that you'd like to be able to configure using
the network, and devices that you definitely do not want configured by the
network.

On Jul 21, 2016 12:31, "Stuart Cheshire" <cheshire@apple.com> wrote:

> On 21 Jul 2016, at 02:54, STARK, BARBARA H <bs7652@att.com> wrote:
>
> > UPnP SSDP announcements include a friendly name in the SSDP header. To
> me, this is comparable to the instance name in DNS-SD / mDNS. And
> comparable to a NetBIOS name.
>
> Yes. I don’t know any service discovery protocol that *doesn’t* have
> “friendly names”.
>
> The question was about a ubiquitous protocol for *setting* the “friendly
> name” that’s universally supported on (virtually) all devices.
>
> > When I ask my router for a list of hosts on the network, and when I ask
> my BluRay player to show me a list of content sources (UPnP), the lists use
> the same names for devices (because these devices use the same name across
> protocols).
>
> If one computer shares two USB printers on the network, do both shared
> printers have to appear with the same name (the same as the name of the
> computer that’s sharing them)? Restricting services to
> one-instance-per-host is quite limiting.
>
> <https://tools.ietf.org/html/rfc6760#section-3.3> Address Services, Not
> Hardware
>
> > Yes, there is also a UPnP Service defined that allows for remotely
> changing the friendly name.
> https://openconnectivity.org/upnp/specifications/friendlyinfoupdate1. But
> this service was only published in 2014 (long, long after the UPnP Device
> Architecture required "friendly name" in SSDP advertisements), it is not
> widely implemented (not mandatory to implement)
>
> Do you personally own *any* device that supports this? I know the
> “standard” exists. My question was how many products actually implement it.
> The world is full of so-called “official standards” that no real-world
> products implement.
>
> > FWIW, UPnP is an ISO/IEC standard.
>
>
> Yes, a great example: OSI networking.
>
> Stuart Cheshire
>
>