Re: Last Call: SMTP Message Submission to Proposed Standard

["William Allen Simpson" <wsimpson@xxxxxxxxxxxxxxx>]

> From: "Jack De Winter" <jack@xxxxxxxxxxxxxx>
> The above is a very small attempt at solving the problem.  It also does
> not solve the roving user problem.
>
> A good example of this is connecting up to the local area net at an
> IETF conference and getting assigned an IP address using DHCP.  Unless
> you enable relaying for your site's mail server for everyone at the
> conference, you cannot submit your mail.
>
> A better solution is to use SUBMIT and AUTH to verify what you are
> doing, who you are, and how you want the message handled.
>
This latest example really gets my goat!

I have never needed to enable relaying for everyone at any conference
while I've been roving.

Only the truly ignorant would try to tell me that the roving user
problem has not been solved, since I've devoted the better part of 15
years to the topic....

I've been using IPSec (RFC-1828) and IP-in-IP tunnelling (RFC-1853) for
more than 4 years to "verify" my connections, and it works just fine,
thankyouverymuch.  (Ignoring the silly changes recently made, of course.)

If you have not deployed IPSec, then how to do you expect us to believe
that you will have any better luck with your "new" protocols?

Why do we need yet another way to solve an already solved problem?

Anyway, I formally request that the title of the draft be changed, the
acronym SMTP be removed, and the remainder to "Message Relay Submission
Protocol (MRSP)".  This is not about SMTP (it just is similar with all
the warts), and it is not about all message submission (most messages
will not use this protocol); rather it is about relaying, and is only
marginally useful in a very limited context.

WSimpson@xxxxxxxxx
    Key fingerprint =  17 40 5E 67 15 6F 31 26  DD 0D B9 9B 6A 15 2C 32