Re: [DNSOP] New Draft Charter
Dean Anderson <dean@av8.com> Tue, 11 March 2008 16:27 UTC
Return-Path: <dnsop-bounces@ietf.org>
X-Original-To: ietfarch-dnsop-archive@core3.amsl.com
Delivered-To: ietfarch-dnsop-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2C7BD3A6E73; Tue, 11 Mar 2008 09:27:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.842
X-Spam-Level:
X-Spam-Status: No, score=-100.842 tagged_above=-999 required=5 tests=[AWL=-0.405, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sjQ8Thd9f9pk; Tue, 11 Mar 2008 09:27:53 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B57723A6DCE; Tue, 11 Mar 2008 09:27:53 -0700 (PDT)
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 080983A67EB for <dnsop@core3.amsl.com>; Tue, 11 Mar 2008 09:27:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7+xV54VucFAT for <dnsop@core3.amsl.com>; Tue, 11 Mar 2008 09:27:49 -0700 (PDT)
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66]) by core3.amsl.com (Postfix) with ESMTP id EB0F03A691B for <dnsop@ietf.org>; Tue, 11 Mar 2008 09:27:02 -0700 (PDT)
Received: from [130.105.12.10] ([130.105.12.10]) (authenticated bits=0) by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id m2BGOfer022423 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 11 Mar 2008 12:24:41 -0400
Date: Tue, 11 Mar 2008 12:24:40 -0400
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@citation2.av8.net
To: Peter Koch <pk@DENIC.DE>
In-Reply-To: <20080311151542.GH22613@x27.adm.denic.de>
Message-ID: <Pine.LNX.4.44.0803111211450.22279-100000@citation2.av8.net>
MIME-Version: 1.0
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] New Draft Charter
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dnsop-bounces@ietf.org
Errors-To: dnsop-bounces@ietf.org
On Tue, 11 Mar 2008, Peter Koch wrote: > Dean, > > > So root and gTLD DNS server operations supervision is off the charter? > > to the extent that is has never been there, yes. > > > It used to be the first item. This appears to affect ISOC IETF > > commitments to ICANN to provide this technical role. > > If you could support this observation by tangible textual reference, that would > be appreciated. As a side note, there is an IETF liaison to ICANN, independent > of whatever WG charter. I'm not sure what you mean to dispute. The text of the charter I quoted cites "This will include root zone name servers, gTLD name servers [...]" I don't think it can be made plainer. The liason role is communicative; the liason communicates the consensus of (in this case) DNSOP. The person of liason has not previously been the sole technical expert provided by the IETF. But if that becomes so, this isn't what is described in the MoU. The IETF technical expertise is the combined contributions of its members through consensus and broad industry support. The liason cannot represent a non-existant consensus. If there is merely one person (the liason) then the value of that opinion is also reduced, as there is no genuine industry consensus in the opinion of just one person. > > 1. Define the processes by which Domain Name System (DNS) software > > may be efficiently and correctly administered, configured, and > > operated on Internet networks. This will include root zone > > name servers, gTLD name servers, name servers for other DNS > > zones, iterative DNS resolvers, and recursive DNS resolvers. > > My recollection of the previous discussion of this exact issue is that > people were in favour of not mentioning any particular systems in the > hierarchy especially to avoid the perception conveyed above. People in favor of changing the charter indeed held the position you describe. But my recollection is that the charter wasn't changed; those people didn't have a consensus to change the charter that way at that time. > Note however, that the charter as proposed would _not_ prevent the > DNSOP WG from, say, updating RFC 2870. Under what provision of the new charter would RFC 2870 fall under? --Dean -- Av8 Internet Prepared to pay a premium for better service? www.av8.net faster, more reliable, better service 617 344 9000 _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
- Re: [DNSOP] New Draft Charter Peter Koch
- [DNSOP] New Draft Charter Peter Koch
- Re: [DNSOP] New Draft Charter Stephane Bortzmeyer
- Re: [DNSOP] New Draft Charter Dean Anderson
- Re: [DNSOP] New Draft Charter Joe Abley
- Re: [DNSOP] New Draft Charter Andrew Sullivan
- Re: [DNSOP] New Draft Charter Jaap Akkerhuis
- Re: [DNSOP] New Draft Charter Dean Anderson
- Re: [DNSOP] New Draft Charter Dean Anderson
- Re: [DNSOP] New Draft Charter Peter Koch
- Re: [DNSOP] New Draft Charter Peter Koch
- Re: [DNSOP] New Draft Charter Dean Anderson
- Re: [DNSOP] New Draft Charter bill fumerola
- Re: [DNSOP] New Draft Charter Dean Anderson
- Re: [DNSOP] New Draft Charter bert hubert
- Re: [DNSOP] New Draft Charter Peter Koch