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

"Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com> Wed, 19 November 2014 02:49 UTC

Return-Path: <jaehoon.paul@gmail.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 562EC1ACF0E for <dnssd@ietfa.amsl.com>; Tue, 18 Nov 2014 18:49:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 XJgL2BCKAP-6 for <dnssd@ietfa.amsl.com>; Tue, 18 Nov 2014 18:49:54 -0800 (PST)
Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DF801A8A78 for <dnssd@ietf.org>; Tue, 18 Nov 2014 18:49:54 -0800 (PST)
Received: by mail-ig0-f177.google.com with SMTP id uq10so240299igb.4 for <dnssd@ietf.org>; Tue, 18 Nov 2014 18:49:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=tPOHuAcfm2SRACojhWg1BdJ+o6olq7hl8d0IDpPPHIc=; b=uQw0FBlh58D7M/OuwRUUWEbkZ7i6TJr8GuwpuhlQnftxXRKnAFCRpJ1wE4xnI/w7+1 AeJHQ7PMv+8vScYygOp8ZoEhl91WGzlUJsGphk8vYHg60SPfXNua8bTe/MYo6MG77pJk ZSvfbVrydVVbN35gRCMHCcTCbXqHNn0NaRF21k8l/HVj5+rzHl4YkAu+aKT50qB1z9/O BIlbZGYNmUp4W2nSambtWS4lC09Sv2p8JfcAnuxdPZbl+yoFVvGRETnZ6LxXA7KhgZNi 6043P86oPd2sfTjAUBFUw/jM4dIbtQ9+T1UbYvZEOQWM7nbmegBVHxJTSNiRZm8MZzNQ R7Zg==
MIME-Version: 1.0
X-Received: by 10.51.16.37 with SMTP id ft5mr852081igd.6.1416365393248; Tue, 18 Nov 2014 18:49:53 -0800 (PST)
Received: by 10.64.62.18 with HTTP; Tue, 18 Nov 2014 18:49:53 -0800 (PST)
In-Reply-To: <F158B437-8DAB-469E-B957-745CDBB3AB41@istumbler.net>
References: <CAPK2DeyuABqSbH5dtdtScYWnE-vkmGO642xFb6FZehu-5MTaAA@mail.gmail.com> <436692B4-978D-4E62-868E-78FA8AF3F26F@nominum.com> <CAPK2Deys6VU83R0hfv_8svNKuaSBEfu_dGqnGkoN_pQ9zE_6HQ@mail.gmail.com> <F61ADDF8-6BC1-4C9E-B80A-32F3EF186E3D@istumbler.net> <CAPK2DeyCToF6MwQOpnbW=tY+uU_iEsgOS0WSe1NYpxGq6kC+3Q@mail.gmail.com> <F158B437-8DAB-469E-B957-745CDBB3AB41@istumbler.net>
Date: Wed, 19 Nov 2014 11:49:53 +0900
Message-ID: <CAPK2DexC=YH_pjMnHw2ubsKe-4LqWm+BM10JwR_AxRm2k9Tudg@mail.gmail.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
To: Alf Watt <alf@istumbler.net>
Content-Type: multipart/alternative; boundary=001a113602402309b705082d4483
Archived-At: http://mailarchive.ietf.org/arch/msg/dnssd/CEDPUhbeMgbHMggUElR8MkoLZkA
Cc: Brian Haberman <brian@innovationslab.net>, Myung-Ki Shin <mkshin@etri.re.kr>, "dnssd@ietf.org" <dnssd@ietf.org>, Jung-Soo Park <pjs@etri.re.kr>, Ted Lemon <Ted.Lemon@nominum.com>, Sejun Lee <prosejun14@gmail.com>
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: Wed, 19 Nov 2014 02:49:57 -0000

Alf,
Thanks for your kind survey information.

It seems that the devices mentioned above will be able to run mDNS.
My point is to allow IoT device vendors to have an alternative way for a
simple DNS naming
that is based on IPv6 stateless autoconfiguration.

For the case where only the mapping between an IoT device's DNS name and
its IPv6 is required,
mDNS seems like an overkill.

Paul


===========================
Mr. Jaehoon (Paul) Jeong, Ph.D.
Assistant Professor
Department of Software /
Department of Computer Engineering
Sungkyunkwan University
Office: +82-31-299-4957
Mobile: +82-10-4758-1765
Fax: +82-31-290-5119
Email: pauljeong@skku.edu, jaehoon.paul@gmail.com
CPS Lab Website: http://cpslab.skku.edu
Personal Homepage: http://cpslab.skku.edu/people-jaehoon-jeong.php

