I tend to agree. I would love to see DK use an s/mime type
infrastructure given that so many email clients and servers do know
s/mime to come extent. Developers know it too. Might help to speed adoption.
mengwong(_at_)dumbo(_dot_)pobox(_dot_)com wrote:
Many people agree that crypto is part of the long-term picture of email.
S/MIME was originally designed as end-user to end-user infrastructure.
Recently a domain-to-domain version has been announced:
http://www.opengroup.org/messaging/sm/smgdev/doc.tpl?CALLER=index.tpl&gdid=4657
But it still looks heavyweight compared to Yahoo DomainKeys.
Wouldn't it be great if S/MIME could, instead of requiring a
cumbersome and O(n^2) initial key exchange between domains, make use
of opportunistic "oh, look, and here's the cert in DNS"?
Oh, and instead of "cert" read "self-signed public key".
Then maybe we'd get the benefits of the Yahoo DK infrastructure but
leverage the existing S/MIME base.
-------
Sender Policy Framework: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
Latest draft at http://spf.pobox.com/spf-draft-200404.txt
Wiki: http://spfwiki.infinitepenguins.net/pmwiki.php/SenderPermittedFrom/
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
--
Carl Hutzler
Director, AntiSpam Operations
America Online Mail Operations
cdhutzler(_at_)aol(_dot_)com
703.265.5521 work
703.915.6862 cell