Linked by Thom Holwerda on Tue 18th Dec 2012 00:03 UTC
Microsoft Microsoft has just responded to Google's move regarding Exchange ActiveSync. Sadly, instead of addressing the very real problems consumers are about to face, Microsoft starts talking about switching to
Permalink for comment 545571
To read all comments associated with this story, please click here.
Member since:

Not sure about the patenting, but the EU forced Microsoft to make a lot of protocols available to competitors.

And Samba team payed Microsoft 10.000 Euros to get access to that documentation:

On 11 dec. (so only couple of days ago) Samba 4 was released which implements a large number of Microsoft protocols and processes. Most of it was already reference engineered of course.

Which includes pretty much all the features Microsoft supports: different domain controller roles, Active Directory, LDAP, Kerberos, DNS, dynamic DNS updates, the SMB 2.0 and SMB 2.1 protocols included since Windows Vista and even experimental support the SMB 3.0 which is included in Windows Server 2012.

The SMB 3.0 protocol which was needed for Windows Server 2012 "Scale Out File Server" brings support for Active/Active and failover Fileserver support.

Which is something the Samba team already did since 2007 with the older SMB 1.x protocols. That is why when the Samba team went to Microsoft this year to do interability testing the Samba team could test code for SMB 3.0 they only created a day before they arrived and it worked.

Also the Linux 3.7 kernel released a couple of days ago also experimental client support for SMB 2.x, most of that code comes from the Samba developers of course.

Let's get back to E-mail and Exchange, the OpenChange project is a full Exchange replacement based on Samba 4 libraries/code.

Only a couple of days ago the OpenChange project completed most of the features by adding support for Active Sync/Outlook Anywhere by implementing the RFC over HTTP(S)*

Maybe Google had a contract with some company to provide them an implementation for ActiveSync and Google did not renew the contract because they knew they could use the above mentioned code if they needed to enable it again ?

Because of the Samba team you too can now see the protocol specification:*~...

So yes, it isn't an open standard and there might be patent problems, but I doubt the problems are all that great now.

So thanks to the EU and the Samba and OpenChange teams the open source code exists (GPLv3 which has a special patents clause to help protect the innocent as well).

The Samba team even sends them notifications if documentation is wrong and Microsoft fixes the documentation.

I always love to hate Microsoft and Microsoft did not do this out of love, they were forced to. So I think we can still have them ;-)

But hey if people don't use Microsoft protocols it isn't a great loss, they usually suck. For example because of compatibility reasons Microsoft still uses crappy hashing for their password store:


Edited 2012-12-18 01:01 UTC

Reply Score: 11