Thanks for this. Some comments: * The last paragraph in Section 2.4 seems to be making the inevitable "what can we really do about fingerprinting?" argument. It would be great if you could acknowledge that despite the severe technical and practical limits on combatting fingerprinting, specifications should try their best to keep that surface area to a minimum. That may be too normative for this document? (Although, of course, it's clear you care about that!). As a pointer the w3c TAG had a great set of findings on unsanctioned tracking that included the following on fingerprinting: "because combatting fingerprinting is difficult, new Web specifications should take reasonable measures to avoid adding unneeded fingerprinting surface area. However, added surface area should not be a primary factor in determining whether to add a new feature."
* In 4.1.1 it says, "Strictly speaking, displaying and scanning QR-codes does not establish a secure private channel, as others could also photograph this code; but it is reasonable secure for the application area of private service discovery." Is this not a threat model from your two more casual use cases stated in the document? That is, if we change the use case to two activists/journalists in Syria at a cafe, would you choose a different design. (For example, have the service generate a short random code since that will be QR-ified anyway.) I recognize this is just one possible option here from the document and that others (like WoT PKI) might be more appropriate for my Syria example. On Wed, Jun 22, 2016 at 8:18 AM, Tim Chown <[email protected]> wrote: > Hi, > > In the dnssd WG, we are developing methods to enable scalable DNS-based > service discovery, which in practice means enabling mDNS/DNS-SD to work over > multiple links within a site. As defined, mDNS/DNS-SD are link-local > protocols, not forwarded by routers. If successful, one ‘win’ is that users > with devices can discover services that may be physically near them, but > that lie in a different subnet. > > At a high level, the proposed solution works by clients/resolvers sending > queries to hybrid proxies running on specific subnets (which may be manually > configured in an enterprise scenario, or auto-discovered in an unmanaged > home network scenario), which then issue local service discovery messages, > the answers to which are relayed back to the originating querier. > > We’re encouraging discussion of privacy considerations in the WG. As a > result, we now have a draft (see below), including an initial proposal for a > solution, for which we’d welcome wider review. The draft also addresses > mDNS/DNS-SD privacy within single subnet scenarios. > > Feel free to comment here, or join the dnssd WG list and contribute there. > > Many thanks, > Tim & Ralph, dnssd WG co-chairs > > Begin forwarded message: > > From: Christian Huitema <[email protected]> > Subject: [dnssd] FW: New Version Notification for > draft-huitema-dnssd-privacy-01.txt > Date: 10 June 2016 at 21:02:50 BST > To: "[email protected]" <[email protected]> > Cc: Daniel Kaiser <[email protected]> > > Here is a new version of the "DNS-SD Privacy" draft. I co-authored it with > Daniel Kaiser. Daniel is completing his PhD at the University of Konstanz, > in Germany, studying issues related to privacy and discovery. This new draft > is in my opinion much improved from the version 00 that I presented in > Buenos Aires. You can read the abstract below for the broad lines of the > proposed solution. Or, better yet, read the draft and comment! > > -- Christian Huitema > > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: Friday, June 10, 2016 12:35 PM > To: Christian Huitema <[email protected]>; Daniel Kaiser > <[email protected]> > Subject: New Version Notification for draft-huitema-dnssd-privacy-01.txt > > > A new version of I-D, draft-huitema-dnssd-privacy-01.txt > has been successfully submitted by Christian Huitema and posted to the IETF > repository. > > Name: draft-huitema-dnssd-privacy > Revision: 01 > Title: Privacy Extensions for DNS-SD > Document date: 2016-06-10 > Group: Individual Submission > Pages: 26 > URL: > https://www.ietf.org/internet-drafts/draft-huitema-dnssd-privacy-01.txt > Status: > https://datatracker.ietf.org/doc/draft-huitema-dnssd-privacy/ > Htmlized: https://tools.ietf.org/html/draft-huitema-dnssd-privacy-01 > Diff: > https://www.ietf.org/rfcdiff?url2=draft-huitema-dnssd-privacy-01 > > Abstract: > DNS-SD allows discovery of services published in DNS or MDNS. The > publication normally discloses information about the device > publishing the services. There are use cases where devices want to > communicate without disclosing their identity, for example two mobile > devices visiting the same hotspot. > > We propose to solve this problem by a two-stage approach. In the > first stage, hosts discover Private Discovery Service Instances via > DNS-SD using special formats to protect their privacy. These service > instances correspond to Private Discovery Servers running on peers. > In the second stage, hosts directly query these Private Discovery > Servers via DNS-SD over TLS. A pairwise shared secret necessary to > establish these connections is only known to hosts authorized by a > pairing system. > > > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > The IETF Secretariat > > _______________________________________________ > dnssd mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/dnssd > > > > _______________________________________________ > ietf-privacy mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/ietf-privacy > -- Joseph Lorenzo Hall Chief Technologist, Center for Democracy & Technology [https://www.cdt.org] 1401 K ST NW STE 200, Washington DC 20005-3497 e: [email protected], p: 202.407.8825, pgp: https://josephhall.org/gpg-key Fingerprint: 3CA2 8D7B 9F6D DBD3 4B10 1607 5F86 6987 40A9 A871 _______________________________________________ ietf-privacy mailing list [email protected] https://www.ietf.org/mailman/listinfo/ietf-privacy
