Microsoft Submits Email Caller ID to the IETF
NetWizard writes "Following on the heels of Yahoo submitting DomainKeys, Microsoft decided to submit their "Caller ID" anti-spam proposal as a draft to the IETF. This proposal tries to tie in IP addresses to the domain of the sender just like SPF does. To make things even more interesting, looks like SPF and MSFT's Caller-ID proposals are merging. On a related note, Yahoo submitted an IPR disclosure for DomainKeys to the IETF."
Maybe they feel kind of guilty since the majority of spam is relayed through trojaned windows boxes? :-)
Microsoft expects that when certain folks start needing new features
that are not expressible in v=spf1, they can publish their records
in XML and all the clients out there will be able to read those
records.
"certain folks" like Outlook developers, maybe?
"They've already taken a stab at the video game industry, remeber? "
So... you're afraid Microsoft will take over email, but you've already noticed they can't make a monopoly out of everything they touch. I can't tell if you're karma whoring or if you've written a rather amusing satire of the way a lot of people here on Slashdot behave.
"Derp de derp."
Linux is very user friendly. It's also very fussy about who it makes friends with.
Good, inexpensive web hosting
And then they sell telemarketers the privilege of having that software block selectively reinstated, and THEN (get ready to really feel used), they recently introduced a new "service" that identifies all callers (i.e., removes the selective blocking), which you can purchase for a nominal monthly fee. I hear the internal codename for this "service" is "Guido." Don't you feel safer with all this "Protection" they're offering you?
Today's Sesame Street was brought to you by the number e.