[dnssd] Review of draft-ietf-dnssd-mdns-dns-interop-04

Ines Robles <maria.ines.robles@ericsson.com> Tue, 14 March 2017 19:09 UTC

Return-Path: <maria.ines.robles@ericsson.com>
X-Original-To: dnssd@ietf.org
Delivered-To: dnssd@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C988129665; Tue, 14 Mar 2017 12:09:28 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ines Robles <maria.ines.robles@ericsson.com>
To: <Iot-dir@ietf.org>
Cc: dnssd@ietf.org, ietf@ietf.org, draft-ietf-dnssd-mdns-dns-interop.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.47.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148951856846.2289.9860804626640095928@ietfa.amsl.com>
Date: Tue, 14 Mar 2017 12:09:28 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/rjMREVwPyrnVVs5ni78R9nQ37No>
Subject: [dnssd] Review of draft-ietf-dnssd-mdns-dns-interop-04
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Tue, 14 Mar 2017 19:09:28 -0000

Reviewer: Ines Robles
Review result: Ready


I have read the draft. The document provides a description of the
requirements for a profile for label interoperation.

In IoT, networks and nodes, in general, have constrained resources.
Related to the topic of the draft in review, several aspects should be
considered from IoT point of view, such as:

- Type of devices that have insufficient resources to run DNS-SD/mDNS
[1] (Some running code [7]). The work in [2][3] depicts an
autoconfiguration scheme for the global (or local) DNS names of IoT
devices. It uses an specific DNS Name Format

- Resource Directory (RD): A web entity that stores information about
web resources and implements the REST interfaces for registration and
lookup of resources. A mapping between CoRE Link Format attributes and
DNS-Based Service Discovery aspects (mapping ins to <Instance>,
Mapping rt to <ServiceType> and Domain mapping) is descripted in
version 9 of RD draft [4]. 

- Optimization of DNS-SD: A proposal for an optimization of DNS-SD
query using TXT records is descripted in [5].

- DNS Message Compression [6], implemented in uBonjour Contiki.

Thus, new work (or updates) is needed to set the requirements for
label interoperation in this type of environments. I understand that
this is out of scope of dns-interop draft. So, what about to add in
the dns-interop draft some text like:

"Related to constrained environments, work is ongoing such as
autoconfiguration[2], optimization of DNS-SD [5] and DNS message
compression [6] that would help to get an efficient selection of
labels for DNS and other resolution systems."

Hope that it helps.



[1] https://www.ietf.org/mail-archive/web/dnssd/current/msg00589.html
[2] https://tools.ietf.org/html/draft-jeong-its-iot-dns-autoconf-01
[3] Lee, Sejun, Jaehoon Paul Jeong, and Jung-Soo Park. "DNSNA: DNS
name autoconfiguration for Internet of Things devices." Advanced
Communication Technology (ICACT), 2016 18th International Conference
on. IEEE, 2016.
[4] https://tools.ietf.org/html/draft-ietf-core-resource-directory-09
[6] Klauck, Ronny, and Michael Kirsche. "Enhanced DNS message
compression-Optimizing mDNS/DNS-SD for the use in 6LoWPANs." Pervasive
Computing and Communications Workshops (PERCOM Workshops), 2013 IEEE
International Conference on. IEEE, 2013.
[7] https://github.com/Agile-IoT/awesome-open-iot#mdns--bonjour