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

"Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com> Sat, 15 November 2014 06:34 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 828771A1A75 for <dnssd@ietfa.amsl.com>; Fri, 14 Nov 2014 22:34:54 -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 b7pG5hB9rq7R for <dnssd@ietfa.amsl.com>; Fri, 14 Nov 2014 22:34:52 -0800 (PST)
Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12EB31A1A5B for <dnssd@ietf.org>; Fri, 14 Nov 2014 22:34:52 -0800 (PST)
Received: by mail-ie0-f169.google.com with SMTP id y20so2417910ier.14 for <dnssd@ietf.org>; Fri, 14 Nov 2014 22:34:51 -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=g/YoEG1OXNH9zy1XlMz0qfetjKkjkgdCC+5hKquRN/I=; b=A1xbvdKEpiz7KX+TIReCIOmrJwDscqE4OhWZ89IgTTXCygvmAxsPg9OAcGMlcoK8k0 OZZJ6sm36oOG3NEytDl/eqEL2x1naGIvBS4wWOrpV+fbpoLkDZajZo7Rm2y0piehyBVT d08ADyS9zK6Do5ZNiHUd9P6j2CdmNI6+xTafLGT6/+tXwFA+TRhod4pFZT6Vas8goPRE fV9ojfcy7MHLdcMz/iDhdcxMpNqXsAUWY4LMCphXWdc+BUUhlS2ZiW+v2M/PCwEAgyOq 36IBWnPPVK9RO7FvCpH9BkfD1oRvOoWNBWoD/3vfmx2tpNJ2c+nZg1lVPCN19/j317WA OUNg==
MIME-Version: 1.0
X-Received: by 10.42.24.10 with SMTP id u10mr15475948icb.58.1416033291292; Fri, 14 Nov 2014 22:34:51 -0800 (PST)
Received: by 10.64.62.18 with HTTP; Fri, 14 Nov 2014 22:34:51 -0800 (PST)
In-Reply-To: <F61ADDF8-6BC1-4C9E-B80A-32F3EF186E3D@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>
Date: Fri, 14 Nov 2014 20:34:51 -1000
Message-ID: <CAPK2DeyCToF6MwQOpnbW=tY+uU_iEsgOS0WSe1NYpxGq6kC+3Q@mail.gmail.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
To: Alf Watt <alf@istumbler.net>
Content-Type: multipart/alternative; boundary=20cf3040e54a5156c50507dff1b6
Archived-At: http://mailarchive.ietf.org/arch/msg/dnssd/nXVKzzxg1AWYMSH4_HGAbkgoV5s
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: Sat, 15 Nov 2014 06:34:54 -0000

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.
>
>
>