On "external deployment"

On "external deployment"

It's not an oversight that this is a EULA rather than a GPL-style copyright license.

Well, they seem to be acting in good faith, having submitted the RPSL to the OSI for certification. The question remains, I guess, whether or not a use-restricting EULA can qualify as open source or free software. I suspect it will pass, since the restrictions in question are not onerous. But having to click through a license just to download, much less use, a piece of software still leaves a bad taste in my mouth, and will cause practical problems for distributors such as Debian. (RPSL-covered software cannot be put on an anonymous FTP server, for example.)

This would include, for instance, putting up a web page that takes a Real file, decode it, and deliver it in some other format

I'd call that "public performance", which is covered by copyright law. Then again, that interpretation of "public performance" would also include any network server software, so maybe I'm off base....

On the other hand, I'm a little surprised that there doesn't seem to be any restriction against someone accepting the license, downloading the code, and posting it again, sans EULA.

Well, they assert that you have to accept the license before downloading the code (which I don't believe is enforceable, but it certainly is a common claim in the proprietary software world), so if you post the code sans EULA, Real still claims that whoever downloads it from you must first accept the license. Since you aren't making it possible for them to "sign" it, I guess you would be offering the code fraudulently.