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

Daniel Park <soohongp@gmail.com> Sat, 15 November 2014 01:10 UTC

Return-Path: <soohongp@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 B2F181AD4B7 for <dnssd@ietfa.amsl.com>; Fri, 14 Nov 2014 17:10:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.451
X-Spam-Level:
X-Spam-Status: No, score=0.451 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, MIME_CHARSET_FARAWAY=2.45, 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 vbz4rBt4h27g for <dnssd@ietfa.amsl.com>; Fri, 14 Nov 2014 17:10:52 -0800 (PST)
Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB34E1A1A46 for <dnssd@ietf.org>; Fri, 14 Nov 2014 17:10:52 -0800 (PST)
Received: by mail-ie0-f174.google.com with SMTP id x19so19041674ier.33 for <dnssd@ietf.org>; Fri, 14 Nov 2014 17:10:52 -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=IVoEX6dbLtJE5YzVdBySY6uh/Ew61+dRt8l/2ecXT98=; b=SX76G677o329W5Iw41Q1l3IONZONFw+CcDdnqyhdqkZfvqpk6Oue+SORkPgr9kMSHy IVzbn4+LoRjI3b7ticBFA4W13psvaNpVcSj6TrNV5WO8oeawngv7Eh9wNL8PZKW+eTFq 4PdXr/L9rTJSafPtAzoW5oidXXj2bJc1khG+fymtY6FAlOpCMstH2Tk0ISkRhsGm4GTU NuJp4Et0sNGHaA15Yp9AfX/lrTFDmD0jHbY2UVOvGqXDnaK5jxSCaOZFmzPVMFjlr51U alVJJh+Dmw8vPTv6BurUZw8f/PUQqr6D9sbmQpmomAqzfuHmM2Bmt2v0EbXINiWDAYqx VGtw==
MIME-Version: 1.0
X-Received: by 10.107.29.5 with SMTP id d5mr589176iod.45.1416013851988; Fri, 14 Nov 2014 17:10:51 -0800 (PST)
Received: by 10.50.47.200 with HTTP; Fri, 14 Nov 2014 17:10:51 -0800 (PST)
Received: by 10.50.47.200 with HTTP; Fri, 14 Nov 2014 17:10:51 -0800 (PST)
In-Reply-To: <DF1EDE9D-9867-4F10-A69C-8F4D34C4D743@nominum.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>
Date: Sat, 15 Nov 2014 10:10:51 +0900
Message-ID: <CAHSr+v1sXdZrFSpTLU+KVXfXExwjZu8KKA92Be8VXZZt=5DVeg@mail.gmail.com>
From: Daniel Park <soohongp@gmail.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Content-Type: multipart/alternative; boundary=001a113fe4d2a51b450507db6a46
Archived-At: http://mailarchive.ietf.org/arch/msg/dnssd/A1z8AiXi_5s-AXtAt9hnYOPxP9s
Cc: brian@innovationslab.net, Myung-Ki Shin <mkshin@etri.re.kr>, dnssd@ietf.org, =?UTF-8?B?67CV7KCV7IiY?= <pjs@etri.re.kr>, "Mr. Jaehoon Paul Jeong" <jaehoon.paul@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 01:10:54 -0000

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
>