what exactly do U need?
there is no special documentation for dedi, it uses same InSim as lfs.exe
running servers info can be collected with LFSW http://www.lfsforum.net/showthread.php?t=14480
docs/Commands.txt contains the dedi commands as well as the regular ones, if that's what you're after. I'm not sure I'd consider anything in the LFS docs directory a whitepaper though
like most games the exchange of data is encrypted as a means to prevent cheating - at least I assume it is. However if you wish to get into communicating with your server (rather than writing alternate server/client binaries) then check out insim.txt in the lfs docs folder.
No documentation for the protocols (excluding InSim/OutSim/Outguage - which you can use for communicating with LFS and are relatively stable), I'm afraid (part of the reason is that this would allow Scawen to change it as he needs to, which is reasonable, I guess).
If you want the client <-> server protocol, you can find out quite a bit by packeting sniffing. How far you want to go is up to you though
I was working on a solution for the negative brake force thingy and mailed the devs about releasing (parts of) the packet structure, it's unlikely to happen.
I got parts of the position/status update packet by sniffing, but now that Scawen implemented the cheating protection, there's no need for my project.