Re: [DNSOP] New Draft Charter
Dean Anderson <dean@av8.com> Tue, 11 March 2008 16:12 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 0C7DB3A6E3B; Tue, 11 Mar 2008 09:12:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.869
X-Spam-Level:
X-Spam-Status: No, score=-100.869 tagged_above=-999 required=5 tests=[AWL=-0.432, 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 U8RIjvol0Rl3; Tue, 11 Mar 2008 09:12:25 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BD4CE3A6DFF; Tue, 11 Mar 2008 09:12:17 -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 EAF243A6DFF for <dnsop@core3.amsl.com>; Tue, 11 Mar 2008 09:12:15 -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 EhSlQHhyQXgP for <dnsop@core3.amsl.com>; Tue, 11 Mar 2008 09:12:14 -0700 (PDT)
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66]) by core3.amsl.com (Postfix) with ESMTP id ED3933A693B for <dnsop@ietf.org>; Tue, 11 Mar 2008 09:11:50 -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 m2BG9RcL022398 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 11 Mar 2008 12:09:27 -0400
Date: Tue, 11 Mar 2008 12:09:27 -0400
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@citation2.av8.net
To: Joe Abley <jabley@ca.afilias.info>
In-Reply-To: <48CA32D3-8B3C-4EAF-9709-8182D0B0EA12@ca.afilias.info>
Message-ID: <Pine.LNX.4.44.0803111200250.22279-100000@citation2.av8.net>
MIME-Version: 1.0
Cc: Peter Koch <pk@DENIC.DE>, 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, Joe Abley wrote: > > On 11-Mar-2008, at 10:37, Dean Anderson wrote: > > > So root and gTLD DNS server operations supervision is off the charter? > > I'm not sure it was ever on the charter. > > The paragraph you quoted seems to suggest that the attention of the > working group is equally-focussed on root, TLD and all other > nameservers, whether authority-only servers or not. I didn't say the charter was exclusively oriented to root and gTLD operations. But the current charter explicitly includes them, and the proposed new charter does not. This is not the first time we've discussed these issues. The last time changes to the charter were proposed, I brought up the same issue. Back then I opposed removing root and gTLD operations from the charter. Now, I'm not so certain it isn't a good idea. As I wrote back then: It seems to me the issues outlined in the current charter element above are still a fundamental and important part of the DNSOP mission, particularly with respect to the ICANN MoU and RFC 2870, which give a substantial role to the IETF on DNS Root server operations. There is still an effect on the ICANN MoU and RFC 2870. For one thing, updating RFC 2870 would appear to be out of scope in the proposed new DNSOP charter. The change in my position is that I'm no longer quite so certain root and gTLD operations are a vital part of the IETF or DNSOP mission. I think the subject of root and gTLD supervision is a vital part for _someone_ or _something_, but perhaps not the IETF. --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