[dnssd] dnssd WG agenda
Tim Chown <tjc@ecs.soton.ac.uk> Sat, 02 April 2016 11:53 UTC
Return-Path: <tjc@ecs.soton.ac.uk>
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 1116112D569 for <dnssd@ietfa.amsl.com>; Sat, 2 Apr 2016 04:53:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.23
X-Spam-Level:
X-Spam-Status: No, score=-1.23 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, SPF_NEUTRAL=0.779, T_RP_MATCHES_RCVD=-0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
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 IlZUJwdwHUV6 for <dnssd@ietfa.amsl.com>; Sat, 2 Apr 2016 04:53:09 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 673F012D568 for <dnssd@ietf.org>; Sat, 2 Apr 2016 04:53:07 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u32Bqx8s002026 for <dnssd@ietf.org>; Sat, 2 Apr 2016 12:52:59 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk u32Bqx8s002026
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1459597980; bh=5wTOi2lRGTGRJtusyIQn/ZBQt3M=; h=From:Subject:Date:To:Mime-Version:References; b=3OJFMulJJkj5TDYBNdasmGnG7R3c84tneyjesPN5hdnMIoUosGk6dN5QF4dgzYYKs aSEVgiPdRJD7VAJaqYLvb+aBNl1/WJs0IpjXaolhNzvFx4tZ/C8Jr0+rhfw5nIduZN ER49bm1Gxj258F0bMQKkSXAG/oq3f/Y9THy5AdXs=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id s31Cqx1913605718Ov ret-id none; Sat, 02 Apr 2016 12:52:59 +0100
Received: from [192.168.0.16] (tchowndsl.claranet.co.uk [212.188.254.49]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id u32BqqFM013164 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <dnssd@ietf.org>; Sat, 2 Apr 2016 12:52:53 +0100
From: Tim Chown <tjc@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B63552B5-69F8-423F-9D57-72FA7E42C0C6"
Message-ID: <EMEW3|81c53070c3cacd35decc5bac91cf4645s31Cqx03tjc|ecs.soton.ac.uk|5C777A33-0B5B-4B67-9D47-7ADB15716784@ecs.soton.ac.uk>
Date: Sat, 02 Apr 2016 12:52:52 +0100
To: dnssd@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
X-Mailer: Apple Mail (2.3112)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=s31Cqx191360571800; tid=s31Cqx1913605718Ov; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
References: <5C777A33-0B5B-4B67-9D47-7ADB15716784@ecs.soton.ac.uk>
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: u32Bqx8s002026
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnssd/Pyp_mesrwP3kM6jxQ3wNErHr9E8>
Subject: [dnssd] dnssd WG agenda
X-BeenThere: dnssd@ietf.org
X-Mailman-Version: 2.1.17
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: <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: Sat, 02 Apr 2016 11:53:11 -0000
Hi, The proposed agenda for Monday is below. Any suggestions for alterations welcome. Our main tasks are: - resolve the outcomes of WGLCs on the 'hybrid proxy' and 'label interop’ drafts - decide whether DNS Push is ready to move to a WGLC - hear about the dnssd threats draft update and the new dnssd privacy draft, and determine how to progress them Tim — snip — DNSSD WG Agenda IETF95, Buenos Aires Monday 4th April 2016 3.50pm - 5.20pm local time Chairs’ Introduction Chairs, 5 mins Discussion: WGLC of Hybrid Unicast/Multicast DNS-Based Service Discovery Stuart Cheshire, 25 mins draft-ietf-dnssd-hybrid-03 https://tools.ietf.org/html/draft-ietf-dnssd-hybrid-03 <https://tools.ietf.org/html/draft-ietf-dnssd-hybrid-03> The level of feedback, either as comments or ’it’s ready’, has been light. Consideration of the scalability of the solution to a famous level would be welcome. We need positive consensus to move forward. Discussion: Next Steps for DNS Push Notifications Tom Pusateri, 15 min draft-ietf-dnssd-push-06 https://tools.ietf.org/html/draft-ietf-dnssd-push-06 <https://tools.ietf.org/html/draft-ietf-dnssd-push-06> Discussion: WGLC of On Interoperation of Labels between DNS and Other Resolution Systems Andrew Sullivan, 10 mins draft-ietf-dnssd-mdns-dns-interop-02 https://tools.ietf.org/html/draft-ietf-dnssd-mdns-dns-interop-02 <https://tools.ietf.org/html/draft-ietf-dnssd-mdns-dns-interop-02> Again, the level of feedback, either as comments or ’it’s ready’, has been light. We need positive consensus to move forward here as well. Discussion: -03 version of Scalable DNS-SD (SSD) Threats Hosnieh Rafiee, 10 mins draft-otis-dnssd-scalable-dns-sd-threats-03 https://tools.ietf.org/html/draft-otis-dnssd-scalable-dns-sd-threats-03 <https://tools.ietf.org/html/draft-otis-dnssd-scalable-dns-sd-threats-03> There are very few changes in the latest version. Is it done? Discussion: New draft: Privacy Extensions for DNS-SD Christian Huitema, 10 mins draft-huitema-dnssd-privacy-00 https://tools.ietf.org/html/draft-huitema-dnssd-privacy-00 <https://tools.ietf.org/html/draft-huitema-dnssd-privacy-00> Discussion on next steps for handling dnssd security/privacy issues Which issues matter? Are they operational or are any protocol-specific issues? Should we merge the two drafts? All, 10 mins Close, Next steps Chairs, 5 mins
- [dnssd] dnssd WG agenda Tim Chown