RE: [ietf-dkim] The problem with sender policy

"william(at)elan.net" <william@elan.net> Sun, 06 August 2006 01:59 UTC

Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G9XvD-0002Qu-2b for ietf-dkim-archive@lists.ietf.org; Sat, 05 Aug 2006 21:59:19 -0400
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G9XvB-0002Nv-Li for ietf-dkim-archive@lists.ietf.org; Sat, 05 Aug 2006 21:59:19 -0400
Received: from sb7.songbird.com (sb7.songbird.com [127.0.0.1]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k761sgVT005403; Sat, 5 Aug 2006 18:54:42 -0700
Received: from sokol.elan.net (sokol.elan.net [216.151.192.200]) by sb7.songbird.com (8.12.11.20060308/8.12.11) with ESMTP id k761sbOr005389 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-dkim@mipassoc.org>; Sat, 5 Aug 2006 18:54:37 -0700
Received: from sokol.elan.net (sokol [127.0.0.1]) by sokol.elan.net (8.13.1/8.13.1) with ESMTP id k761s4EE007940; Sat, 5 Aug 2006 18:54:04 -0700
Received: from localhost (william@localhost) by sokol.elan.net (8.13.1/8.13.1/Submit) with ESMTP id k761s3Uc007937; Sat, 5 Aug 2006 18:54:03 -0700
X-Authentication-Warning: sokol.elan.net: william owned process doing -bs
Date: Sat, 05 Aug 2006 18:54:03 -0700
From: "william(at)elan.net" <william@elan.net>
To: John L <johnl@iecc.com>
Subject: RE: [ietf-dkim] The problem with sender policy
In-Reply-To: <20060805212005.D17637@simone.iecc.com>
Message-ID: <Pine.LNX.4.62.0608051828490.11690@sokol.elan.net>
References: <BB621D48443A854A89D86528F915864C0215F77B@CATL0MS02.corp.cox.com> <20060805212005.D17637@simone.iecc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Songbird: Clean, Clean
Cc: Bill.Oxley@cox.com, ietf-dkim@mipassoc.org
X-BeenThere: ietf-dkim@mipassoc.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF DKIM Discussion List <ietf-dkim.mipassoc.org>
List-Unsubscribe: <http://mipassoc.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=unsubscribe>
List-Archive: <http://mipassoc.org/pipermail/ietf-dkim>
List-Post: <mailto:ietf-dkim@mipassoc.org>
List-Help: <mailto:ietf-dkim-request@mipassoc.org?subject=help>
List-Subscribe: <http://mipassoc.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=subscribe>
Sender: ietf-dkim-bounces@mipassoc.org
Errors-To: ietf-dkim-bounces@mipassoc.org
X-SongbirdInformation: support@songbird.com for more information
X-Songbird-From: ietf-dkim-bounces@mipassoc.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002

On Sat, 5 Aug 2006, John L wrote:

>> In no way does accreditation=DKIM

But policy records are in a way. Lets look at it in general -
policy record is just a statement of what sender believes to
be true about their email system setup and how receiver can
use the email..

Accreditation is basically the same thing but the difference
is that its not sender directly saying it but that sender asked
(paid) some other party to provide this information to the
public (and depending on how good accreditation service is
they might go through some sort of checks to verify its true;
in the end its still that accreditation service has been paid
by the sender and is thus not true neutral party no matter
what they say). Another slight difference is that accreditation
focuses more on the "use of the email" rather then email system
setup. Reputation is actually highly similar too but in that
case it only answers about "use of the email" from perspective
of 3rd party that has [hopefully] nothing to do with the sender.

We could in fact have a system/protocol that accommodates all of
these at once. The difference would be that for "policy record"
the answer would be found directly at the service run by the
sender (or whoever appears to be the sender in case you need
to check on that). In the case of accreditation you'd ask some
3rd party chosen by the sender where as with reputation you'd
ask 3rd party chosen by the receiver. The questions asked could
all actually be the same and could even be if that party always
sends signed email.

As far as example given by John [FDIC and banks], I think its
special corner-case because banks members of FDIC so what
FDIC does is answer a question if they are member or not
and there is no doubt that FDIC is only place to reliably
find this out. However if a bank were to have paid some
other 3rd party to say this bank belongs to FDIC, I'd not
believe it much more then if bank itself said that directly
(in fact lawyers would say it should be believed less).

-- 
William Leibzon
Elan Networks
william@elan.net
_______________________________________________
NOTE WELL: This list operates according to 
http://mipassoc.org/dkim/ietf-list-rules.html