However, for ISPs especially, the spam problem is not fully solved by any means. They still spend a lot of money on R&D in a cat-and-mouse game with spammers, as well as the infrastructure investment to deal with the inbound volume that gets rejected at or near the gateway.

Identity management consists of a set of discrete products that also have elements of overlapping and common functionality: workflow a roles framework; interfaces for self-service and delegated administration, and a directory. Large vendors sought to build portfolios that would integrate by sharing these services, which simplifies their coordinated use by customers.

I don't that happening this year, I don't see it happening next year or the year after that--that leaves 2009, and I'll leave that one open. There are a lot of issues, but basically it boils down to trust and antitrust.

A lot of people are just opposed to the idea of being charged for something that they believe is fundamental infrastructure.

The notion is to [unify] Active Directory, which is about as ubiquitous as it gets, and use it more strategically. It will spur use of [these features].

Sender authentication solutions are very slow to reach maturity, and that is simply a shame on the ISPs, who have not been aggressive enough in developing the specs and deploying them in full force.

It's a little early to tell whether [chargeback] really influences user behavior.

Sadly, this law will likely have the same effect as Can-Spam Act had -- that is, very little.

Companies don't want to give out information about where their employees are surfing. Microsoft was not pleased when Amazon.com showed the top book picks by its employees.