Slashdot Mirror

← Back to Stories (view on slashdot.org)

Microsoft Submits Email Caller ID to the IETF

Posted by michael on from the snake-oil-cheap dept.

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."

3 of 173 comments (clear)

  1. Why XML ? by Space+cowboy · · Score: 5, Interesting


    First off - I'm a great fan of XML - as a configuration specification format, it's great and I love it. I don't however think it's the solution to every problem - the BIND format is inherently non-XML, why not (if the proposal is to specify outgoing nameservers in the same way as we currently specify incoming nameservers) simply have an MO (Outbound :-) tag with virtually the same semantics as an MX tag (obviously a different payload, though, in the same way as MS propose) ?

    One of the reasons I love XML is that the configuration can later be extended without impacting on any parsers that only read version 1.0. Perhaps this *is* a good reason. Or perhaps it's a way of getting a standard out there that's easy to 'embrace and extend'. Paranoia? Perhaps.

    I do think it's a nice idea though, and it will stop a lot of spam - it will also make it far more valuable to 'own' the mailserver, with all of the implications thereof...

    Simon.

    --
    Physicists get Hadrons!
  2. The real problem is proprietary ownership of this by eric76 · · Score: 5, Insightful

    What we really need is a solution that is completely non-proprietary. A solution that no one company has any ability to control.

    Can you imagine what the network would be like today if Microsoft (or anyone else for that matter) had patents that allowed them absolute control over any of the common protocols (telnet, ftp, http, smtp, pop3, imap, ... )?

  3. Re:How does this benefit Microsoft's bottom line? by sjb21043 · · Score: 5, Insightful

    Lots of industry folks (MSFT, Dell, etc) have been reporting lately that a significant portion of their service calls come from either spam or spyware.

    Cutting service costs will definitely help the bottom line.