Microsoft Plans To License Server Message Block Protocol This Summer

Microsoft

The company, which said earlier this week that it would also license its Common Internet File System (CIFS) protocol, will license the SMB file-sharing protocol later this summer, Microsoft spokesman Jim Desler told CRN. "The SMB protocol license will be available later on this summer," Desler said.

The SMB protocol requests file and print services from a Windows client to a Windows server over a corporate network. The ability to license SMB--and the core CIFS in Windows NT 4.0 --will allow improved interoperability between non-Windows systems and Windows systems, Desler said. For example, companies can create their own implementations of the CIFS and SMB protocols for use on non-Windows clients and servers on a royalty-free basis.

The licensing of these server-side protocols has been met with a mixture of hope and skepticism. At least one competitor in the Linux space said licensing the SMB or CIFS won't help him.

"It probably won't help at all, unless they release the IDL [Interface Definition Language files that define the protocols used to manage Windows servers," said Jeremy Allison, member of an open-source development team called Samba that develops the Linux-based Samba file and print server. "We care about definition of protocols. That's the complete definition of the binary bits that go over the wire between two computers."

As part of its antitrust problems in the United States and Europe, Microsoft has made recent gestures to provide better disclosure of technical information. The company announced it would license the core CIFS earlier this week as well as its implementation of the Kerberos security protocol on Feb. 20.

Many of these technical disclosures are "above and beyond [what is required by the consent decree," said Microsoft's Desler.

In addition, last May Microsoft launched its shared source initiative program that allows corporations and governments the ability to view Windows source code. Last month, Microsoft extended the program to a key channel constituency--systems integrators. As part of that, Microsoft makes available about 97 percent of the Windows source code for viewing but not modification or redistribution. Microsoft Shared Source Product Manager Jason Matusown told CRN recently that the remaining 3 percent of the Windows code includes code developed by third parties and other "high APIs Microsoft is holding on to more tightly," such as product activation code.

However, some industry observers--namely the nine state attorneys general and District of Columbia that oppose the proposed antitrust settlement between the company and the U.S. Justice Department--would like to see broader access to the Windows Source Code and the APIs.

Licensing SMB and other server-side protocols "isn't really about opening APIs ... it's about allowing those technologies to be supported on non-Windows platforms," said Andrew Brust, president of Progressive Systems, an applications developer and consulting firm in New York. "I think the whole thing is encouraging and a confidence-building measure," he said.

"These moves allow Microsoft technologies, or Microsoft implementations of certain standards, to be implemented, or communicated with, on non-Windows platforms. In some cases, these initiatives are being implemented without any regulatory agency specifically requesting them to be. This is Microsoft being proactive, and I think it's a good business for them, and beneficial to the industry in general."