[ietf-dkim] Attempted summary, SSP again
hsantos at santronics.com
Fri Jan 27 10:05:36 PST 2006
----- Original Message -----
From: "Stephen Farrell" <stephen.farrell at cs.tcd.ie>
> In my mind this is a subtlety of SSP as it is now, (and like John L
> hinted maybe), I could see the WG consensus landing on either side.
It is unfortuate John gets to lick his chops on this. Just because he
didn't understand the specs, doesn't mean no one else does either.
It causes alot of delays and it seems alot of time was wasted that ALL
IMPUT was ignored.
We need to make sure that PEOPLE that do understand the specs and are
not getting wrong impressions.
We are talking about an EXCLUSIVE POLICY, the "OH equal !" policy for
the layman impaired.
This is the biggest, the numero UNO benefit of DKIM. As it is written,
Mail must be signed by the original domain.
Mail must NEVER be signed by a 3rd party.
This is extremely fundamental to the protocol. If this interpretation
is wrong, I would like to KNOW exactly with this OH equal ! means.
Was Michael saying that a 3rd party service can masquarade itself as the
Earl, Arvel, and I, including Mike all touched based with this about 6+
months ago. But as possible new policies or changes to the specs. As
it is written now, it is exclusive OA Domain only, No 3rd party policy.
> I don't see why this needs to be finalised now, but why don't you
> create an issue for it, that way we *will* get back to it.
I could do that, but this was already spelled out many months ago.
> The important thing to note though is that stuff like this will
> change in SSP before it becomes an RFC. AFAIK, there's never been
> any similar I-D that didn't undergo similar changes.
> So, I'm afraid you do have to wait,
For what, the FINAL RFC? You are kidding?
I can't even get a common courtesy of a clarification and confirmation
of the exclusive (O=!) policy?
Hector Santos, Santronics Software, Inc.
More information about the ietf-dkim