This article makes it sound like Yahoo is pushing pretty hard with
domain keys.
http://www.businessweek.com/technology/content/jan2004/tc20040113_3442_tc047.htm
If the world decides to adopt Domain Keys, there are pros and cons. The
biggest pro is that we could then abandon SRS with a sigh of relief.
The biggest con is that everybody has to pay more in CPU and, possibly,
PKI certificates. Look at what a domain costs vs what an SSL cert costs.
There will be resistance to a proposal that creates king-makers.
The accreditation mechanism that has been proposed on this list is at
least open and structured so that the balance of power between sender
and receiver is equitable. SPF is completely compatible with S/MIME and
PGP; the only reason we haven't defined a mechanism for them is because,
well, nobody ask for it Shall we put one in?
The biggest concern for most users is a future where
- Yahoo will refuse to accept mail from domains that don't publish a DomainKey
- the DomainKey has to be rooted in a certificate chain owned by a
select group of registrars
- users won't be able to just publish their own public keys in DNS
And you still have to deal with the vast majority of domains who will
want to just keep sending mail as before. A designated sender scheme,
while less technically perfect, is degrees of magnitude less work to
implement.
Slashdot weighs in:
http://ask.slashdot.org/askslashdot/04/01/14/0158228.shtml?tid=111&tid=126&tid=95
-------
Sender Permitted From: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
Latest draft at http://spf.pobox.com/draft-mengwong-spf-02.9.4.txt
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname(_at_)©#«Mo\¯HÝÜîU;±¤Ö¤Íµø?¡