Re: [Asrg] C/R Interworking Framework

Yakov Shafranovich <research@solidmatrix.com> Thu, 05 June 2003 02:54 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 WAA23457 for <asrg-archive@odin.ietf.org>; Wed, 4 Jun 2003 22:54:17 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h552rsa11767 for asrg-archive@odin.ietf.org; Wed, 4 Jun 2003 22:53:54 -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 h552rrB11764 for <asrg-web-archive@optimus.ietf.org>; Wed, 4 Jun 2003 22:53:53 -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 WAA23434; Wed, 4 Jun 2003 22:53:46 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Nkr7-0002Ur-00; Wed, 04 Jun 2003 22:51:57 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Nkr6-0002Uo-00; Wed, 04 Jun 2003 22:51:56 -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 h552q8B11666; Wed, 4 Jun 2003 22:52:08 -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 h552p7B11646 for <asrg@optimus.ietf.org>; Wed, 4 Jun 2003 22:51:08 -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 WAA23374 for <asrg@ietf.org>; Wed, 4 Jun 2003 22:51:00 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19NkoR-0002U7-00 for asrg@ietf.org; Wed, 04 Jun 2003 22:49:11 -0400
Received: from 000-237-424.area5.spcsdns.net ([68.27.166.189] helo=68.27.166.189 ident=trilluser) by ietf-mx with smtp (Exim 4.12) id 19NkoP-0002TU-00 for asrg@ietf.org; Wed, 04 Jun 2003 22:49:10 -0400
Message-Id: <5.2.0.9.2.20030604224953.00b41848@solidmatrix.com>
X-Sender: research@solidmatrix.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
To: Vernon Schryver <vjs@calcite.rhyolite.com>, asrg@ietf.org, Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
From: Yakov Shafranovich <research@solidmatrix.com>
Subject: Re: [Asrg] C/R Interworking Framework
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-MimeHeaders-Plugin-Info: v2.03.00
X-GCMulti: 1
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: Wed, 04 Jun 2003 22:49:54 -0400

At 06:01 PM 6/4/2003 -0600, Vernon Schryver wrote:

> > From: Yakov Shafranovich <research@solidmatrix.com>
>
> > ...
> > However, if we are defining an SMTP process for CRI protocols, can we use
> > the VRFY command as a part of an ESMTP extension?
>
>What about deployment and adoption rates?  Do you want it to work
>even with MTAs not running your new protocol?
>In other words, do you want it to work only in theory or to also have a
>glimmer of a hope of working in the real Internet within the next 20 years?

As I pointed out before in a posting to Eric Dean, my vision is a 
multi-stage CRI protocol. The basic protocol would use RFC 2822 headers and 
human-readable email, which would be compatible with current MTAs. As C/R 
systems become more common, they can negotiate to use the other parts of 
the protocol such as an ESMTP extension or MIME fields. An extension 
mechanism would be in place where the protocol can be extended to support 
things like PKI, hash cash, etc. The VRFY command would be part of that 
ESMTP extension which will be used by C/R systems that want to, and not 
used by existing MTAs. Existing MTAs will start off by supporting the basic 
protocol or if they want the other parts.

Additionally, deployment and adoption rates is something that should be 
considered in more detail (this would be something that Eric Brunner can 
help us with). According to D. J. Berstein's SMTP statistics 
(http://cr.yp.to/surveys/smtpsoftware6.txt), the following breakdown of 
major MTAs was present on the Internet in 2001 (out of 958):

401/958 41.85%          UNIX Sendmail
176/958 18.37%          Windows Microsoft Exchange or IIS SMTP
167/958 17.43%  UNIX qmail
57/958  5.9%            Windows Ipswitch IMail

These four accounted for about 84% of all MTAs with the other MTAs were 1% 
or less. Of these, qmail and sendmail account for 59.28% of all MTAs, with 
the Windows ones accounting for the other 24.27%.

IF a CRI protocol is implemented and both qmail and sendmail support it, 
that would mean that a sizable majority of the Internet would support it. 
If Microsoft jumps in, that would increase the effect. The question 
remains, taking the impact of qmail and sendmail, and the propagation rates 
for admins installing the newest versions, how long would deployment take?

Yakov




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