Re: [dnsext] the DNS Directorate and the end of dnsext

Jim Reid <jim@rfc1035.com> Mon, 05 December 2011 01:08 UTC

Return-Path: <jim@rfc1035.com>
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E5E821F847F for <dnsext@ietfa.amsl.com>; Sun, 4 Dec 2011 17:08:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vizt0yjPrv3k for <dnsext@ietfa.amsl.com>; Sun, 4 Dec 2011 17:08:23 -0800 (PST)
Received: from shaun.rfc1035.com (smtp.v6.rfc1035.com [IPv6:2001:4b10:100:7::25]) by ietfa.amsl.com (Postfix) with ESMTP id B5DFE21F8469 for <dnsext@ietf.org>; Sun, 4 Dec 2011 17:08:23 -0800 (PST)
Received: from gromit.rfc1035.com (gromit.rfc1035.com [195.54.233.69]) by shaun.rfc1035.com (Postfix) with ESMTP id 6F53DCBC44C; Mon, 5 Dec 2011 01:08:21 +0000 (GMT)
Message-Id: <7A0435E4-C0D0-4D0B-A6C0-B2704B8AFFC3@rfc1035.com>
From: Jim Reid <jim@rfc1035.com>
To: bmanning@vacation.karoshi.com
In-Reply-To: <20111204232556.GA30268@vacation.karoshi.com.>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v936)
Date: Mon, 05 Dec 2011 01:08:20 +0000
References: <4ED94590.3090902@ogud.com> <4ED954A2.8090708@dougbarton.us> <EEAE3014-48B5-4344-B253-7A2269447EA5@cisco.com> <20111204055236.GB19382@vacation.karoshi.com.> <A48F2510-A84D-461B-AA9C-8BA29B8503F0@rfc1035.com> <20111204232556.GA30268@vacation.karoshi.com.>
X-Mailer: Apple Mail (2.936)
Cc: DNSEXT Group Working <dnsext@ietf.org>
Subject: Re: [dnsext] the DNS Directorate and the end of dnsext
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Dec 2011 01:08:24 -0000

On 4 Dec 2011, at 23:25, bmanning@vacation.karoshi.com wrote:
> 	perhaps.  if a directorate exists without a foundational
> 	wg to support it

What, just like pretty much all the other IETF directorates: http://www.ietf.org/iesg/directorate.html?

Could dnsop serve as your "foundational wg"? If not, why not?

> 	what you end up with is an effective censure board
> 	that rules on proposed changes to the DNS, absent broad input
> 	from the community.

I think you're being over-dramatic. The role of the DNS Directorate is  
very clear. At least it is once you find its home page: http://www.ietf.org/iesg/directorate/dns.html 
.  :-) It's a bit of a stretch to claim dnsdir constitutes an  
"effective censure board that rules on proposed changes to the DNS".

> 	absent a WG, what are the rules for becoming a member of the  
> directorate and 	how is a member removed for cause?

Oh. You believe the IETF is a democracy with bureacucratic procedures.  
I see. :-) I do agree that you have a valid point in how DNS  
directorate members are chosen and retired. This still has nothing to  
do with the winding up of dnsext IMO.

> 	If you are comfortable w/ the IESG and the ADs making
> 	DNS protocol choices on yur behalf, then that is your perogative.

I didn't say that and I very much doubt our friends in the DNS  
directorate see their role like that either. Though since there's no  
reports on what they do/say, how could someone from the outside know?

> 	I for one, am not and would like the ability to have/conviene
> 	a WG to solve DNS issues -BY THE COMMUNITY- and not by a closed,
> 	opaque body that is not accountable to that community.

+1. I would expect that if the DNS Directorate was confronted with  
something that looked like a protocol change, they'd do The Right  
Thing. ie Get the Powers That Be to create and charter a new WG.

> 	I have the answer on who,  we don't have answers on succession
> 	or accountablity

By all means continue to bang that drum Bill. But please don't confuse  
that with the demise of dnsext.