Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)

Olafur Gudmundsson <ogud@ogud.com> Mon, 17 February 2014 18:58 UTC

Return-Path: <ogud@ogud.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CDB11A0275 for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 10:58:47 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 zmQ56tA6Wic7 for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 10:58:45 -0800 (PST)
Received: from smtp85.ord1c.emailsrvr.com (smtp85.ord1c.emailsrvr.com [108.166.43.85]) by ietfa.amsl.com (Postfix) with ESMTP id 714E21A012E for <dnsop@ietf.org>; Mon, 17 Feb 2014 10:58:45 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp3.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 16EA550150; Mon, 17 Feb 2014 13:58:42 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp3.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 5DBF650089; Mon, 17 Feb 2014 13:58:37 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <951E7F4B-81AC-43BB-B878-4266C5E00373@nominum.com>
Date: Mon, 17 Feb 2014 13:58:37 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <9B97E8E9-9E8A-4374-B65A-4BFA64A10801@ogud.com>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <5300C10A.8010308@dcrocker.net> <5300C52A.9050802@frobbit.se> <5300E26B.4030301@dcrocker.net> <alpine.LFD.2.10.1402161123090.27242@bofh.nohats.ca> <951E7F4B-81AC-43BB-B878-4266C5E00373@nominum.com>
To: Ted Lemon <ted.lemon@nominum.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/_-4RR6ujO0m0oz8u5IjeqIHRsBA
Cc: dnsop WG <dnsop@ietf.org>, Paul Wouters <paul@nohats.ca>, Dave Crocker <dcrocker@bbiw.net>, David Conrad <drc@virtualized.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Feb 2014 18:58:47 -0000

On Feb 17, 2014, at 11:22 AM, Ted Lemon <ted.lemon@nominum.com>; wrote:

> On Feb 16, 2014, at 9:03 PM, Paul Wouters <paul@nohats.ca>; wrote:
>> DNSOP needs
>> to broaden its charter, or we need to revive some kind of DNSEXT group.
> 
> We would need to find some volunteers to act as co-chair.   I don't think adding the work to the DNSOP charter is the right thing to do, although I am not wedded to that position.   I just suspect that (a) it will make life in DNSOP harder and (b) we will get better review in an intarea working group.   But that's a fairly artificial point to be making, so argue away!   :)


I think recreating DNS WG is a bad idea. 
We have a few ideas on the table in various that are related to 
	a) DNS transport TCP, SCTP, "tree answer: give me all records need to answer/validate X starting from point above X", 
	Zone transfer improvements 
	aa) DNS "privacy" ie. channel encryption/authentication 
	b) Operational Automation 
	c) Keeping noise out of DNS (AS112) and name spaces/meta-tld/alt TLD.
	d) New protocols adopting DANE
	e) Name server control protocols 


a) and aa) should have its own short term WG 
b) Belongs in DNSOP 
c) is above DNSEXT and DNSOP wg it is more of an intersection of many different areas like RAI, APPS, 
OPS and SECURITY  ==> a special WG 
d) DANE WG is handling that 
d) Domain boundaries BOF may turn into a WG. 
e) Belongs in DNSOP 

So Yes I see a need for a focused DNS protocol wg at this time.
The problem with long lived groups is you never know when new useful work will show up,
killing groups or just the threat of killing a WG seems to bring out innovation. 

	Olafur