Re: [dnssd] Call for WG Adoption: draft-huitema-dnssd-privacy-01

Daniel Kaiser <daniel.kaiser@uni-konstanz.de> Tue, 26 July 2016 12:49 UTC

Return-Path: <daniel.kaiser@uni-konstanz.de>
X-Original-To: dnssd@ietfa.amsl.com
Delivered-To: dnssd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E48C12D811 for <dnssd@ietfa.amsl.com>; Tue, 26 Jul 2016 05:49:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.486
X-Spam-Level:
X-Spam-Status: No, score=-5.486 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.287] autolearn=ham autolearn_force=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 d5vv2P9Rd8jY for <dnssd@ietfa.amsl.com>; Tue, 26 Jul 2016 05:49:48 -0700 (PDT)
Received: from purin.rz.uni-konstanz.de (purin.rz.uni-konstanz.de [134.34.240.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1B6412D8EF for <dnssd@ietf.org>; Tue, 26 Jul 2016 05:49:46 -0700 (PDT)
Received: from nkongsamba.rz.uni-konstanz.de (HELO smtp.uni-konstanz.de) ([134.34.240.62]) by viribus.rz.uni-konstanz.de with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Jul 2016 12:49:44 +0000
Received: from [192.168.1.12] (unknown [5.158.128.23]) (Authenticated sender: daniel.kaiser) by smtp.uni-konstanz.de (Postfix) with ESMTPSA id 71983106; Tue, 26 Jul 2016 14:49:44 +0200 (CEST)
To: Tim Chown <Tim.Chown@jisc.ac.uk>
References: <3D43CEAD-3D12-4E32-AA01-8A1E4ABD8D86@jisc.ac.uk> <CABkgnnVnB=ByS_jmguWR3aWsmtjP-WwJtEcPOTHRoEPuif4SDQ@mail.gmail.com> <95946360-5699-4a88-1d2c-18ef684a7a35@uni-konstanz.de> <E75CFEC5-F32B-4283-8784-AF3EF922C4AC@jisc.ac.uk>
From: Daniel Kaiser <daniel.kaiser@uni-konstanz.de>
Message-ID: <a86d0de0-c660-5064-c4a1-bc811d5c806c@uni-konstanz.de>
Date: Tue, 26 Jul 2016 14:49:44 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <E75CFEC5-F32B-4283-8784-AF3EF922C4AC@jisc.ac.uk>
Content-Type: multipart/alternative; boundary="------------755741DA7E1F2942F6C03A0F"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnssd/mb4MYbDRfnEu0KsgU3NFEBojoTU>
Cc: "dnssd@ietf.org" <dnssd@ietf.org>
Subject: Re: [dnssd] Call for WG Adoption: draft-huitema-dnssd-privacy-01
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Discussion of extensions to DNS-based service discovery for routed networks." <dnssd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnssd>, <mailto:dnssd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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, 26 Jul 2016 12:49:51 -0000

Hi Tim,

we could write a 00 draft on pairing which might help
the AD and the WG to decide whether pairing should be

1) integrated in the existing privacy draft,
2) addressed in a separate draft within the dnssd group, or
3) addressed in another working group.

As there is consensus that we should address pairing,
I will definitely continue working on that :).

"The adoption call for the main document will still need to take into account that the pairing work needs to be done."


Is there something I should do?


kind regards
Daniel


On 07/26/2016 11:56 AM, Tim Chown wrote:
> Hi Daniel,
>
> On 26 Jul 2016, at 10:50, Daniel Kaiser <daniel.kaiser@uni-konstanz.de<mailto:daniel.kaiser@uni-konstanz.de>> wrote:
>
> We started working on a new document on pairing.
> A reference to this new pairing document will be substituted for
> the pairing part in the privacy document.
>
> Further, we will remove the part on the simple design from the
> privacy document making it more concise.
>
> I don’t think a strong view was expressed either way in Berlin as to whether the work should be in one document or two. But if our AD does recommend taking the pairing work to a different WG, then abstracting the work to a separate doc will of course be useful.
>
> The adoption call for the main document will still need to take into account that the pairing work needs to be done.
>
> Tim
>
> On 07/26/2016 10:28 AM, Martin Thomson wrote:
>
> What is the status of the pairing piece of this work?  None of this
> can work without addressing that portion.  The document contains some
> ideas, but these are quite nebulous and certainly not sufficient to
> deploy an interoperable solution for this.
>
> (I'm generally supportive of this work, but I want to make sure that
> everyone understands the scope and magnitude of the work involved
> here.)
>
> On 25 July 2016 at 16:16, Tim Chown <Tim.Chown@jisc.ac.uk><mailto:Tim.Chown@jisc.ac.uk> wrote:
>
>
> Hi,
>
> At the meeting in Berlin, there was a positive reaction to the "Privacy
> Extensions for DNS-SD” draft,
> https://tools.ietf.org/html/draft-huitema-dnssd-privacy-01.
>
> While only a small number of people had read it in detail, those who had
> read it expressed a desire for the WG to adopt the draft.
>
> This email therefore begins a two-week formal dnssd mail list call for
> adoption of the draft by the WG. Please send any comments, for or against,
> to the dnssd WG list. If you indicated support in the meeting, feel free to
> reaffirm this, and add any comments.
>
> The call ends on Monday 8th August.
>
> The document status in the data tracker can be found at
> https://datatracker.ietf.org/doc/draft-huitema-dnssd-privacy/.
>
> Note that the WG in which the specifics of the pairing protocol will be
> developed will be reviewed by our AD. On the one had it is a generic
> mechanism that may be better defined in a security WG, on the other we
> should have a critical mass of people to get the work done here, if the
> draft is adopted.
>
> Tim
>
>
>
>
> _______________________________________________
> dnssd mailing list
> dnssd@ietf.org<mailto:dnssd@ietf.org>
> https://www.ietf.org/mailman/listinfo/dnssd
>
>
>
> _______________________________________________
> dnssd mailing list
> dnssd@ietf.org<mailto:dnssd@ietf.org>
> https://www.ietf.org/mailman/listinfo/dnssd
>
>
> _______________________________________________
> dnssd mailing list
> dnssd@ietf.org<mailto:dnssd@ietf.org>
> https://www.ietf.org/mailman/listinfo/dnssd
>
>