There is a lot of secret sauce in protocols. Those decisions can have serious positive/negative implications on performance and features. Making those easily available to everyone could potentially destroy a business.
Don't get me wrong, I've had to reverse engineer my share of proprietary protocols to get behavior I wanted (and would have loved to see them be open), but I don't think I can get onboard with the idea that requiring open protocols is trivial or noninvasive.
But we aren't discussing just these specific APIs/protocols (and I haven't look at them, so I'd have to take your word on that), we are discussing this generally.
Don't get me wrong, I've had to reverse engineer my share of proprietary protocols to get behavior I wanted (and would have loved to see them be open), but I don't think I can get onboard with the idea that requiring open protocols is trivial or noninvasive.