RE: [Asrg] seeking comments on new RMX article

"Eric D. Williams" <eric@infobro.com> Mon, 05 May 2003 22:39 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 SAA20262 for <asrg-archive@odin.ietf.org>; Mon, 5 May 2003 18:39:59 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h45MmBe10633 for asrg-archive@odin.ietf.org; Mon, 5 May 2003 18:48:11 -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 h45MmB810630 for <asrg-web-archive@optimus.ietf.org>; Mon, 5 May 2003 18:48:11 -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 SAA20255; Mon, 5 May 2003 18:39:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CoeN-0001XQ-00; Mon, 05 May 2003 18:41:35 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19CoeM-0001XN-00; Mon, 05 May 2003 18:41:34 -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 h45Mk7810479; Mon, 5 May 2003 18:46:07 -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 h45McZ810016 for <asrg@optimus.ietf.org>; Mon, 5 May 2003 18:38:35 -0400
Received: from infobro.com (black.infobro.com [63.71.25.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA19897 for <asrg@ietf.org>; Mon, 5 May 2003 18:29:53 -0400 (EDT)
Received: from red (unverified [207.199.136.153]) by infobro.com (EMWAC SMTPRS 0.83) with SMTP id <B0002379966@infobro.com>; Mon, 05 May 2003 18:30:48 -0400
Received: by localhost with Microsoft MAPI; Mon, 5 May 2003 18:30:52 -0400
Message-ID: <01C31334.759A27D0.eric@infobro.com>
From: "Eric D. Williams" <eric@infobro.com>
To: "asrg@ietf.org" <asrg@ietf.org>
Subject: RE: [Asrg] seeking comments on new RMX article
Organization: Information Brokers, Inc.
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
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: Mon, 05 May 2003 16:50:28 -0400
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Monday, May 05, 2003 1:30 PM, Vernon Schryver 
[SMTP:vjs@calcite.rhyolite.com] wrote:
> > From: "Eric D. Williams" <eric@infobro.com>
>
> > Is RMX a proposed change to existing Internet services OR, 1) a proposed
> > extension to/of existing services? 2) an additional use of existing
> > services?
> > 3) a new protocol?
> >
> > My read is that it is #2 above.  The RMX proposal do not seem to constitute
> > a
> > change to existing services but rather a leveraging of those services to
> > achieve a specific goal.  It also seems to be application specific as
> > opposed
> > to a networking protocol.
>
> Yes, but what is your point?
>   - Have you noticed much use of DNSSEC?
>   - How about some of the major improvements in the not so recent
>      update to the HTTP protocol?
>   - SMTP-TLS has been available for years, but this mailing list is not
>      using it.  Do the SMTP servers or clients near you use it?
>
> Then there are RIPv2, IPv6, TCP-SACK, and TCP-ENS.  Even TCP
> slow-start took most of 10 years, and that was in the old days when
> the net was tiny and well controlled.

No internet protocol started with ubiquity AFAIK, some have not been adopted 
after being 'standardized' some evolved into de-facto standards before IETF/ISO 
(insert acronym) work was completed.  I do not think that these are valid 
measures of the viability of a proposal.  Also successful adoption IMHO is 
based on whether something 'gives the people what they want' and not 
necessarily 'what they need' or 'what they asked for'.

The paragraph you cite was inserted based upon Dave's post concerning changes 
to Internet services.  My point is I don't see the RMX proposal as a change to 
Internet services.  DNSSEC and SMTP-TLS are along the same lines.  Recall my 
opinion is that it may be 'what people need' or 'what they asked for' but is it 
'what they want'?  I think implementation difficulty also plays into the mix 
(on that I think we all agree).

> As the saying goes, "In theory there is no difference between theory
> and practice, but in practice there is."
>
> Would those who assure us that deploying RMX or any anti-spam scheme
> could be done in fewer than 10 years tell us about their credentials
> for making their authoritative sounding statements?  What protocol
> have they been involved in that was deployed as fast as their spam
> system would be?

I don't think any of us could boldly make such a claim as an individual, but 
surely that is not a criteria for evaluation of a proposal.  Achieving 
convergence and interoperation of a specification can be onerous (LDAP) or 
trivial (RFC822).

-e
_______________________________________________
Asrg mailing list
Asrg@ietf.org
https://www1.ietf.org/mailman/listinfo/asrg