On Wed, Nov 19, 2014 at 3:46 AM, Alf Watt <alf@istumbler.net> wrote:

> The proposal may have merit for other reasons but in terms of resource
> usage for IoT devices it’s very instructive to look at existing products.
>
> The Phillips Hue lights are built around a 32 ARM core [1] with limited
> RAM (128kb). The Nest Protect smoke detector is also built around a similar
> 32bit ARM core from Freescale, the K60[2].
>
> Both of these are attached to a Zigbee radio, which provides sufficient
> bandwidth for DNS-SD over mDNS, as per our charter[3].
>
> Devices which need service discovery on batteries will very likely be
> using layer-2 discovery mechanisms for power consumption reasons (i.e.
> BT-LE).
>
> I have a hard time imagining that a device with much less capabilities
> than above will be a useful internet node. If it can't afford to run a
> simple discovery service then what is it doing on the network?
>
> Best,
> Alf
>
> [1]
> http://www.digchip.com/datasheets/parts/datasheet/456/STM32F217VET6.php
> "ARM-based 32-bit MCU, MB Flash/128+4KB RAM, crypto, USB OTG HS/FS,
> Ethernet, 17 TIMs, 3 ADCs, 15  comm. interfaces & camera"
> [2] *http://cache.freescale.com/files/32bit/doc/data_sheet/K60P100M100SF2V2.pdf?fpsp=1&WT_TYPE=Data%20Sheets&WT_VENDOR=FREESCALE&WT_FILE_FORMAT=pdf&WT_ASSET=Documentation
> <http://cache.freescale.com/files/32bit/doc/data_sheet/K60P100M100SF2V2.pdf?fpsp=1&WT_TYPE=Data%20Sheets&WT_VENDOR=FREESCALE&WT_FILE_FORMAT=pdf&WT_ASSET=Documentation>*
> [3] http://datatracker.ietf.org/wg/dnssd/charter/
>
> On Nov 14, 2014, at 10:34 PM, Mr. Jaehoon Paul Jeong <
> jaehoon.paul@gmail.com> wrote:
>
> Alf,
> For embedded such as printers, cameras that have power and capacity
> equivalent to smartphone,
> you are right.
>
> For low-power low-capacity devices, such as light bulb and smoke detecting
> sensor,
> I think that running server(s) seems not viable
> even though I have no exact number of target memory and cpu size
> for such low-power low-capacity IoT devices.
>
> Is there anyone else to comment on the hardware specification of such IoT
> devices?
>
> Thanks.
>
> Paul
>
> ===========================
> Mr. Jaehoon (Paul) Jeong, Ph.D.
> Assistant Professor
> Department of Software /
> Department of Computer Engineering
> Sungkyunkwan University
> Office: +82-31-299-4957
> Mobile: +82-10-4758-1765
> Fax: +82-31-290-5119
> Email: pauljeong@skku.edu, jaehoon.paul@gmail.com
> CPS Lab Website: http://cpslab.skku.edu
> Personal Homepage: http://cpslab.skku.edu/people-jaehoon-jeong.php
>
> On Fri, Nov 14, 2014 at 12:02 PM, Alf Watt <alf@istumbler.net> wrote:
>
>> I’m confused, the mDNSResponder code is very lightweight and already runs
>> on embedded devices such as printers, cameras and may other low-memory and
>> low-cpu devices.
>>
>> What is your target memory and cpu size for an IoT device? Given that
>> we’ve been using mDNS for more than a decade, the steady pace of
>> improvement in semiconductors means that even the smallest device will have
>> more than sufficient resources for mMDS.
>>
>> Best,
>> Alf
>>
>> On Nov 14, 2014, at 1:34 PM, Mr. Jaehoon Paul Jeong <
>> jaehoon.paul@gmail.com> wrote:
>>
>> The solution in RFC 6762 (Multicast DNS) section 9 is viable for regular
>> computers,
>> such as laptop, desktop, and smartphone that can afford to run mDNS
>> responder.
>> For IoT devices, such as light bulb and fire detecting sensor, that have
>> limited memory and storage,
>> mDNS seems not viable for the DNS naming for them.
>>
>>
>>
>
>