Re: How IETF treats contributors
Dean Anderson <dean@av8.com> Wed, 01 September 2004 05:27 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07944; Wed, 1 Sep 2004 01:27:10 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2NgR-0000gt-0s; Wed, 01 Sep 2004 01:29:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2Nch-0005gy-Gh; Wed, 01 Sep 2004 01:25:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C2NbA-0005Mm-Vs for ietf@megatron.ietf.org; Wed, 01 Sep 2004 01:23:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07770 for <ietf@ietf.org>; Wed, 1 Sep 2004 01:23:56 -0400 (EDT)
Received: from cirrus.av8.net ([130.105.36.66]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C2NdH-0000eF-UE for ietf@ietf.org; Wed, 01 Sep 2004 01:26:09 -0400
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66]) (authenticated bits=0) by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i815NNTT011347 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 1 Sep 2004 01:23:24 -0400
Date: Wed, 01 Sep 2004 01:23:23 -0400
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: Paul Vixie <vixie@vix.com>
In-Reply-To: <g34qmjjkgw.fsf@sa.vix.com>
Message-ID: <Pine.LNX.4.44.0409010043160.9376-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Score: 2.7 (++)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Cc: ietf@ietf.org
Subject: Re: How IETF treats contributors
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 2.7 (++)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
"Vixie trusts himself"--Yet another self-authenticated claim. It is an important question "who to trust". I would trust people who don't lie, who don't associate with liars, and who don't make questionable changes to critical infrastructure without appropriate technical discussion. People who don't have a history of trust violations: 1) Deployment of Anycast to DNS Root servers without discussion on any IETF DNS list. The other Root operators no doubt trusted Vixie to discuss it with others. He didn't. 2) Alteration of the BIND 9 AXFR implementation so that it no longer interoperates with other DNS Nameserver implmentations. This was done without discussion. Well after deploying Bind 9, Vixie finally came to the DNSEXT group to ask for an alteration to the AXFR specification. This was the first discussion of the change. The proposed alteration to AXFR was rejected. 3) Associates with known disreputable people including court-proven liars such Alan Brown. Mr. Vixie tells people falsely that Av8 Internet IP Address blocks are hijacked. This is an intentional, willful false claim: it isn't a mistake, or an oversight, or a "false positive". Vixie tries to avoid legal responsibility by a claim of being operated from Australia. 4) Used the MAPS RBL to block non-spam email from Exactis, resulting in the Exactis V. MAPS suit. This was a violation of the trust of those who were misled to believe that MAPS was an anti-spam list rather than a personal revenge list. Vixie still asserts that blacklists and ISPs can block email from anyone for any reason, misleading people. This is just the short list. --Dean On 31 Aug 2004, Paul Vixie wrote: > Nick.Carter@think3.com ("Nick Carter") writes: > > > ... You could contest it saying it was an excrescence of Vixie's work, > > but the details do not exist in Vixie's work. As noted with Dean, Vixies > > work is implausible and therefore credit should not be given. All work > > submitted should be punctilio and of protocol. > > of the three of us (you, me, dean) i have a pretty clear idea who i'd trust > the most to advise anybody about what can or cannot be done in SMTP or DNS. > > however, i'm quite interested in feedback as to the plausibility of miller's > idea, which i expressed at <http://sa.vix.com/~vixie/mailfrom.txt>. thanks! > _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- How IETF treats contributors Hadmut Danisch
- Re: How IETF treats contributors Ted Hardie
- Re: How IETF treats contributors Paul Vixie
- Re: How IETF treats contributors Marc Blanchet
- Re: How IETF treats contributors Dean Anderson
- Re: How IETF treats contributors Dean Anderson
- Re: How IETF treats contributors Ted Hardie
- Re: How IETF treats contributors Dean Anderson
- Re: How IETF treats contributors william(at)elan.net
- RE: How IETF treats contributors Christian Huitema
- Re: How IETF treats contributors Dean Anderson
- Re: How IETF treats contributors John Day
- Re: How IETF treats contributors Clint Chaplin
- RE: How IETF treats contributors Thomas Gal
- RE: How IETF treats contributors Nick Carter
- Re: How IETF treats contributors Olaf M. Kolkman
- RE: How IETF treats contributors Scott Bradner
- Re: How IETF treats contributors Vernon Schryver
- Re: How IETF treats contributors Paul Vixie
- Re: How IETF treats contributors Paul Vixie
- Re: How IETF treats contributors Hadmut Danisch
- Re: How IETF treats contributors Hadmut Danisch
- Re: How IETF treats contributors Hadmut Danisch
- RE: How IETF treats contributors ned.freed
- Re: How IETF treats contributors Dean Anderson
- Re: How IETF treats contributors Dean Anderson
- Re: How IETF treats contributors william(at)elan.net
- Re: How IETF treats contributors Harald Tveit Alvestrand
- Re: How IETF treats contributors Nathaniel Borenstein
- Re: How IETF treats contributors ned.freed
- Re: How IETF treats contributors grenville armitage