IETF Logo Mail Archive

Re: [Asrg] seeking comments on new RMX article

Vernon Schryver <vjs@calcite.rhyolite.com> Tue, 06 May 2003 17:03 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29503 for <asrg-archive@odin.ietf.org>; Tue, 6 May 2003 13:03:43 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h46HCIM09479 for asrg-archive@odin.ietf.org; Tue, 6 May 2003 13:12:18 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h46HCH809476 for <asrg-web-archive@optimus.ietf.org>; Tue, 6 May 2003 13:12:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29490; Tue, 6 May 2003 13:03:13 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19D5sU-0000cD-00; Tue, 06 May 2003 13:05:18 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19D5sU-0000cA-00; Tue, 06 May 2003 13:05:18 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h46H4b808207; Tue, 6 May 2003 13:04:37 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h46H1w808049 for <asrg@optimus.ietf.org>; Tue, 6 May 2003 13:01:58 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29198 for <asrg@ietf.org>; Tue, 6 May 2003 12:52:53 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19D5iV-0000Y7-00 for asrg@ietf.org; Tue, 06 May 2003 12:54:59 -0400
Received: from calcite.rhyolite.com ([192.188.61.3]) by ietf-mx with esmtp (Exim 4.12) id 19D5iT-0000Y4-00 for asrg@ietf.org; Tue, 06 May 2003 12:54:58 -0400
Received: (from vjs@localhost) by calcite.rhyolite.com (8.12.9/8.12.9) id h46Gtj8c004430 for asrg@ietf.org env-from <vjs>; Tue, 6 May 2003 10:55:45 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200305061655.h46Gtj8c004430@calcite.rhyolite.com>
To: asrg@ietf.org
Subject: Re: [Asrg] seeking comments on new RMX article
References: <200305061020.57273@grx>
Sender: asrg-admin@ietf.org
Errors-To: asrg-admin@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/asrg/>
Date: Tue, 06 May 2003 10:55:45 -0600

> From: David Walker <antispam@grax.com>

> The reason RMX records haven't made a big impact to date is the lack of a 
> standard. ...

The idea that writing and publishing a standard as an RFC causes
a protocol or other idea to be used is quite popular.  Many people have
the illusion that soon after an RFC is written, the Internet starts
using it.  That idea is quite wrong.  Publishing a standard has very
little effect on whether a protocol or procecure is ever used.

The purpose of the IETF is to encourage interoperable implementations.
The IETF tends to reduce competition between competing standards, but
it is almost useless for getting a standard used.

However, feel free to see if I'm wrong.  You can get an RFC defining
whatever you like as an RMX protocol published within a month.  You
don't need from permission me, Paul Judge, or anyone else but the RFC
Editor, and they are quite liberal.  If I'm wrong, in less time than
this mailing list has existed, RMX would be fixing lots of spam.


Vernon Schryver    vjs@rhyolite.com
_______________________________________________
Asrg mailing list
Asrg@ietf.org
https://www1.ietf.org/mailman/listinfo/asrg

v2.23.0 | Report a Bug | By Email