Re: Update to Submit RFC

Chris,

CN> We really need to put a nail in the coffin of unauthenticated mail submission.

There are a number of things I like about the path you are going down,
with the proposed changes to Submit, although I do have comments about
some of the details.

However, what is missing is a clear statement of the problems that are
being solved.  We can debate the solution details after we are clear
about the goals.

By itself, there is no reason to have submit be separate from smtp
relaying.  The justification for making the split was to make it
possible to have posting diverge.  To date, there has not been
interesting divergence.  When we define a set of posting features that
solve compelling needs, folks will start using it.

1. Client authentication

As you note, this is a clear and present and strong requirement.  I
agree.  It is also something that is fundaementally different for
posting, compared with relaying.

As you note, we need a single, default implementation choice for
achieving this, no matter what alternatives might also be supported.


2. Binary

Sorry, but I don't see this as compelling.  Nice, perhaps, but not
something that will drive the adoption of the changes.


3.  ???

Uh oh.  I don't see any other pressing requirements that are being
solved.

We need more problems that are being solved by this upgrade.  I'd
suggest some, but can't think of any that are compelling.


d/
--
 Dave Crocker <mailto:[email protected]>
 Brandenburg InternetWorking <http://www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>