Re: [DNSOP] New Draft Charter

Andrew Sullivan <ajs@crankycanuck.ca> Tue, 11 March 2008 15:33 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 A62AA3A6DA5; Tue, 11 Mar 2008 08:33:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.797
X-Spam-Level:
X-Spam-Status: No, score=-100.797 tagged_above=-999 required=5 tests=[AWL=-0.360, 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 5pRZhWQKeTjh; Tue, 11 Mar 2008 08:33:43 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B08433A6A43; Tue, 11 Mar 2008 08:33:43 -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 93A3A3A67B2 for <dnsop@core3.amsl.com>; Tue, 11 Mar 2008 08:33:42 -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 Awnl8k4rTH0q for <dnsop@core3.amsl.com>; Tue, 11 Mar 2008 08:33:41 -0700 (PDT)
Received: from main2.mycybernet.net (main2.mycybernet.net [209.222.63.140]) by core3.amsl.com (Postfix) with ESMTP id 92B783A697E for <dnsop@ietf.org>; Tue, 11 Mar 2008 08:33:41 -0700 (PDT)
Received: from 227-54-222-209.mycybernet.net ([209.222.54.227] helo=crankycanuck.ca) by main2.mycybernet.net with esmtp (Exim 4.62) (envelope-from <ajs@crankycanuck.ca>) id 1JZ6RR-00015T-L1 for dnsop@ietf.org; Tue, 11 Mar 2008 11:31:01 -0400
Received: by crankycanuck.ca (Postfix, from userid 1000) id 67BEA50190; Tue, 11 Mar 2008 11:30:56 -0400 (EDT)
Date: Tue, 11 Mar 2008 11:30:56 -0400
From: Andrew Sullivan <ajs@crankycanuck.ca>
To: dnsop@ietf.org
Message-ID: <20080311153056.GC1465@crankycanuck.ca>
References: <Pine.LNX.4.44.0803111031320.22279-100000@citation2.av8.net> <48CA32D3-8B3C-4EAF-9709-8182D0B0EA12@ca.afilias.info>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <48CA32D3-8B3C-4EAF-9709-8182D0B0EA12@ca.afilias.info>
User-Agent: Mutt/1.5.13 (2006-08-11)
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

Dear colleagues,

On Tue, Mar 11, 2008 at 10:53:54AM -0400, Joe Abley wrote:
> 
> 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.

While that's true, the older text also explictly says that the WG is
interested in administration, configuration, and operation of the DNS:

      Define the processes by which Domain Name System (DNS) software may be
      efficiently and correctly administered, configured, and operated on
      Internet networks.

It seems to me that that additional scope is worth retaining.  Perhaps this
sentence

      The DNS Operations (DNSOP) Working Group will develop and review
      guidelines for the correct, efficient and secure configuration of DNS
      authoritative servers, resolvers, and DNSSEC validators.

could be altered slightly to 

      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.

?

A
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop