Skip to main content

Early Review of draft-ietf-dnssd-mdns-dns-interop-04
review-ietf-dnssd-mdns-dns-interop-04-iotdir-early-robles-2017-03-14-00

Request Review of draft-ietf-dnssd-mdns-dns-interop-04
Requested revision 04 (document currently at 04)
Type Early Review
Team Internet of Things Directorate (iotdir)
Deadline 2017-03-15
Requested 2017-02-28
Requested by Terry Manderson
Authors Andrew Sullivan
Draft last updated 2017-03-14
Completed reviews Intdir Early review of -04 by Bernie Volz
Iotdir Early review of -04 by Ines Robles
Opsdir Early review of -04 by Jürgen Schönwälder
Genart Last Call review of -04 by Robert Sparks
Secdir Last Call review of -04 by Sean Turner
Artart Telechat review of -04 by Eliot Lear
Comments
I would like this document reviewed for;

Internet area: focus on impacts related to internet technologies

IoT Directorate: Look for and highlight any issues that might be raised for IoT devices in this interop,

Ops: Are there any DNS operational implications to Label interop that should be raised.
Assignment Reviewer Ines Robles
State Completed
Review review-ietf-dnssd-mdns-dns-interop-04-iotdir-early-robles-2017-03-14
Reviewed revision 04
Result Ready
Completed 2017-03-14
review-ietf-dnssd-mdns-dns-interop-04-iotdir-early-robles-2017-03-14-00
Hi,

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 (unique_id.object_identifier.OID.domain_name).

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

Cheers,

Ines.

[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 [5]
https://tools.ietf.org/html/draft-aggarwal-dnssd-optimize-query-00 [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