Re: [DNSOP] WGLC: Requirements for Management of Name Servers for the DNS

Todd Glassey CISM CIFI <tglassey@earthlink.net> Sun, 22 March 2009 18:01 UTC

Return-Path: <tglassey@earthlink.net>
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 932B63A69D4 for <dnsop@core3.amsl.com>; Sun, 22 Mar 2009 11:01:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.594
X-Spam-Level:
X-Spam-Status: No, score=-2.594 tagged_above=-999 required=5 tests=[AWL=0.005, BAYES_00=-2.599]
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 Y99nq3fRFBJs for <dnsop@core3.amsl.com>; Sun, 22 Mar 2009 11:01:41 -0700 (PDT)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by core3.amsl.com (Postfix) with ESMTP id AA2153A689D for <dnsop@ietf.org>; Sun, 22 Mar 2009 11:01:41 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=jMwwgqdfAJ430i9NnojBqLFzYzmwr1Brmcpq4dd4KmnHgks9Azth9aaQq8CTcM7U; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.66] (helo=[192.168.1.100]) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1LlS0E-00080S-E6; Sun, 22 Mar 2009 14:02:30 -0400
Message-ID: <49C67D34.60606@earthlink.net>
Date: Sun, 22 Mar 2009 11:02:28 -0700
From: Todd Glassey CISM CIFI <tglassey@earthlink.net>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>
References: <20090318163132.GA8085@unknown.office.denic.de> <49C5D04A.8020603@dougbarton.us>
In-Reply-To: <49C5D04A.8020603@dougbarton.us>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79bfc476159a6da1b665aa7a9f0e31cf11350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.66
Cc: IETF DNSOP WG <dnsop@ietf.org>
Subject: Re: [DNSOP] WGLC: Requirements for Management of Name Servers for the DNS
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/mail-archive/web/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>
X-List-Received-Date: Sun, 22 Mar 2009 18:01:42 -0000

Doug Barton wrote:
> Peter Koch wrote:
>   
>> Dear WG,
>>
>> this is to initiate a working group last call on
>>
>>         "Requirements for Management of Name Servers for the DNS"
>>         draft-ietf-dnsop-name-server-management-reqs-02.txt
>>
>> ending Friday, 2009-04-10, 23:59 UTC.  The tools site gives easy access to
>> diffs and such under
>>  <http://tools.ietf.org/html/draft-ietf-dnsop-name-server-management-reqs-02>.
>>     
>
> I've read the draft at the URL above and am generally supportive of
> its moving forward. I noticed the following nits. Assuming that the
> grammatical issues could be sorted out down the road I would not
> object to the draft moving forward without the other issues I mention
> below being addressed.
>
>
> hope this helps,
>
> Doug
>
>
> Abstract: "not a interoperable" should be "not an ..."
> Abstract: The last paragraph is awkward. Perhaps:
> 	This document discusses the requirements of a management
> 	system for DNS name servers and can be used as a shopping
> 	list of needed features for such a system.
>   

As long as you are being nit picky the phrase "(Domain Name Service) 
name servers" reads kinda funny. How about just DNS Resolver's or 
something like that?

T.
> 1. Introduction: "not a interoperable" should be "not an ..."
> 1. Introduction: The awkward paragraph from the Abstract is repeated here.
> 2.1.1 Zone Size Constraints: The last sentence is awkward. Perhaps:
> 	Both deployment scenarios are common.
> 2.1.3 Configuration Data Volatility: Same as 2.1.1 above.
> 2.1.5 Common Data Model: "is needed for of the operations discussion"
> 	the "of" there should be removed
> 3.1.1 Needed Control Operations
> 	The ability to do a reload on an individual zone should probably be
> mentioned here.
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>
>