IETF Logo Mail Archive

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

Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 18 February 2014 16:57 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 D8C0D1A0510 for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 08:57:16 -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 WiSBiYbw8Gnu for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 08:57:15 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 74BD41A0228 for <dnsop@ietf.org>; Tue, 18 Feb 2014 08:57:15 -0800 (PST)
Received: from mx1.yitter.info (nat-01-mht.dyndns.com [216.146.45.240]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id B51F68A031 for <dnsop@ietf.org>; Tue, 18 Feb 2014 16:57:10 +0000 (UTC)
Date: Tue, 18 Feb 2014 11:57:10 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: dnsop@ietf.org
Message-ID: <20140218165710.GD27482@mx1.yitter.info>
References: <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> <20140217164408.GC27215@mx1.yitter.info> <9D53CD2A-B443-468B-9EB6-B934728DAF25@nominum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <9D53CD2A-B443-468B-9EB6-B934728DAF25@nominum.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/lgXviO6UVOzjJvkpx4YSEP4Kc2w
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: Tue, 18 Feb 2014 16:57:19 -0000

On Mon, Feb 17, 2014 at 12:57:40PM -0500, Ted Lemon wrote:
> 
> Sure.   If dnsop wants to do this work, that's fine.

No.  This was precisely my point.  For most of the stuff people want,
the work should be in a WG that does not have "DNS" in its name.
That's the _key_ point.  We protocol weenies need to get out of our
comfy chair and go learn why in the world people want to put
_anything_ in the DNS.  Our failure to do that is how we ended up with
the situation we have: we keep stamping our feet and saying that the
DNS works _just fine_ with new RRTYPEs, for instance, except that many
who want to use them cannot.

My view was that if there was something that was DNS-specific that
needed attention, people should have a BoF.  And look!  We have 2 BoFs
on specific DNS topics in London.  The questions are narrow and
focussed, not big floppy "gee, this looks like DNS, so it should be
swatted over to the DNS weenies" ones.  

If the goal is a "Get off my lawn" working group, then big generic
questions are in order.  But I think we can do better.

A


-- 
Andrew Sullivan
ajs@anvilwalrusden.com

v2.23.0 | Report a Bug | By Email