In the complex world of video transmission and network management, data doesn’t just “flow”; it is carefully orchestrated. Three acronyms often surface when discussing how media moves from source to viewer: IGMP, RTSP, og HLS.
While all three relate to media and networking, they operate at different layers and serve vastly different purposes from managing bandwidth in a local network to delivering Netflix to your smartphone.
This guide breaks down the mechanics, use cases, and distinct characteristics of each protocol.
1. IGMP: The Multicast Gatekeeper
Internet Group Management Protocol
IGMP is not a streaming protocol in the traditional sense; it is a network layer management protocol. Its primary job is to manage membership in multicast groups.
How It Works
In a standard Unicast network, if 100 people want to watch a video stream, the server sends 100 separate copies of the data. This crushes bandwidth. In a Multicast network, the server sends one copy, and the network switches/routers replicate it only for the specific users who requested it.
IGMP is the language spoken between the client (host) and the local router:
Join: When a user switches to a specific IPTV channel, their device sends an IGMP “Join” report for that specific multicast group IP.
Traffic Flow: The router receives the request and directs that specific stream to the user’s subnet.
Leave: When the user changes the channel, an IGMP “Leave” message is sent, and the router stops forwarding that data to conserve bandwidth.
Key Feature: IGMP Snooping
Switches are typically Layer 2 devices and don’t read Layer 3 IP packets. However, with IGMP Snooping, a switch “listens” to the IGMP conversation between the host and router. This allows the switch to send multicast traffic only to the specific ports that asked for it, rather than flooding every port on the switch.
Best for: IPTV systems, internal corporate broadcasts, financial data feeds.
Latency: Ultra-low (close to real-time).
Transport: Layer 3 (IP).
2. RTSP: The Network Remote Control
Real-Time Streaming Protocol
If IGMP is the traffic cop, RTSP is the remote control. RTSP does not actually transmit the video data itself; rather, it controls the streaming server.
How It Works
RTSP establishes and maintains a control session between the client and the server. It uses a syntax very similar to HTTP.
Control State: RTSP is a “stateful” protocol. The server tracks the state of the client (Connected, Playing, Paused).
Commands: It supports commands like
SETUP,PLAY,PAUSE,RECORD, ogTEARDOWN.Data Transport: While RTSP handles the commands, the actual video/audio data is usually delivered via RTP (Real-time Transport Protocol) over UDP (User Datagram Protocol).
Because it usually utilizes UDP for transport, RTSP prioritizes speed over data integrity. If a packet drops, it doesn’t stop to ask for it again; it keeps moving to prevent lag.
Best for: IP Security Cameras (CCTV), drone feeds, teleconferencing systems.
Latency: Low (typically <2 seconds).
Transport: TCP for control, usually UDP for media.
3. HLS: The Adaptive Universalist
HTTP Live Streaming
Developed by Apple, HLS changed the game by treating video streams not as a continuous flow of data, but as a sequence of small file downloads. It is currently the dominant standard for internet video delivery.
How It Works
HLS works by chopping a video stream into short chunks (usually 2–10 seconds long) and creating a text-based index file called a Manifest (.m3u8).
The Manifest: The player downloads the
.m3u8file, which contains a list of URLs pointing to the video chunks.Adaptive Bitrate (ABR): This is HLS’s superpower. The server encodes the video at multiple quality levels (480p, 720p, 1080p, 4K). If the user’s internet connection drops, the player automatically switches to a lower quality chunk in the next request to prevent buffering.
HTTP Delivery: Because it uses standard HTTP/HTTPS (port 80/443), HLS passes easily through standard firewalls and can be cached by CDNs (Content Delivery Networks) just like standard web images or text.
Best for: OTT platforms (Netflix, Hulu), YouTube, mobile streaming, reaching massive audiences over the public internet.
Latency: Historically high (10–30 seconds), though Low-Latency HLS (LL-HLS) is bringing this down significantly.
Transport: TCP (HTTP).
Summary Comparison
Funksjon | IGMP | RTSP | HLS |
|---|---|---|---|
Primary Role | Multicast Group Management | Stream Control (Remote) | Adaptive Media Delivery |
Transport Layer | IP (Layer 3) | TCP/UDP | TCP (HTTP) |
Forsinkelse | Near Zero | Lav | Medium to High |
Scalability | High (Local Network) | Low (Server intensive) | Massive (CDN friendly) |
Reliability | Network Dependent | Packet loss possible (UDP) | High (TCP retransmission) |
Firewall Friendliness | Low (Blocked by WANs) | Medium (Needs specific ports) | High (Uses standard web ports) |
Primary Use Case | IPTV, Local Networks | CCTV, Surveillance | Public Internet Streaming |
Konklusjon
The choice between these protocols depends entirely on the environment:
Use IGMP if you are an ISP building a cable TV service or a sysadmin managing a private LAN where bandwidth efficiency is paramount.
Use RTSP if you are installing security cameras or need a low-latency feed where occasional visual artifacts are acceptable but lag is not.
Use HLS if you want to broadcast video to thousands of users across the world on varying devices (iOS, Android, Desktop) and network speeds.
Norwegian 
English (United States) 
German 
Dutch 
Swedish 
Danish 
English (UK) 
English (Australia) 
English (New Zealand)