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

bmanning@vacation.karoshi.com Mon, 05 December 2011 02:39 UTC

Return-Path: <bmanning@karoshi.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 30B1021F8ABC for <dnsext@ietfa.amsl.com>; Sun, 4 Dec 2011 18:39:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 2a2aUvh6MNQl for <dnsext@ietfa.amsl.com>; Sun, 4 Dec 2011 18:39:53 -0800 (PST)
Received: from vacation.karoshi.com (vacation.karoshi.com [198.32.6.68]) by ietfa.amsl.com (Postfix) with ESMTP id AD27221F8AB9 for <dnsext@ietf.org>; Sun, 4 Dec 2011 18:39:53 -0800 (PST)
Received: from karoshi.com (localhost.localdomain [127.0.0.1]) by vacation.karoshi.com (8.12.8/8.12.8) with ESMTP id pB52daFa030664; Mon, 5 Dec 2011 02:39:41 GMT
Received: (from bmanning@localhost) by karoshi.com (8.12.8/8.12.8/Submit) id pB52dVo7030663; Mon, 5 Dec 2011 02:39:31 GMT
Date: Mon, 05 Dec 2011 02:39:30 +0000
From: bmanning@vacation.karoshi.com
To: Jim Reid <jim@rfc1035.com>
Message-ID: <20111205023930.GA30651@vacation.karoshi.com.>
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.> <7A0435E4-C0D0-4D0B-A6C0-B2704B8AFFC3@rfc1035.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <7A0435E4-C0D0-4D0B-A6C0-B2704B8AFFC3@rfc1035.com>
User-Agent: Mutt/1.4.1i
Cc: bmanning@vacation.karoshi.com, 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 02:39:54 -0000

On Mon, Dec 05, 2011 at 01:08:20AM +0000, Jim Reid wrote:
> 
> I think you're being over-dramatic. 

	as may be... 

> >	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.

	actually, it kind of does - the directorate came into existance to 
	support dnsext - absent dnsext, there is no good reason to keep
	an private, non-transparent group around making policy choices
	(Ralph indicated they would be taking on this role...)

> 
> >	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?

	we wouldn't and there is no way to find out.  pretty much the 
	definition of a cenusre board, star chamber, or kangaroo court.

	completely unaccuntable.
	
> >	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.

	really?  do you want to test that?  why couldnt the community
	do it?  like they have for the past 25 years.  

> >	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.

	as long as they are tied together - then they will get mentioned 
	together.