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

Suzanne Woolf <suzworldwide@gmail.com> Mon, 17 February 2014 18:45 UTC

Return-Path: <suzworldwide@gmail.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 BEEF51A0539 for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 10:45:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 ipuNXVGNWqcZ for <dnsop@ietfa.amsl.com>; Mon, 17 Feb 2014 10:45:02 -0800 (PST)
Received: from mail-qg0-x230.google.com (mail-qg0-x230.google.com [IPv6:2607:f8b0:400d:c04::230]) by ietfa.amsl.com (Postfix) with ESMTP id DFC101A0520 for <dnsop@ietf.org>; Mon, 17 Feb 2014 10:45:01 -0800 (PST)
Received: by mail-qg0-f48.google.com with SMTP id a108so5469542qge.7 for <dnsop@ietf.org>; Mon, 17 Feb 2014 10:44:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=y644nO5AVY0zqQYb0VaREjRgtXjHUw8ON/zF9Z7Fopg=; b=qqaH8sqkKx52mdjDwabuYzxQINLDQnrwKewWbHWyXdVQGfUpSZHICk/02OW7G7mqv+ BwWjhzOYQYmz/nKFxQNj8dokiuAfJ5P8XllOsuh/07Q4rYOBWpTACADeDkF0SgN6zclM rViEH136oIWrZb+x/HhnfLhonUUVCMSDiO23NYAuLLfLAFbjeDcseS2aYZDTf/3d3K+j kr22Amj7+fCg/wLvxEX8dWwkBE/QTnh+cEe7Gn4YecPky71obNalhoHmKSYeK2aCf6eV caXeOR17lZBYfHcqXrmAi7ago6iXID+BHAjApAR8jGMRMNRaARgHqVuTjOWveFfT83uq hBbw==
X-Received: by 10.224.166.210 with SMTP id n18mr29873933qay.32.1392662699186; Mon, 17 Feb 2014 10:44:59 -0800 (PST)
Received: from [10.0.0.15] (c-24-63-89-87.hsd1.ma.comcast.net. [24.63.89.87]) by mx.google.com with ESMTPSA id i7sm47546232qan.0.2014.02.17.10.44.55 for <dnsop@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 17 Feb 2014 10:44:55 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <915BC55A-FCB2-4C7D-AABA-E8BE8018D4CF@virtualized.org>
Date: Mon, 17 Feb 2014 13:45:01 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <51F20B86-AB72-4AAC-9223-3C4DE2B6084E@gmail.com>
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> <20140217164408.GC27215@mx1.yitter.info> <9D53CD2A-B443-468B-9EB6-B934728DAF25@nominum.com> <915BC55A-FCB2-4C7D-AABA-E8BE8018D4CF@virtualized.org>
To: dnsop <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/bnzbUkjh6DbDKA39ZAjfx10qwYo
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:45:04 -0000

On Feb 17, 2014, at 1:15 PM, David Conrad <drc@virtualized.org>; wrote:

> Ted,
> 
> On Feb 17, 2014, at 9:57 AM, Ted Lemon <Ted.Lemon@nominum.com>; wrote:
>> If dnsop wants to do this work, that's fine.
> 
> Given the various topics being discussed in DNSOP and the relatively high interest/reviews/comments/etc being shown, I think DNSOP is working fine.

This hasn't always been the case. At the moment, we've got a couple of high-profile issues by the tail and we're working to get some items that had gone dormant in front of the WG again. I hope the current level of interest can be sustained as needed to get work meaningfully defined and completed. Ask me in Toronto how I think we're doing :)
> 
>> Unfortunately, the dysfunction will arise wherever DNS improvements are suggested, so not trying to fix it is not an option.   And of course I realize that many good IETF contributors have been ground to a nubbin trying to fix the aforementioned dysfunction, and have no particular reason to think I would have been more able to fix it than my predecessors.
> 
> Given experiences, I have to wonder if the whole idea of a long-term working group just leads to dysfunction -- perhaps the IETF version of an echo chamber (or perhaps even inbreeding).  Perhaps a better approach would be to use something like DNSOP which has an operations bent is use to see if there are ideas/interest in particular topics that can drive the creation of working groups that focus on the specific DNS-related issues?

This seems to me to be the function v6ops has in its charter as "Solicit input from network operators and users to identify operational issues with the IPv4/IPv6 Internet [for us, with DNS], and determine solutions or workarounds to those issues….This work should primarily be conducted by those areas and WGs which are responsible and best fit to analyze these problems, but v6ops may also cooperate in focusing such work."

In preliminary discussion of the re-chartering that will be on the agenda for London, we've already stumbled on the possibility that what's really needed here is something similar to what v6ops does-- a way to support getting a feedback loop closed between DNS operators and the assorted DNS users elsewhere in the IETF. The actual mechanism of that interaction may well include "problem statement" documents to be handed off to other WGs, but I think that's not necessarily a bad thing; the work should go where there are people motivated and able to do it, but still should be informed by focused expertise on the infrastructure, including DNS.

MHO (no hat): The balancing act is not only between operators and vendors/implementors, but also between DNS as an application that needs to evolve with the uses of the Internet and DNS as infrastructure that everyone relies upon and therefore should probably maintain some level of predictability and consistency. If DNSOP can't do anything useful towards managing that balance under its current charter, or a new charter that can get consensus support and action, we can and should shut it down.


Suzanne