From: Marc-André M. <mar...@gm...> - 2009-01-28 05:04:29
|
You can download an archive of all the windows network protocol documentation as pdfs here: http://download.microsoft.com/download/9/5/E/95EF66AF-9026-4BB0-A41D-A4F81802D92C/Windows_Communication_Protocols.zip http://msdn.microsoft.com/en-ca/library/cc240445(PROT.10).aspx<http://msdn.microsoft.com/en-ca/library/cc240445%28PROT.10%29.aspx> I don't know if anybody else has noticed, but these new updates also include RemoteApp: http://msdn.microsoft.com/en-ca/library/cc242568(PROT.10).aspx<http://msdn.microsoft.com/en-ca/library/cc242568%28PROT.10%29.aspx> I've just downloaded the whole thing, it seems very complete! |
From: Johannes S. <Joh...@gm...> - 2009-01-28 12:55:50
|
Hi, On Wed, 28 Jan 2009, Marc-André Moreau wrote: > You can download an archive of all the windows network protocol > documentation as pdfs here: > http://download.microsoft.com/download/9/5/E/95EF66AF-9026-4BB0-A41D-A4F81802D92C/Windows_Communication_Protocols.zip > > http://msdn.microsoft.com/en-ca/library/cc240445(PROT.10).aspx<http://msdn.microsoft.com/en-ca/library/cc240445%28PROT.10%29.aspx> > > I don't know if anybody else has noticed, but these new updates also include > RemoteApp: http://msdn.microsoft.com/en-ca/library/cc242568(PROT.10).aspx<http://msdn.microsoft.com/en-ca/library/cc242568%28PROT.10%29.aspx> > > I've just downloaded the whole thing, it seems very complete! What's the license? Unless they allow use in Open Source programs explicitely, without fee, I fail to be impressed. Ciao, Dscho |
From: Marc-André M. <mar...@gm...> - 2009-01-28 19:50:14
|
No, it is free! (I never thought I would live to see something like this). At the beginning of each document you have something like this: *Intellectual Property Rights Notice for Protocol Documentation* - *Copyrights.* This protocol documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the protocols, and may distribute portions of it in your implementations of the protocols or your documentation as necessary to properly document the implementation. This permission also applies to any documents that are referenced in the protocol documentation. - *No Trade Secrets.* Microsoft does not claim any trade secret rights in this documentation. - *Patents.* Microsoft has patents that may cover your implementations of the protocols. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, the protocols may be covered by Microsoft's Open Specification Promise (available here: http://www.microsoft.com/interop/osp<http://go.microsoft.com/fwlink/?LinkId=114384>). If you would prefer a written license, or if the protocols are not covered by the OSP, patent licenses are available by contacting pro...@mi.... - *Trademarks.* The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. *Reservation of Rights.* All other rights are reserved, and this notice does not grant any rights other than specifically described above, whether by implication, estoppel, or otherwise. *Tools.* This protocol documentation is intended for use in conjunction with publicly available standard specifications and network programming art, and assumes that the reader either is familiar with the aforementioned material or has immediate access to it. A protocol specification does not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments you are free to take advantage of them. More details are given here: http://www.microsoft.com/interop/osp/default.mspx Microsoft Open Specification PromisePublished: September 12, 2006 | Updated: October 13, 2008 Microsoft irrevocably promises not to assert any Microsoft Necessary Claims against you for making, using, selling, offering for sale, importing or distributing any implementation to the extent it conforms to a Covered Specification ("Covered Implementation"), subject to the following. This is a personal promise directly from Microsoft to you, and you acknowledge as a condition of benefiting from it that no Microsoft rights are received from suppliers, distributors, or otherwise in connection with this promise. If you file, maintain or voluntarily participate in a patent infringement lawsuit against a Microsoft implementation of such Covered Specification, then this personal promise does not apply with respect to any Covered Implementation of the same Covered Specification made or used by you. To clarify, "Microsoft Necessary Claims" are those claims of Microsoft-owned or Microsoft-controlled patents that are necessary to implement only the required portions of the Covered Specification that are described in detail and not merely referenced in such Specification. "Covered Specifications" are listed below. This promise is not an assurance either (i) that any of Microsoft's issued patent claims covers a Covered Implementation or are enforceable or (ii) that a Covered Implementation would not infringe patents or other intellectual property rights of any third party. No other rights except those expressly stated in this promise shall be deemed granted, waived or received by implication, exhaustion, estoppel, or otherwise. In other words, we are totally free to use it, copy it, use it. On Wed, Jan 28, 2009 at 7:56 AM, Johannes Schindelin < Joh...@gm...> wrote: > Hi, > > On Wed, 28 Jan 2009, Marc-André Moreau wrote: > > > You can download an archive of all the windows network protocol > > documentation as pdfs here: > > > http://download.microsoft.com/download/9/5/E/95EF66AF-9026-4BB0-A41D-A4F81802D92C/Windows_Communication_Protocols.zip > > > > http://msdn.microsoft.com/en-ca/library/cc240445(PROT.10).aspx<http://msdn.microsoft.com/en-ca/library/cc240445%28PROT.10%29.aspx> > <http://msdn.microsoft.com/en-ca/library/cc240445%28PROT.10%29.aspx> > > > > I don't know if anybody else has noticed, but these new updates also > include > > RemoteApp: > http://msdn.microsoft.com/en-ca/library/cc242568(PROT.10).aspx<http://msdn.microsoft.com/en-ca/library/cc242568%28PROT.10%29.aspx> > <http://msdn.microsoft.com/en-ca/library/cc242568%28PROT.10%29.aspx> > > > > I've just downloaded the whole thing, it seems very complete! > > What's the license? Unless they allow use in Open Source programs > explicitely, without fee, I fail to be impressed. > > Ciao, > Dscho > |
From: Johannes S. <Joh...@gm...> - 2009-01-28 22:06:56
|
Hi, On Wed, 28 Jan 2009, Marc-André Moreau wrote: > *Patents.* Microsoft has patents that may cover your implementations of > the protocols. Neither this notice nor Microsoft's delivery of the > documentation grants any licenses under those or any other Microsoft > patents. However, the protocols may be covered by Microsoft's Open > Specification Promise (available here: > http://www.microsoft.com/interop/osp<http://go.microsoft.com/fwlink/?LinkId=114384>). > If you would prefer a written license, or if the protocols are not covered > by the OSP, patent licenses are available by contacting > pro...@mi.... > > [...] > > In other words, we are totally free to use it, copy it, use it. I do not see that. Ciao, Dscho |
From: Jennings,
Jared L C. U. A. 46 SK/C. <jar...@eg...> - 2009-01-28 23:18:02
|
Johannes Schindelin [mailto:Joh...@gm...]: > On Wed, 28 Jan 2009, Marc-André Moreau wrote: > > > Microsoft has patents that may cover your implementations of > > the protocols. Neither this notice nor Microsoft's delivery of the > > documentation grants any licenses under those or any other Microsoft > > patents. > > In other words, we are totally free to use it, copy it, use it. > > I do not see that. How does using the documentation make things worse? Couldn't Microsoft already claim software patent over rdesktop, which is an "implementation of the [RDP] protocol"? I detailed a month ago (15 Dec 2008) how the Open Specification Promise (OSP) may or may not cover RDP and its extensions, particularly the smartcard extension. Here's the relevant excerpt of my message: There exists a publicly readable RDP smartcard extension protocol document, at <http://msdn.microsoft.com/en-us/library/cc242596(PROT.10).aspx>. In its preamble it says that the protocol "may be covered by Microsoft's Open Specifications Promise;" it says (RDPESC section 1.4) that it's an extension of the filesystem virtual channel extension, which (RDPEFS section 1.4) is embedded in a static virtual channel specified by basic RDP, which (RDPBCGR section 1.4) is "based on the ITU T.120 series of protocols." The Open Specifications Promise says that it covers "T.120." |
From: Matthew C. <mat...@cs...> - 2009-01-28 23:44:39
|
I agree, my opinion (and also the opinion of the Samba Team) is that the documentation is fine to use and doesn't make things any worse. Also, at least the core T.120 stuff is covered under Open Specification Promise. If there's specific problems with the licence let me know and I'll speak to my Microsoft MCPP contact to try and get things clarified. >From previous communication I can attest that there's many people in Microsoft who have a genuine interest in enabling interoperability with projects like Samba and rdesktop, so I think the kneejerk distrust is unjustified. Matt |