Re: [homenet] Request for Comments on New Internet Draft for Homenet WG

["Mr. Jaehoon Paul Jeong" <[e-mail]>]

Hi Markus,
First of all, thanks for your valuable feedback.

Let me answer your questions and comments.

First, as a basic domain, link-local collision domain is assumed,
but we can extend it into multiple links (or subnets) naturally
if a router can work as a proxy for IPv6 hosts.
That is, if a host tries to autoconfigure its DNS name in a subnet and
there exists another host with the same DNS name in an adjacent subnet,
a router interconnecting these two subnets can responds to the DAD
to tell the first host the duplication of the DNS name due to the second
host.

Second, our proposed scheme can be used along with mDNS or SSDP
for IoT devices (e.g., lamp, door lock, and light sensor) whose capacity
cannot afford to run mDNS by itself in terms of memory or processor
capacity.
It those tiny IoT devices with IPv6 stack and stateless autoconfiguration
functionality,
they will be able to support the DNS name services without the intervention
of a home network administrator.

At least, Device Name Generation (in Section 5.2.1) can be used to generate
a DNS name
for home network devices or IoT devices that run mDNS or SSDP.

Third, for DNSSL, DNS suffixes announced by a router within a home network
can be restricted
to a local domain, such as homenet. Since this can be decided by a local
policy within a home network,
we can eliminate the propagation of ISP DNS suffix into a home network.

Are there any other comments or questions?

Sincerely,
Paul




===========================
Mr. Jaehoon (Paul) Jeong, Ph.D.
Assistant Professor
Department of Software /
Department of Computer Engineering
Sungkyunkwan University
Office: [phone]
Mobile: [phone]
Fax: [phone]
Email: [e-mail], [e-mail]
CPS Lab Website: http://cpslab.skku.edu
Personal Homepage: http://cpslab.skku.edu/people-jaehoon-jeong.php

On Thu, Oct 9, 2014 at 11:22 PM, Markus Stenberg <[e-mail]>
wrote:

> Heya,
>
> it seems to be aiming to work only within link-local collision domain, and
> therefore it seems to be outside the work homenet WG is chartered to do.
> Perhaps dnssd is more appropriate for this work, although I am not sure
> about that either (they do more than just naming, as the focus is on
> service discovery).
>
> Also, I am not sure why you are not just using mDNS (RFC6762) or SSDP (of
> UPnP) or something else; you get service discovery AND naming with them.
>
> Finally, use of DNSSL option for this seems like a bad idea. For example,
> let’s assume my ISP gives me ’services.isp.com’ search path, and it gets
> propagated to my LAN. My devices start showing up under ..services.isp.com
> names (too) :-p
>
> Cheers,
>
> -Markus
>
> P.S. Name construction scheme is interesting.