ietf-mxcomp
[Top] [All Lists]

Re: FW: Drive Towards Consensus

2004-06-22 07:50:16

On Tue, Jun 22, 2004 at 07:34:30AM -0400, Hector Santos wrote:
| > > Message Types Tied to Individual Mechanisms
| > > ------- ----- ---- -- ---------- ----------
| > >
| > > Many domains send both non-bulk and bulk mail, generally through very
| > > different parts of their organization.  It may be useful to have
| > > annotations on an SPF mechanism that describe the kinds of mail they
| > > send.  For example:
| > >     v=spf1 +mx/bulk +indirect:comcast.com/nonbulk -all
| >
| > Again, I see this as a case of being "not useful because no one will
| > believe unverifiable claims."
| 
| Jim, I agree with Wayne.  I would not support MARID domain defined
| reputation lookup.   In my opinion, reputation lookups should  be a
| server-side sysop defined factor because sysops will trust thier setup.  Not
| the remote domain. In our current design implementation, sysop defined
| reputation lookups is done first before any LMAP method lookup.
| 
| I would suggest that Accreditation Service Bureaus (ASB) trying to "buy"
| into the MARID concept by augmenting into the validation scheme, are
| probably only going to work (feasible) as a "permit" concept.  For
| illustration purposes only, the domain policy can look like this:
| 
|          (whatever format)  MARID=v1.0 ...  .... +accred:XYZ-######  -all

I agree that assertions of rate limiting, etc. should be
made by accreditation agencies, not by the sender domains.

I say this based on two principles: agency and matching.

Agency means that if the assertions are made by the
accreditor, a self-policing dynamic keeps both parties
honest.  The domain wants to do the right thing or lose its
accreditation; the accreditor wants to make sure the domain
is living up to its standards or it loses its reputation.

Matching means that if the assertions are made by the sender
domain, without preexisting trust, there is no way for a
reputation services to evaluate those assertions.

At http://www.isipp.com/codelist.php we see that accreditors
have already thought through these issues and have created
exactly the kind of data structure that we allude to above.