IETF Logo Mail Archive

Re: [dnssd] DNS Name Autoconfiguration for Home Network Devices

Stuart Cheshire <cheshire@apple.com> Tue, 18 November 2014 22:46 UTC

Return-Path: <cheshire@apple.com>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DD391AC3C9 for <dnssd@ietfa.amsl.com>; Tue, 18 Nov 2014 14:46:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.685
X-Spam-Level:
X-Spam-Status: No, score=-104.685 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 41DljH7XWuad for <dnssd@ietfa.amsl.com>; Tue, 18 Nov 2014 14:46:54 -0800 (PST)
Received: from mail-in2.apple.com (mail-out2.apple.com [17.151.62.25]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A1801AC3BE for <dnssd@ietf.org>; Tue, 18 Nov 2014 14:46:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple; q=dns/txt; i=@apple.com; t=1416350813; x=2280264413; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-transfer-encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=3auKvwM+7HxZavaeS4HTHuCrqUXAOqjVn+NhCvMuHig=; b=LYoFI+i5gnLPutwVgr3sXNB0zhDrSJFADnxCSwcxOW8+JvUOTmhWLvirv0t791BN +qStmvNFY++26SMQBBtv0WppctGzSZ0gWi+Q0OjjEmDpu9tGjapk5uk1TNdjSakh gvxYXaXb576+nC1fuqs0kqyL60FJVnKd3Whm7DUl4IR9pkm9T8pH+eH3NrgrF+PQ ETTzSHACq5MGZfJf0QgcFPrYaxnBmQbDUn0XdfkycKi8pZoIeVDVT1b+lFG6ppmA YQE57sHn3wkMeNAYGrbKlui4qmU6x7Do8leX2zV9TJaBuD7x0WdJaK5LG1wnM4CN RPnqK4/7mzF1/8jgFxk1eQ==;
Received: from relay3.apple.com (relay3.apple.com [17.128.113.83]) by mail-in2.apple.com (Apple Secure Mail Relay) with SMTP id D7.34.18976.C5CCB645; Tue, 18 Nov 2014 14:46:52 -0800 (PST)
X-AuditID: 11973e11-f79a66d000004a20-1d-546bcc5c8dae
Received: from spicerack.apple.com (spicerack.apple.com [17.128.115.40]) (using TLS with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate) by relay3.apple.com (Apple SCV relay) with SMTP id EF.6D.05439.26CCB645; Tue, 18 Nov 2014 14:46:58 -0800 (PST)
Received: from chesh1.apple.com (chesh1.apple.com [17.193.13.41]) by spicerack.apple.com (Oracle Communications Messaging Server 7.0.5.30.0 64bit (built Oct 22 2013)) with ESMTPSA id <0NF900EYXBA4D540@spicerack.apple.com> for dnssd@ietf.org; Tue, 18 Nov 2014 14:46:52 -0800 (PST)
Content-type: text/plain; charset="windows-1252"
MIME-version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Stuart Cheshire <cheshire@apple.com>
In-reply-to: <CAPK2Dew8BOUOG-bZ-_EcTtxuz6m_NeAUj70i8jzXc4RC-zTFFA@mail.gmail.com>
Date: Tue, 18 Nov 2014 14:46:49 -0800
Content-transfer-encoding: quoted-printable
Message-id: <26B22159-3630-493B-AAA0-BC2DEA9DBA7F@apple.com>
References: <CAPK2DeyuABqSbH5dtdtScYWnE-vkmGO642xFb6FZehu-5MTaAA@mail.gmail.com> <436692B4-978D-4E62-868E-78FA8AF3F26F@nominum.com> <CAPK2Deys6VU83R0hfv_8svNKuaSBEfu_dGqnGkoN_pQ9zE_6HQ@mail.gmail.com> <cc9f90afaa7a48bdaf7a8906546571b5@BY2PR03MB412.namprd03.prod.outlook.com> <CAPK2Dex=hR5HE-BFtvbMzgadfcu-4CPgP8zd1sziNPCQNJ+aCw@mail.gmail.com> <D08FC56A.3C9AF%Robby.Simpson@GE.com> <42C3C87F-0D99-47CB-B50A-9107BD10A2E6@bangj.com> <CAPK2Dew8BOUOG-bZ-_EcTtxuz6m_NeAUj70i8jzXc4RC-zTFFA@mail.gmail.com>
To: "dnssd@ietf.org" <dnssd@ietf.org>
X-Mailer: Apple Mail (2.1510)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrELMWRmVeSWpSXmKPExsUi2FAYrBtzJjvEYMdlG4v3S2cxOjB6LFny kymAMYrLJiU1J7MstUjfLoEr4+vDaewFnzkrWnf9Z21g/MTexcjBISFgInH0VlAXIyeQKSZx 4d56ti5GLg4hgb2MEt8OnmaFqXl9XBgiPplJ4umceYwQznwmidVfLzGDFDEL6Encv6gFMogX yNy5dxsriC0s4CGxvPkHC4jNJqAl8eLzFTYQm1MgWGL27zdgN7AIqErMX2YBEmYW0JZ48u4C K8QYG4mpKxcxgthCAs0sElu3gtWIAJX3zjnFBHGzrMTpc89ZQM6REHjKKvHs5zPGCYxCsxAu moXkollIVixgZF7FKJSbmJmjm5lnpJdYUJCTqpecn7uJERSo0+0EdzAeX2V1iFGAg1GJhzdh alaIEGtiWXFl7iFGaQ4WJXHeT0VAIYH0xJLU7NTUgtSi+KLSnNTiQ4xMHJxSDYxJUatYPFOz NGOvra+/5FWz6/J2o/KgC9vurp8/49BpnlqLlJnNIYV1UWzpLtIKBxZX3yt3vJSqLGb+o/Tw jPbfQvvcnn+LmXaIh0lYxHNf9YPWe9Nj93BOeH306hrea0c8b+ww9Xl8X7HvQveHmK/zmfc2 N24/y7SD/fDrW/ofTWUbptumBZ1RYinOSDTUYi4qTgQAyBIFLjUCAAA=
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprGLMWRmVeSWpSXmKPExsUi2FCsoZt0JjvE4Mk0YYv3S2cxOjB6LFny kymAMYrLJiU1J7MstUjfLoEr4+vDaewFnzkrWnf9Z21g/MTexcjBISFgIvH6uHAXIyeQKSZx 4d56ti5GLg4hgclMEk/nzGOEcOYzSaz+eokZpIFZQE/i/kUtkAZeIHPn3m2sILawgIfE8uYf LCA2m4CWxIvPV9hAbE6BYInZv9+A7WIRUJWYv8wCJMwsoC3x5N0FVogxNhJTVy5iBLGFBJpZ JLZuBasRASrvnXOKCeI2WYnT556zTGDkn4VwxCwkR8xCMnUBI/MqRoGi1JzESmO9xIKCnFS9 5PzcTYzg0CoM3sH4Z5nVIUYBDkYlHt6EqVkhQqyJZcWVuYcYJTiYlUR4BbuzQ4R4UxIrq1KL 8uOLSnNSiw8xSnOwKInzKgLDWUggPbEkNTs1tSC1CCbLxMEp1cDIetZLqKjV3XLZjA9SARsk k1va+91OtnfztuqUbIyZvH4Jj7Fp6isB/webOIOTe14cSz/7rbVDsfnd/P8NokcnlHQqhMv0 rb/ySdXXPGpBTHvDJvtPbr9avKb9fZvs9eZ8hAnLhAWnq2sC9ud/+rXgEJ+1Zqu+eYrf7biv C2dcmcx+913Px5NKLMUZiYZazEXFiQCFvyLPKQIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/dnssd/4bFvTbmAfGXS2NkJL4e6bypY59U
Subject: Re: [dnssd] DNS Name Autoconfiguration for Home Network Devices
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of extensions to Bonjour \(mDNS and DNS-SD\) for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 18 Nov 2014 22:46:56 -0000

On 17 Nov, 2014, at 17:33, Mr. Jaehoon Paul Jeong <jaehoon.paul@gmail.com> wrote:

> Hi Tom,
> 
> You are right for appliances with enough capacity to run mDNS.
> 
> However, for low capacity IoT devices without mDNS, my proposal will be able to support an alternative way for DNS naming.

You assert that there are devices with insufficient resources to run DNS-SD/mDNS.

You assert that these devices would have sufficient resources to run your alternative.

I think you need data to substantiate these claims. Note that devices like the SitePlayer Telnet implement DNS-SD/mDNS in under one kilobyte (about 850 bytes of code, if I remember correctly): <http://netmedia.com/siteplayer/telnet/>

So you need to demonstrate that:

1. That there are devices where 850 bytes of code is too much.

2. That these devices can implement your thing in under 850 bytes.

3. That your thing is useful. I’m still unclear on what your thing is useful for. Your proposal says how devices pick host names, but not how users find out what those host names are, or find out what those devices do, or what protocol to use to communicate with them, and how clients resolve those host names to addresses.

Stuart Cheshire

v2.23.0 | Report a Bug | By Email