Been trying to avoid it but ....
my understanding was that i=author d=signer
i=foobar.coxhosted.com d=dkim.signer.coxmail.com and that was how 3rd party
signing was going to work
Bill Oxley
Messaging Engineer
Cox Communications, Inc
404-847-6397
-----Original Message-----
From: ietf-dkim-bounces(_at_)mipassoc(_dot_)org on behalf of Dave CROCKER
Sent: Wed 1/28/2009 6:53 PM
To: John R. Levine
Cc: ietf-dkim(_at_)mipassoc(_dot_)org
Subject: Re: [ietf-dkim] DKIM does not identify senders, and we have big
semantic problems
John R. Levine wrote:
Gee, how many ways are there to say that i= doesn't identify the user?
The i= field doesn't do that. DKIM doesn't identify individuals, only
domains.
John,
Oh boy.
Your statement is not correct.
The spec says that it *does* identify a user.
It does not say the identification is an email address.
It does not say that the user is the author.
It does not say that anyone other that the creator of the identification
can
parse and comprehend the identifier.
But it does say that it is the user who the signing was done "on behalf of".
d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html