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

"Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com> Sat, 15 November 2014 17:47 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 23AD61AC417 for <dnssd@ietfa.amsl.com>; Sat, 15 Nov 2014 09:47:45 -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 cjrwCCJiIQ5W for <dnssd@ietfa.amsl.com>; Sat, 15 Nov 2014 09:47:43 -0800 (PST)
Received: from mail-ie0-x22c.google.com (mail-ie0-x22c.google.com [IPv6:2607:f8b0:4001:c03::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C71D71A1AE1 for <dnssd@ietf.org>; Sat, 15 Nov 2014 09:47:42 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id ar1so5034585iec.31 for <dnssd@ietf.org>; Sat, 15 Nov 2014 09:47:42 -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=7wWLtRlr5/1nDHxLT60dQrG98PsiEsMUYMpBXjadSCI=; b=ODpAh1ZIlAsoey7zLtQVhSW/yWF03/E0ZqaqtiU1vYXmjKrRRw8r+lWsWZkbmExdU5 n+thYTs3TdYhhUSakYeilG5u9eFG4UCDx5bFLuMsLeB8QopFtQbOATWkT2rVi/IyzQ78 sb5z/INSXQWtm0DzHxtPvVKyCTOEWjy6Fuvf1J16HYOLyl+yw6U0sxnsuOSZKJMeZyeH wggC2by9yD5OIWzUsPiA/YtEmaLD8bre71yR7TylOCB7yvH8ZHT8u8KO29ryezlClc/8 /APKakQcRjfiz+xNz7VYhG0s7tHTGDQulY2Wq3fuRWeIJPGKSDjT3QOGqc7FPrI6RD/x Zn/g==
MIME-Version: 1.0
X-Received: by 10.50.62.4 with SMTP id u4mr14428686igr.46.1416073662000; Sat, 15 Nov 2014 09:47:42 -0800 (PST)
Received: by 10.64.62.18 with HTTP; Sat, 15 Nov 2014 09:47:41 -0800 (PST)
In-Reply-To: <CAHSr+v1sXdZrFSpTLU+KVXfXExwjZu8KKA92Be8VXZZt=5DVeg@mail.gmail.com>
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> <DF1EDE9D-9867-4F10-A69C-8F4D34C4D743@nominum.com> <CAHSr+v1sXdZrFSpTLU+KVXfXExwjZu8KKA92Be8VXZZt=5DVeg@mail.gmail.com>
Date: Sat, 15 Nov 2014 07:47:41 -1000
Message-ID: <CAPK2DeyKiA+qP_xqD3OERGBn1RipnKvV0HhpStK0ccqcDQ+2ug@mail.gmail.com>
From: "Mr. Jaehoon Paul Jeong" <jaehoon.paul@gmail.com>
To: Daniel Park <soohongp@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bdca6e099a7f40507e957eb
Archived-At: http://mailarchive.ietf.org/arch/msg/dnssd/xds6GfVINW0z-5JaBnpvJDMZRhM
Cc: Brian Haberman <brian@innovationslab.net>, Myung-Ki Shin <mkshin@etri.re.kr>, "dnssd@ietf.org" <dnssd@ietf.org>, =?UTF-8?B?67CV7KCV7IiY?= <pjs@etri.re.kr>, Ted Lemon <Ted.Lemon@nominum.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 17:47:45 -0000

Daniel,
That's a good point.

One use case is IPv6 networking in smart grid networks and home area
networks
are based on IEEE 1901.2 Narrowband Powerline Communication Networks (PLC).
All IoT devices will not necessarily use only wireless communications for
LLN (low power and lossy networks),
such as IEEE 802.15.4.

Also, CoAP is indeed a useful protocol for IoT devices, but we cannot
preclude the cases
where IoT devices do not use CoAP.

Since low capacity IoT devices using IPv6 somehow are IPv6 hosts, it will
be useful
to let those IoT devices autoconfigure their unique DNS names and
tell a network managment entity (e.g., home network users or administrators)
their naming information in terms of management.

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 3:10 PM, Daniel Park <soohongp@gmail.com>; wrote:

> Before rushing this topic here, you should be clarifying why DNS-bases
> discovery is necessary for IoT lite things. As of now, CoAP is mostly
> popular in this world. It is well designed by IETF considering IoT resource
> model and simplified message exchanges...
>
> So, do you have any strong use case and requirement with DNS-based
> approach in IoT?
>
> Daniel.
>
> Soohong Daniel Park, Ph.D.
> Samsung Software R&D Center
> 2014. 11. 15. 오전 7:18에 "Ted Lemon" <Ted.Lemon@nominum.com>님이 작성:
>
>> On 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.
>>
>> The issue for lln devices is often battery capacity.
>>
>> _______________________________________________
>> dnssd mailing list
>> dnssd@ietf.org
>> https://www.ietf.org/mailman/listinfo/dnssd
>>
>