Subject: [dns-privacy] Seeking comments on draft-ietf-dnssd-push-05

From: Tim Chown <[email-masked]>
Date: Thu, 17 Mar 2016 23:05:34 +0000

Hi,

As part of chartered work in the dnssd WG, we are progressing a solution for scalable DNS-based service discovery. 

A requirements text has already been published as RFC 7558, and we now have a proposed hybrid proxy solution, draft-ietf-dnssd-hybrid-03, entering WGLC on the [email-masked] mail list, with a view to the result of that last call being discussed in the dnssd session at IETF95.

The hybrid proxy describes use of a DNS push mechanism, which is specified in a separate draft, draft-ietf-dnssd-push-05. 

DNS Push mandates TCP, and use of TLS for Push notifications (see start of section 4). It thus seems to Ralph and I that there is some potential overlap here with the work in dprive on DNS over TLS, so we would welcome comments from dprive WG participants on the draft, either here or on the [email-masked] <mailto:[email-masked]> list, so that we can have a good discussion in BA on progressing the work. We are also hopeful to have feedback from at least one implementation of DNS Push in advance of the meeting.

The draft can be found at https://tools.ietf.org/html/draft-ietf-dnssd-push-05 <https://tools.ietf.org/html/draft-ietf-dnssd-push-05>. 

Abstract

   The Domain Name System (DNS) was designed to return matching records
   efficiently for queries for data that is relatively static.  When
   those records change frequently, DNS is still efficient at returning
   the updated results when polled.  But there exists no mechanism for a
   client to be asynchronously notified when these changes occur.  This
   document defines a mechanism for a client to be notified of such
   changes to DNS records, called DNS Push Notifications.

Many thanks,

Ralph and Tim
dnssd WG co-chairs