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

Tim Chown <> Wed, 15 March 2017 10:32 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BB0AE129A9F; Wed, 15 Mar 2017 03:32:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id roeHxj5Ex1Cs; Wed, 15 Mar 2017 03:32:22 -0700 (PDT)
Received: from ( [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D1F44129AAA; Wed, 15 Mar 2017 03:32:21 -0700 (PDT)
Received: from (localhost []) by (8.13.8/8.13.8) with ESMTP id v2FAWGBN024369; Wed, 15 Mar 2017 10:32:16 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 v2FAWGBN024369
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple;; s=201304; t=1489573937; bh=22tYXeBBj4WhjWt778H1NPIDgEY=; h=From:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References; b=ARbIlG6+NnbTaXErwuFV/STMNrnSaJyMwsBVmf5cIw4Od+SdF12AXgEPLD7UlPpwP QyXasVr3GOAFgHVThpsCCygK/1mfarqo2EG5HU8djnedScwX9KfEUYFUdYX0EHJWSm L5bv5RxCcw7dxBQF52w7K4F/zPOcoIKc1pc2uAK0=
Received: from ([2001:630:d0:f102:250:56ff:fea0:401]) by ( [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <> with ESMTP (valid=N/A) id y2EAWG1640403462z3 ret-id none; Wed, 15 Mar 2017 10:32:16 +0000
Received: from [] ( []) (authenticated bits=0) by (8.13.8/8.13.8) with ESMTP id v2FAWB4D002316 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Mar 2017 10:32:11 GMT
From: Tim Chown <>
Message-ID: <EMEW3|3d7f89a896697bb5f0f1b013499e85eey2EAWG03tjc||>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A8FB0ECA-1BD9-4521-9700-E6CFD83556CA"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Wed, 15 Mar 2017 10:32:11 +0000
In-Reply-To: <>
To: Ines Robles <>, Ralph Droms <>
References: <> <>
X-Mailer: Apple Mail (2.3259)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=y2EAWG164040346200; tid=y2EAWG1640403462z3; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=6:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v2FAWGBN024369
Archived-At: <>
Subject: Re: [dnssd] Review of draft-ietf-dnssd-mdns-dns-interop-04
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 15 Mar 2017 10:32:25 -0000

Hi Ines,

Many thanks for this review.

As you’ve implictly noted, the focus of draft-ietf-dnssd-mdns-dns-interop-04 is interoperability of the labels used, primarily between unicast and multicast DNS.

You raise some very good points about the efficiency of mDNS/DNS-SD, particularly in constrained environments. This isn’t something we’ve covered in any detail as yet in the dnssd WG, aside from draft-aggarwal-dnssd-optimize-query-00 being presented a few IETFs ago, but DNS-SD in mesh networks is in our charter ( <>). To date we’ve focused on enterprise and home networks as managed and unmanaged multi-link IP environments. 

It would be useful to explore potential issues with DNS-SD in constrained environments further. Is there someone who might be at Chicago and able to raise this issue in our meeting, briefly?  We could make some time for this topic. That might then help seed further work.

Tim (dnssd co-chair)

> On 14 Mar 2017, at 19:09, Ines Robles <> wrote:
> Reviewer: Ines Robles
> Review result: Ready
> 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]
> [2]
> [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]
> [5]
> [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]