Re: [dnssd] Stephen Farrell's No Objection on draft-ietf-dnssd-requirements-05: (with COMMENT)

Tom Pusateri <pusateri@bangj.com> Tue, 17 March 2015 18:22 UTC

Return-Path: <pusateri@bangj.com>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 971471A883C; Tue, 17 Mar 2015 11:22:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.038
X-Spam-Level:
X-Spam-Status: No, score=-1.038 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ApaTFVN7LY_e; Tue, 17 Mar 2015 11:22:09 -0700 (PDT)
Received: from oj.bangj.com (amt0.gin.ntt.net [129.250.11.170]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39A7F1A886F; Tue, 17 Mar 2015 11:22:08 -0700 (PDT)
Received: from [192.168.1.116] (67.20.136.197.dyn-e120.pool.hargray.net [67.20.136.197]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id 60CB0230B; Tue, 17 Mar 2015 14:17:58 -0400 (EDT)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_61649CBE-9E40-4CC1-A776-CC7D7E5058C2"; protocol="application/pgp-signature"; micalg="pgp-sha1"
X-Pgp-Agent: GPGMail 2.5b5
From: Tom Pusateri <pusateri@bangj.com>
In-Reply-To: <2C1D6897-BE72-4902-97A6-C5C6943B1EF7@gmail.com>
Date: Tue, 17 Mar 2015 14:22:05 -0400
Message-Id: <F64EF3B5-BD6C-498A-8F6D-1AAB9C60E1BF@bangj.com>
References: <20150310230433.13239.32024.idtracker@ietfa.amsl.com> <2C1D6897-BE72-4902-97A6-C5C6943B1EF7@gmail.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnssd/NVYBnCP6EbusFynChpahbLEDa4E>
Cc: dnssd-chairs@ietf.org, draft-ietf-dnssd-requirements.all@ietf.org, dnssd@ietf.org, Chown Tim <tjc@ecs.soton.ac.uk>, The IESG <iesg@ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [dnssd] Stephen Farrell's No Objection on draft-ietf-dnssd-requirements-05: (with COMMENT)
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of extensions to Bonjour \(mDNS and DNS-SD\) for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 17 Mar 2015 18:22:10 -0000

> On Mar 17, 2015, at 1:51 PM, Ralph Droms <rdroms.ietf@gmail.com> wrote:
> 
> Stephen - let me summarize the responses to your comments; please let us know if these responses will be sufficient to address your comments...
> 
>> - 6.6: I think one can also leak private information by
>> searching in too broad a scope, e.g. if the client can be
>> fingerprinted allowing re-identification. I think that's
>> different from the example given, and maybe worth noting too.
> 
> Kerry pointed out that the difference between the threat from searching for services as opposed to other forms of name resolution in arbitrary zones is unclear.  While it would be possible to edit this text to include searching as well as registration, I think the resulting text would be too restrictive to allow for useful solutions.  Would you be willing to accept the text as it exists or do you have some other new text to suggest?
> 
> - Ralph
> 

I tried to make it clear in my response yesterday that this was a non-issue but maybe I wasn't as direct as I should have been.

There is no leak of private information by the client. The client is in total control of the scope and the recipient of it's query.

Tom