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

Andrew Sullivan <ajs@anvilwalrusden.com> Mon, 17 February 2014 16:44 UTC

Return-Path: <ajs@anvilwalrusden.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 CF96F1A00B4 for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 08:44:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level:
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] 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 aoMnadKf1EUx for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 08:44:21 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id E5C801A0509 for <dnsop@ietf.org>; Mon, 17 Feb 2014 08:44:20 -0800 (PST)
Received: from mx1.yitter.info (c-75-69-155-67.hsd1.nh.comcast.net [75.69.155.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id E90768A031 for <dnsop@ietf.org>; Mon, 17 Feb 2014 16:44:17 +0000 (UTC)
Date: Mon, 17 Feb 2014 11:44:15 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20140217164408.GC27215@mx1.yitter.info>
References: <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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <951E7F4B-81AC-43BB-B878-4266C5E00373@nominum.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/q9LrB1kHoFlmUMmEPIKc7iSS-aQ
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 16:44:23 -0000

I am not convinced that DNS belongs in the Internet area.  It's an
application.  I think if we need a place to discuss broader DNS
innovation, then it should be in Applications.

But I also have pretty strong doubts that "DNS innovation" needs a
place for such discussion, on the grounds that when we _had_ such a WG
nobody did any work.  It was just a mailing list and WG for people to
say, "Get off my lawn."  Document reviews languished for months or
years.  LCs resulted in no comments. 

Why shouldn't that work go on in the WGs that want the innovations in
question?  Why shouldn't people who know about the DNS involve
themselves in the protocols that want to use these innovations so
that, instead of being Defenders of the Protocol Faith, they are
engineers trying to solve practical engineering problems that others
have, but in a way consistent with the deployed architecture?

Best regards,

A

On Mon, Feb 17, 2014 at 11:22:19AM -0500, Ted Lemon 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!   :)
> 
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop

-- 
Andrew Sullivan
ajs@anvilwalrusden.com