IETF Logo Mail Archive

Re: [dnssd] Setting device friendly names

Alf Watt <alf@istumbler.net> Thu, 21 July 2016 13:10 UTC

Return-Path: <alf@istumbler.net>
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 8391012DA8F for <dnssd@ietfa.amsl.com>; Thu, 21 Jul 2016 06:10:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.618
X-Spam-Level:
X-Spam-Status: No, score=-2.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
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 g8DbAw6QYn0w for <dnssd@ietfa.amsl.com>; Thu, 21 Jul 2016 06:10:51 -0700 (PDT)
Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4E7D12D187 for <dnssd@ietf.org>; Thu, 21 Jul 2016 06:10:48 -0700 (PDT)
Received: from [10.9.9.212] (helo=mailfront12.runbox.com) by bars.runbox.com with esmtp (Exim 4.71) (envelope-from <alf@istumbler.net>) id 1bQDkS-0001Mt-H3; Thu, 21 Jul 2016 15:10:44 +0200
Received: from c-24-5-43-153.hsd1.ca.comcast.net ([24.5.43.153] helo=[192.168.29.206]) by mailfront12.runbox.com with esmtpsa (uid:871115 ) (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.82) id 1bQDkE-0001Ue-Fh; Thu, 21 Jul 2016 15:10:30 +0200
Content-Type: multipart/alternative; boundary="Apple-Mail-1E502186-E026-42EE-93C1-5151729BFC30"
Mime-Version: 1.0 (1.0)
From: Alf Watt <alf@istumbler.net>
X-Mailer: iPhone Mail (13G34)
In-Reply-To: <CAPt1N1nPkM2XBi5EapzP7RQmOYNwTWmRuSuD1Y3=JWXmTQcu7w@mail.gmail.com>
Date: Thu, 21 Jul 2016 06:10:27 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <E31A479B-02C8-46E0-B507-527C365EB2C1@istumbler.net>
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> <CAPt1N1nPkM2XBi5EapzP7RQmOYNwTWmRuSuD1Y3=JWXmTQcu7w@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/YI4F7x8m9KGvz09KWayGB5XZBao>
Cc: Stuart Cheshire <cheshire@apple.com>, 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 13:10:55 -0000

Don't forget, good ol DHCPv4 provides option 12 for setting host names by the server: 

https://tools.ietf.org/html/rfc2132

Support will depend on the client respecting the option, which at least some Linux distributions don't seem to out of the box.

The option wasn't included (even for the more common case of the client requesting a name from the server) in DHCPv6, which suggests using DDNS for allowing the host to update the name after auto-configuration. 

http://www.ietf.org/rfc/rfc3315.txt

Best,
Alf

> On Jul 21, 2016, at 3:51 AM, Ted Lemon <mellon@fugue.com> wrote:
> 
> 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
> _______________________________________________
> dnssd mailing list
> dnssd@ietf.org
> https://www.ietf.org/mailman/listinfo/dnssd

v2.23.0 | Report a Bug | By Email