Re: [DNSOP] New Draft Charter

Dean Anderson <dean@av8.com> Fri, 14 March 2008 22:55 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 F09E63A6B04; Fri, 14 Mar 2008 15:55:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.617
X-Spam-Level:
X-Spam-Status: No, score=-100.617 tagged_above=-999 required=5 tests=[AWL=-0.180, 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 ZD4L9LP-yxOb; Fri, 14 Mar 2008 15:55:07 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EAB9B3A686D; Fri, 14 Mar 2008 15:55:06 -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 144B83A686D for <dnsop@core3.amsl.com>; Fri, 14 Mar 2008 15:55:05 -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 YBNOL9Oy6uS4 for <dnsop@core3.amsl.com>; Fri, 14 Mar 2008 15:55:04 -0700 (PDT)
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66]) by core3.amsl.com (Postfix) with ESMTP id 167783A67E9 for <dnsop@ietf.org>; Fri, 14 Mar 2008 15:55:04 -0700 (PDT)
Received: from citation2.av8.net (citation2.av8.net [130.105.12.10]) (authenticated bits=0) by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id m2EMqj5n000941 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 14 Mar 2008 18:52:45 -0400
Date: Fri, 14 Mar 2008 18:52:44 -0400
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@citation2.av8.net
To: Peter Koch <pk@denic.de>
In-Reply-To: <20080314040611.GF7553@x27.adm.denic.de>
Message-ID: <Pine.LNX.4.44.0803141852150.17638-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

What clause would DNS Root Anycast stability fall under?

		--Dean

On Fri, 14 Mar 2008, Peter Koch wrote:

> Dean,
> 
> > > 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 fact that name servers dealing with a certain level in the DNS hierarchy or
> with certain parts of the DNS tree are not or are no longer explicitly mentioned
> does not imply that they could not taken into special consideration where
> appropriate.
> 
> > 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
> 
> IETF Liaisons are appointed by and report to the IAB.  There is an IAB
> statement regarding the IETF's Liaison to the ICANN Board of Directors at
> <http://www.iab.org/liaisons/icann/icann-liaison.html>.  Neither DNSOP nor
> any other IETF WG is mentioned there and is at the sole discretion of the
> IAB to consult with IETF WGs in its (the IAB's) role of assisting the
> Liaison in executing their duties.  I asked you to provide tangible reference
> (i.e. "chapter and verse") to support your view of DNSOP having a special
> role w.r.t. root server operations.  I fail to see this information having
> been provided.  Also, there was no support of your view. Therefore I consider
> this issue closed.
> 
> > 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.
> 
> The sad fact is that me dropped the ball on the charter work.
> 
> > > 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?
> 
> The general clause
> 
>   The DNS Operations (DNSOP) Working Group will develop and review guidelines
>   for the correct, efficient and secure configuration, administration, and
>   operation of DNS authoritative servers, resolvers, and DNSSEC validators.
> 
> would certainly cover this.
> 
> -Peter [with hat]
> 
> 

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