Re: RDP Protocol Specification

Tech-Archive recommends: Speed Up your PC by fixing your registry

From what I understand after reviewing the documents on this site in order
to get the RDP spec I'd have to enter into a legal agreement with Microsoft then fly to Redmond and review the spec at their offices. I could do this for free for three days or pay $4,500 for 30-days access, or pay $12,500 to have full access off-site. That's a lot to go through for a specification detailing a protocol that's already been reverse-engineered (rdesktop). One would think it'd be in Microsoft's interest to allow developers to work with RDP as much as possible, at least on the client side, because it'd create more demand for Windows Server products. One might say that this benefit would be mitigated by people writing their own RDP clients for alternative operating systems and thus creating less demand for Windows embedded operating systems but, as I said, rdesktop's been around for years and is currently being used by a lot of people to work through the RDP spec. I'd just rather have a complete whitepaper published by a responsible company to work from rather than sifting through some nasty uncommented and undocumented open source code but I don't think I'd path through the nose for it or fly to Redmond for it.

Scott Lloyd
Lloyd Software


"TP" <tperson.knowspamn@xxxxxxxxxxxxxxx> wrote in message news:eqCRZeOmHHA.3264@xxxxxxxxxxxxxxxxxxxxxxx
Hi Scott,

If you want the RDP specs, then you need to license it via the Microsoft Communications Protocol Program (MCPP).

MCPP Info:

http://www.microsoft.com/about/legal/intellectualproperty/protocols/mcpp.mspx

Terminal Server Task:

http://www.microsoft.com/about/legal/intellectualproperty/protocols/TaskDetails.aspx?pkid=910

TS Licensing Info:

http://www.microsoft.com/about/legal/intellectualproperty/protocols/TaskInfo.aspx?pkid=910

-TP

Scott Lloyd wrote:
Why in the world hasn't Microsoft released a spec for one of the most
important protocols ever? I have wanted to do some direct work with
the RDP protocol for a long time and find the lack of documentation
frustrating and unreasonable.

Scott Lloyd
Lloyd Software

.