Re: [Driu] Proposed agenda

Tom Pusateri <pusateri@bangj.com> Wed, 20 June 2018 16:18 UTC

Return-Path: <pusateri@bangj.com>
X-Original-To: driu@ietfa.amsl.com
Delivered-To: driu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D11DA12F1A2 for <driu@ietfa.amsl.com>; Wed, 20 Jun 2018 09:18:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 cY0pR6RQBV7b for <driu@ietfa.amsl.com>; Wed, 20 Jun 2018 09:18:44 -0700 (PDT)
Received: from oj.bangj.com (amt0.gin.ntt.net [129.250.11.170]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28BCF130E9C for <driu@ietf.org>; Wed, 20 Jun 2018 09:18:44 -0700 (PDT)
Received: from [10.46.144.157] (unknown [208.66.48.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id 073BAFD5; Wed, 20 Jun 2018 12:18:40 -0400 (EDT)
From: Tom Pusateri <pusateri@bangj.com>
Message-Id: <7A7BA397-728F-432D-A449-D040D1D8B363@bangj.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2966966B-BAE5-4D05-BEAF-9811803AEF3F"
Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\))
Date: Wed, 20 Jun 2018 12:18:40 -0400
In-Reply-To: <9976F5D7-864E-4F85-9232-866150EF53D1@icann.org>
Cc: "driu@ietf.org" <driu@ietf.org>
To: Paul Hoffman <paul.hoffman@icann.org>
References: <9976F5D7-864E-4F85-9232-866150EF53D1@icann.org>
X-Mailer: Apple Mail (2.3445.8.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/driu/SZEkpTDrCRhpupwUMvUEq-ktjFA>
Subject: Re: [Driu] Proposed agenda
X-BeenThere: driu@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: "DNS Resolver Identification and Use \(DRIU\)." <driu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/driu>, <mailto:driu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/driu/>
List-Post: <mailto:driu@ietf.org>
List-Help: <mailto:driu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/driu>, <mailto:driu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jun 2018 16:18:47 -0000


> On Jun 20, 2018, at 12:06 PM, Paul Hoffman <paul.hoffman@icann.org> wrote:
> 
> Greetings. Even though the discussion here has been less vigorous than I expected, there is clearly some interest in the topics. I suspect when we get a bunch of people in the room, the mic lines might engender more interest in specific topics.
> 
> Also, I'm volunteering folks who might not be attending the meeting. If you are interested in preparing a presentation but are not going to be at the meeting, getting someone else to present is just fine.
> 
> We have 90 minutes. I propose the following, but am totally open to other suggestions. In particular, if someone has a draft or even a partially-formed idea about topics related to DNS resolver identification and use, please speak up now so we can give scheduled time instead of open mic time. Some areas I suspect people may have ideas are:
> - DNS resolver choice in protocols other than DHCP
> - DHCP configuration for protocols other than DNS that have multiple transports (maybe SMTP?)
> - Fallbacks from secure to non-secure where there is no user interface for warnings
> 
> Intro to the topics: 15 mins (Paul Hoffman)
> DHCPv6 Options for private DNS Discovery: 15 mins (Tom Pusateri and Willem Toorop)
> Levels of security and privacy for different resolver transports: 15 mins (Sara Dickinson)
> Open mic (remainder of time)
> 
> With the current agenda, we are just before the last DNSOP meeting, so we will hopefully have a good turnout of DNS folks. I hope we also get a good turnout of folks who think about configuration as well.
> 

I expect much of the discussion of DHCP to get bogged down in the threat analysis of providing secure DNS configuration over DHCP. I think this would be better served by creating a separate agenda item for discussion. As mentioned before, I have written a threat document here but continue to work on it.

https://github.com/pusateri/draft-tpwt-dhc-dns-discovery/blob/master/threat.md <https://github.com/pusateri/draft-tpwt-dhc-dns-discovery/blob/master/threat.md>

Tom