[DNSOP] New Draft Charter
Peter Koch <pk@DENIC.DE> Tue, 11 March 2008 03:07 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 6938B3A6A1D; Mon, 10 Mar 2008 20:07:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.739
X-Spam-Level:
X-Spam-Status: No, score=-100.739 tagged_above=-999 required=5 tests=[AWL=-0.302, 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 vUssysiXxNdF; Mon, 10 Mar 2008 20:07:55 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3BB453A6A4E; Mon, 10 Mar 2008 20:07:55 -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 E469528C10E for <dnsop@core3.amsl.com>; Mon, 10 Mar 2008 20:07:53 -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 ptbQ2qDnm4hO for <dnsop@core3.amsl.com>; Mon, 10 Mar 2008 20:07:52 -0700 (PDT)
Received: from office.denic.de (gw-office.denic.de [81.91.160.182]) by core3.amsl.com (Postfix) with ESMTP id 8CD9D3A6A37 for <dnsop@ietf.org>; Mon, 10 Mar 2008 20:07:42 -0700 (PDT)
Received: from x27.adm.denic.de ([10.122.64.128]) by office.denic.de with esmtp id 1JYunp-0001Ic-Ls; Tue, 11 Mar 2008 04:05:21 +0100
Received: from localhost by x27.adm.denic.de with local id 1JYuni-0008BR-O3; Tue, 11 Mar 2008 04:05:14 +0100
Date: Tue, 11 Mar 2008 04:05:14 +0100
From: Peter Koch <pk@DENIC.DE>
To: IETF DNSOP WG <dnsop@ietf.org>
Message-ID: <20080311030514.GB30313@x27.adm.denic.de>
Mime-Version: 1.0
Content-Disposition: inline
User-Agent: Mutt/1.4.2.3i
Subject: [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 WG, after several attempts, here is the most recent version of the new DNSOP charter to be discussed in tomorrow's WG session: ----------------------------------------------------------------------------- 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. Target audiences for those guidelines are zone administrators as well as software developers who provide tools for DNS zone administration or (default) server/resolver/validator configuration. The group will perform the following activities: 1) develop or review guidelines for chosing zone configuration parameters that affect inter-server or server-resolver communication, including but not limited to SOA RR parameters, TTL values, and glue information 2) develop or review guidelines for any DNSSEC specific operational parameters, such as key length or key validity periods 3) investigate and identify requirements of DNSSEC to the lower layers, both transport and network 4) develop or review operational guidelines that address the specifics of IPv4/v6 coexistence and transition 5) review the use of existing DNS frameworks (SRV, DDDS) in other protocols, especially focussing on operational consequences and scalability, most importantly when these frameworks are used in other wg's protocol proposals. 6) develop and review guidelines for resolver (stub and full) behaviour, including search path and timing issues as well as query strategies. 7) establish terminology and methodology for performance measurements of servers, resolvers or the service as such. 8) identify the requirements for a name server configuration and control protocol. To avoid overlap with the DNS Extensions working group, the DNSOP group will not change the on the wire behaviour of the DNS. Terminology issues will, where appropriate, be addressed in coordination with DNSEXT. ----------------------------------------------------------------------------- This version is expected to take into account the feedback given on the list and during the WG meetings in and after 2006 as well as recent additions to the set of active work items. -Peter _______________________________________________ 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