Or use of existing internet protocols, yes.
Here's an example: I was in an amateur rocketry group. One of our primary telemetry connections was wifi; 802.11b channel 1 is in an amateur band. We used directional antennas on the ground, cylindrical patch antennas on the rocket, and 1W of power (which is why we needed amateur licenses, to exceed the standard 100mW for wifi) and we could reliably communicate via standard IP while the rocket was a long distance away and breaking the sound barrier. The ESSID was one of our callsigns.
Our standard telemetry protocol was unencrypted packets, because ham radio. But a common need while debugging the rocket on the launchpad was to SSH in (it ran Linux). So our options were:
- Use something obsolete with much worse UX, like telnet.
- Use SSH and try to convince it to run without encryption, an option which is a bad idea for every other use case and which modern SSH rightfully refuses to contemplate.
- Use SSH with published keys, and hope that suffices to meet the spirit of the regulation.
- Add some complexity to the system to reduce power level while on the pad so that we weren't actually using a ham license.
- Safe the engines, go out to the pad a mile away, and hook up to the wired umbilical for debugging.
Removing the encryption restriction would allow using standard SSH and similar systems.