Re: [dnsext] Reminder: draft charter was posted for discussion

Paul Vixie <vixie@isc.org> Thu, 08 July 2010 02:00 UTC

Return-Path: <owner-namedroppers@ops.ietf.org>
X-Original-To: ietfarch-dnsext-archive@core3.amsl.com
Delivered-To: ietfarch-dnsext-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B36313A69ED; Wed, 7 Jul 2010 19:00:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 XXTyKZA8X8ln; Wed, 7 Jul 2010 19:00:26 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 97BCD3A6827; Wed, 7 Jul 2010 19:00:26 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1OWgJz-000NRF-Hz for namedroppers-data0@psg.com; Thu, 08 Jul 2010 01:54:39 +0000
Received: from [2001:4f8:3:bb:230:48ff:fe5a:2f38] (helo=nsa.vix.com) by psg.com with esmtps (TLSv1:CAMELLIA256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <vixie@vix.com>) id 1OWgJx-000NQl-0Z for namedroppers@ops.ietf.org; Thu, 08 Jul 2010 01:54:37 +0000
Received: from nsa.vix.com (localhost [127.0.0.1]) by nsa.vix.com (Postfix) with ESMTP id A5D6AA1031 for <namedroppers@ops.ietf.org>; Thu, 8 Jul 2010 01:54:36 +0000 (UTC) (envelope-from vixie@nsa.vix.com)
From: Paul Vixie <vixie@isc.org>
To: namedroppers@ops.ietf.org
Subject: Re: [dnsext] Reminder: draft charter was posted for discussion
In-Reply-To: Your message of "Mon, 05 Jul 2010 14:06:41 -0400." <20100705180640.GF49823@shinkuro.com>
References: <20100705180640.GF49823@shinkuro.com>
X-Mailer: MH-E 8.1; nil; GNU Emacs 23.1.1
Date: Thu, 08 Jul 2010 01:54:36 +0000
Message-ID: <43030.1278554076@nsa.vix.com>
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-ID: <namedroppers.ops.ietf.org>
List-Unsubscribe: To unsubscribe send a message to namedroppers-request@ops.ietf.org with
List-Unsubscribe: the word 'unsubscribe' in a single line as the message text body.
List-Archive: <http://ops.ietf.org/lists/namedroppers/>

> Date: Mon, 5 Jul 2010 14:06:41 -0400
> From: Andrew Sullivan <ajs@shinkuro.com>
> 
> This is a reminder that we posted some time ago a new draft charter
> for the WG.  We've had very little feedback on it.  ...
> 
> I attach it again here for your convenience.  ...
> 
> This topic will take a considerable chunk of the time we have
> scheduled in Maastricht.  The charter represents our commitments to
> the rest of the IETF.
> 
> If you have opinions on it, it would be nice to hear them.  ...

with the understanding that there's a range of possible views as to the
desireability of continued evolution in a mature deployed protocol, here
are mine.  i apologize to our WGC's for the lateness of this reply.

+---
| DRAFT charter for DNSEXT, 2010-05-28.  SUBJECT TO CHANGE
...
| The WG will consider work in the following areas:
| 
| * DNSSEC and TSIG/TKEY algorithm maintenance
| * Mechanisms that complement, or are alternatives to, TSIG and SIG(0)

since TSIG and SIG(0) are both last-mile (recursive to stub) protocols,
perhaps this bullet item would be clearer if it was amended to say:

* Last mile (recursive to stub) mechanisms that complement, or are
  alternatives to, TSIG and SIG(0); specifically including stub DNSSEC
  validation and protocol extensions to support same.

| * Hardening DNS protocol and providing guidance to implementers

the word "hardening" is at best unclear in this context.  perhaps this can
be reworded as follows:

* Improving defensibility and resiliency of DNS protocol agents by analyzing
  possible buffer overrun/underrun conditions and offering implementation
  guideance on test coverage for same.

| * Improving DNS zone synchronization mechanisms 

i think this is too specific, and should be reworded as follows:

* Improving DNS zone and DNS server configuration synchronization mechanisms 

...
| Goals and Milestones:
...
+---

i have no other comments.