Remote Access Protocols

These protocols play key roles in network communication by establishing sessions and enabling secure or remote access to devices and systems.

Protocol

Description

Use Case

VNC (Virtual Network Computing)

Platform-independent protocol for remote desktop sharing via TCP ports 5900+. Shares graphical desktop for remote control and support.

Cross-platform desktop sharing and remote technical support.

SPICE (Simple Protocol for Independent Computing Environments)

Open-source protocol aimed at streaming graphical desktop and media over a network. Supports USB redirection, audio, video, and optimized frame updates.

Virtual machine console access (e.g., with QEMU/KVM in Linux).

Main Features

  • Platform-independent remote desktop sharing over TCP ports starting at 5900

  • Shares graphical desktops for remote control and support

  • Simple, lightweight, but typically unencrypted

  • Works across multiple operating systems

RFC References

Use Cases

  • Cross-platform remote technical support and desktop sharing

  • Remote access to Unix/Linux desktops and mixed environments

  • Training and collaborative screen sharing

Alternative Protocols

  • RDP – Windows-focused remote desktop with advanced features

  • TeamViewer, AnyDesk – Enhanced secure remote desktop solutions

  • SSH with X11 forwarding – Unix/Linux GUI applications over secure channels

Main Features

  • Open-source protocol primarily for accessing virtual desktops (e.g., QEMU/KVM)

  • Supports audio, video, USB redirection, and efficient frame updates

  • Integrated with libvirt and virt‑viewer for VM access

  • Designed with virtualization in mind, offering low-latency performance

RFC References

  • Open-source project — no RFC

Use Cases

  • Administrator and user access to Linux virtual machine consoles

  • Embedded virtualization management and remote desktop tasks

Alternative Protocols

  • RDP / VNC – More general-purpose remote access

  • PCoIP / ICA – Enterprise-grade virtual desktop protocols