IETF Logo Mail Archive

Re: [dnssd] Setting device friendly names

"STARK, BARBARA H" <bs7652@att.com> Thu, 21 July 2016 13:22 UTC

Return-Path: <bs7652@att.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 4EBC912D616 for <dnssd@ietfa.amsl.com>; Thu, 21 Jul 2016 06:22:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level:
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-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 Evld2-ZqwEyv for <dnssd@ietfa.amsl.com>; Thu, 21 Jul 2016 06:22:30 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4EC212D60B for <dnssd@ietf.org>; Thu, 21 Jul 2016 06:22:30 -0700 (PDT)
Received: from pps.filterd (m0049287.ppops.net [127.0.0.1]) by m0049287.ppops.net-00191d01. (8.16.0.11/8.16.0.11) with SMTP id u6LDDlAw006536; Thu, 21 Jul 2016 09:22:29 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049287.ppops.net-00191d01. with ESMTP id 24axxv8h3h-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 21 Jul 2016 09:22:29 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u6LDMRJu019640; Thu, 21 Jul 2016 09:22:28 -0400
Received: from alpi133.aldc.att.com (alpi133.aldc.att.com [130.8.217.3]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id u6LDMIb9019529 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 21 Jul 2016 09:22:19 -0400
Received: from GAALPA1MSGHUBAE.ITServices.sbc.com (GAALPA1MSGHUBAE.itservices.sbc.com [130.8.218.154]) by alpi133.aldc.att.com (RSA Interceptor); Thu, 21 Jul 2016 13:22:07 GMT
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.74]) by GAALPA1MSGHUBAE.ITServices.sbc.com ([130.8.218.154]) with mapi id 14.03.0294.000; Thu, 21 Jul 2016 09:22:06 -0400
From: "STARK, BARBARA H" <bs7652@att.com>
To: Ted Lemon <mellon@fugue.com>
Thread-Topic: [dnssd] Setting device friendly names
Thread-Index: AdHiibYrxB4vZWkMQdmCvDMGAtoHugAItUmAACJTDvIACarMAAAAuYWA///m7rQ=
Date: Thu, 21 Jul 2016 13:22:05 +0000
Message-ID: <8F6598B8-BBE0-4496-B850-51686E63A527@att.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>, <CAPt1N1nPkM2XBi5EapzP7RQmOYNwTWmRuSuD1Y3=JWXmTQcu7w@mail.gmail.com>
In-Reply-To: <CAPt1N1nPkM2XBi5EapzP7RQmOYNwTWmRuSuD1Y3=JWXmTQcu7w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_8F6598B8BBE04496B85051686E63A527attcom_"
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2016-07-21_05:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1604210000 definitions=main-1607210148
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/kYP1FazNq_CQ0ddBXWN0gXnEJPc>
Cc: Stuart Cheshire <cheshire@apple.com>, "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: Thu, 21 Jul 2016 13:22:32 -0000

+1
Thx. You said that so much better than I did. :)
And even where network configuration is desirable, a one-size-fits all ubiquitous solution is  not the right answer. We should not design an architecture with such a dependency.
Barbara

On Jul 21, 2016, at 12:51 PM, Ted Lemon <mellon@fugue.com<mailto: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<mailto:cheshire@apple.com>> wrote:
On 21 Jul 2016, at 02:54, STARK, BARBARA H <bs7652@att.com<mailto: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

v2.23.0 | Report a Bug | By Email