RE: [Asrg] seeking comments on new RMX article

"Eric D. Williams" <eric@infobro.com> Mon, 05 May 2003 16:13 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 MAA06730 for <asrg-archive@odin.ietf.org>; Mon, 5 May 2003 12:13:47 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h45GLpK14135 for asrg-archive@odin.ietf.org; Mon, 5 May 2003 12:21:51 -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 h45GLp814132 for <asrg-web-archive@optimus.ietf.org>; Mon, 5 May 2003 12:21:51 -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 MAA06721; Mon, 5 May 2003 12:13:17 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Cicd-0006ny-00; Mon, 05 May 2003 12:15:23 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Cicd-0006nv-00; Mon, 05 May 2003 12:15:23 -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 h45GFl813861; Mon, 5 May 2003 12:15:47 -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 h45GBO813592 for <asrg@optimus.ietf.org>; Mon, 5 May 2003 12:11:24 -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 MAA06402 for <asrg@ietf.org>; Mon, 5 May 2003 12:02:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19CiSX-0006jo-00 for asrg@ietf.org; Mon, 05 May 2003 12:04:57 -0400
Received: from black.infobro.com ([63.71.25.39] helo=infobro.com) by ietf-mx with smtp (Exim 4.12) id 19CiSR-0006j2-00 for asrg@ietf.org; Mon, 05 May 2003 12:04:51 -0400
Received: from red (unverified [207.199.136.153]) by infobro.com (EMWAC SMTPRS 0.83) with SMTP id <B0002379376@infobro.com>; Mon, 05 May 2003 12:04:01 -0400
Received: by localhost with Microsoft MAPI; Mon, 5 May 2003 12:04:05 -0400
Message-ID: <01C312FE.6CEADBB0.eric@infobro.com>
From: "Eric D. Williams" <eric@infobro.com>
To: 'Dave Crocker' <dhc@dcrocker.net>, Mike Rubel <asrg@mikerubel.org>
Cc: "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 11:53:57 -0400
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Perhaps the issue here is not mail transport at all.  In face I think what is 
at issue is gaining access to an MTA and not the mail transport protocol at 
all.  Let's say mobile user 'A' wants to send eMail.  She has multiple methods 
for accessing the MTA but only one mail transport.  The mobile user MAY 
leverage some other 'session transport' protocol to gain access to her 
applications MTA transport protocol.

If this is a valid scenario then a mobile user MAY not have to utilize 
'arbitrary' hosts in the 'void' to enable mail transport.  I am not clear why 
but the use of arbitrary disturbs me in this context I would be more 
comfortable with "assigned" or "designated."  Although I do understand why the 
term 'arbitrary' is apropos.

-e

On Sunday, May 04, 2003 9:56 PM, Dave Crocker [SMTP:dhc@dcrocker.net] wrote:
> Mike,
>
>
> AD>> Are there NO other methods which a mobile user may use to send mail?
>
> MR> What about VPN?  What about stunnel?
>
> those are not mail protocols.
>
> MR>   What about smtp-auth?
>
> smtp-auth is an option to smtp.  so, it is smtp.
>
> MR>   What about
> MR> Courier's "outbox" for IMAP over SSL?
>
> I don't know what you are referring to, but it is not an Internet
> standard for posting mail.
>
>
> MR>   Heck, what about ssh tunnels?
>
> not a mail protocol.
>
>
> MR> Perhaps I'm not understanding your objection?
>
> possibly.
>
>
>
> d/
> --
>  Dave Crocker <mailto:dcrocker@brandenburg.com>
>  Brandenburg InternetWorking <http://www.brandenburg.com>
>  Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>
>
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg
_______________________________________________
Asrg mailing list
Asrg@ietf.org
https://www1.ietf.org/mailman/listinfo/asrg