From brian@hursley.ibm.com Thu Feb 03 14:57:24 2000 Return-Path: Delivered-To: djb@cr.yp.to Received: (qmail 32743 invoked from network); 3 Feb 2000 14:57:23 -0000 Received: from mail-gw.hursley.ibm.com (194.196.110.15) by koobera.math.uic.edu with SMTP; 3 Feb 2000 14:57:23 -0000 Received: from sp3at21.hursley.ibm.com (sp3at21.hursley.ibm.com [9.20.45.21]) by mail-gw.hursley.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with ESMTP id OAA90900; Thu, 3 Feb 2000 14:55:55 GMT Received: from hursley.ibm.com (gsine02.us.sine.ibm.com [9.14.6.42]) by sp3at21.hursley.ibm.com (AIX4.2/UCB 8.7/8.7.3) with ESMTP id OAA23758; Thu, 3 Feb 2000 14:55:50 GMT Message-ID: <389996B6.BF217343@hursley.ibm.com> Date: Thu, 03 Feb 2000 08:54:46 -0600 From: Brian E Carpenter Organization: IBM X-Mailer: Mozilla 4.61 [en] (Win98; I) X-Accept-Language: en,fr MIME-Version: 1.0 To: "D. J. Bernstein" CC: iab@ISI.EDU Subject: Re: namedroppers mismanagement References: <20000203011127.23004.qmail@cr.yp.to> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Dan, You received a response to your complaint from the Internet Area Directors on January 26, and on January 27 you sent a repeat of your complaint to the IESG as a whole. Since you have not yet received a response from the IESG Chair to that complaint, it is premature to contact the IAB. We will not consider an appeal from you until the IESG has responded, if you find that response unsatisfactory. This is in accordance with the procedure described in BCP 9, section 6.5, especially 6.5.1. I should point out that the IESG is always overloaded with its regular work, and responses to appeals generally take one to two months to prepare, rather than a few days as you seem to expect. Regards Brian Carpenter IAB Chair "D. J. Bernstein" wrote: > > This is a complaint to the IAB about the management of the namedroppers > mailing list. I will wait a few days for a response. > > In short, to use the language of RFC 2026 section 6.5.1: Mismanagement > of the namedroppers mailing list is preventing the IETF DNSEXT working > group from adequately considering the views of its participants, and is > placing the quality and integrity of the working group's decisions in > jeopardy. > > As a concrete example, I would like DNSEXT to update RFC 2181 to > eliminate a security flaw that I explained on bugtraq; but I have been > unable to raise this issue on the namedroppers mailing list, because > Randy Bush has discarded my messages. Please see > > http://cr.yp.to/dnscache/namedroppers.html > > for details of this incident and several other incidents. > > I am not sure if this complaint is within the letter of RFC 2026 section > 6.5.1, which seems to focus primarily on previous WG decisions. However, > the WG chairs and the IESG have told me repeatedly that I'm following > the correct procedure. > > I have already attempted to resolve these problems with the WG chairs, > the ADs, and the IESG as a whole. The WG chairs and the ADs are > attempting to fix two problems: > > (1) Failure of the software to deliver messages immediately. > (2) Failure of Bush to notify authors of his censorship actions. > > However, the other problems remain, and are clearly not going to be > resolved by the WG chairs or the IESG. So I am sending this complaint to > the IAB. > > ---Dan