If you’ve ever wondered why your IP camera freezes, your livestream lags, or your “professional CCTV system” behaves like a drunk toaster - congratulations.
You’ve stumbled into the greatest joke of modern networking:
The entire global video surveillance and streaming industry runs on a pile of mismatched, outdated, incompatible protocols taped together with hope and cable ties.
We’re talking about:
RTP — the fossil
RTSP — the bossy control freak
RTMP — the undead
ONVIF — the bureaucrat with a clipboard
Together, these four hold up billions - yes, billions of streams every single day.
And the miracle isn’t that they work well. The miracle is that they work at all.
Welcome to a brutally honest teardown of the video industry’s sacred cow. Let’s carve it.
RTP: the underpaid millennial doing all the real work
RTP is the one protocol in this whole circus that actually does something useful, and naturally, it’s also the most abused.
RTP carries the video.
RTP carries the audio.
RTP deals with timing, packet order, jitter, and loss.
RTP never complains, never asks for a raise, never takes a vacation.
RTP basically runs the entire global real-time media economy the same way underpaid interns run corporate America.
And what does RTP use to deliver your precious video frames?
UDP.
The protocol that shrugs and says:
“Oops? You wanted reliability?
lol.”
If packets die, RTP just keeps walking.
If the network burns, RTP keeps walking.
If you scream at it, RTP — you guessed it — keeps walking.
RTP is the backbone of WebRTC, VoIP, IP cameras, intercoms, video conferencing, and basically anything that isn’t a 30-second-delayed HLS stream for your grandmother.
In short:
RTP, the least appreciated entity in streaming, is carrying all of us on its broken back.
RTSP: the middle manager who produces no work but gives plenty of orders
RTSP doesn’t transport media. It doesn’t solve latency issues. It doesn’t fix jitter. It doesn’t encode, decode, or optimize anything.
It just tells everyone else what to do — loudly, confidently, and often incorrectly.
RTSP is the guy with a clipboard yelling:
PLAY
PAUSE
RECORD
STOP
SETUP
TEARDOWN (the most dramatic command in network history)
RTSP is the overconfident project manager of streaming.
Produces nothing. Controls everything.
And magically — magically! — RTSP became the standard for IP cameras across the globe.
Why?
Because the industry looked at all alternatives and concluded: “Well, everything else is even worse.”
RTMP: the zombie protocol that didn’t read the memo about being dead
Flash died. Flash was buried. Flash was cremated, the ashes scattered, and the obituary printed.
But RTMP?
RTMP walked out of the coffin like: “Sup. Still working.” If RTMP were a person, it would be the employee who was fired three years ago but still shows up and somehow outperforms the entire new staff.
Every major platform still accepts RTMP ingest: YouTube. Twitch. Facebook. Restream. Your local streaming server. Everyone.
Because RTMP:
works over TCP
doesn’t freak out over bad Wi-Fi
handles bitrates like a champ
has predictable latency
just… works
Try replacing it. Go ahead. watch your ingest break, your encoder cry, and your viewers revolt.
RTMP is proof that in tech, “not dead yet” is often the only requirement for becoming a standard.
ONVIF: the overworked bureaucrat trying to control feral cameras
Before ONVIF, every camera manufacturer had its own private fantasy API — a different dialect of madness:
Dahua: XML made by someone who hates XML
Hikvision: half-documented JSON with missing fields
Axis: beautifully engineered but incompatible with everyone
Cheap no-name Chinese cams: protocols written by someone’s cousin over a weekend
ONVIF arrived like a frustrated government inspector: “ENOUGH. Everyone follows MY rules now.”
And shockingly, it worked.
Does ONVIF transmit video?
No. Never. Not even close.
All ONVIF does is:
Discover cameras
Fetch RTSP URLs
Configure streams
Control PTZ
Manage events
Ensure authentication
Make vendors behave like semi-civilized citizens
ONVIF is the duct tape of the CCTV world. If it disappeared tomorrow, the IP camera market would collapse into feral chaos within 48 hours.
Why don’t we replace all this garbage? Because the industry is allergic to improvement.
You might wonder: “Why not create one clean, modern, elegant protocol to replace everything?”
Because the video industry can’t agree on anything except that coffee is essential.
Real-time video has mutually exclusive needs:
Low latency
→ RTP/RTSP/WebRTC
(Because operators want to see intruders before they leave.)
High reliability
→ RTMP/SRT/RIST
(Because broadcasters can’t have their stream die mid-Super Bowl.)
Massive scale
→ HLS/DASH
(Because millions of viewers won't watch your low-latency RTSP stream over UDP.)
Hardware discoverability
→ ONVIF
(Because cameras are basically wild animals.)
Browser compatibility
→ Well… nothing really works perfectly, but HLS wins by default.
Every protocol exists because some combination of engineers, vendors, committees, lawyers, and opportunists demanded it. And now it’s all too entrenched to replace.
Bonus: the rest of the clown parade
HLS
“Here’s a video chunk. And another. And another.
You’ll see the goal 25 seconds late, but hey — at least Safari likes me.”
MPEG-DASH
HLS but with PDFs explaining why it’s better.
WebRTC
Amazing technology powered by black magic, sacrifice, and network misery.
SRT
Because broadcasters want to feel that someone cares about their packets.
RIST
Like SRT, but written by networking purists who hate fun.
MPEG-TS
Older than half your coworkers. Works anyway. Will outlive us all.
The ugly truth
Your entire multi-billion-dollar global video industry runs on:
a 1990s transport protocol (RTP)
a control protocol with the personality of a grumpy librarian (RTSP)
a zombie ingest workflow designed for Flash (RTMP)
an XML-based bureaucratic overlord (ONVIF)
plus a stack of web protocols invented because Apple needed to stream WWDC.
And yet — and this is the punchline — it all somehow works.
Blurry? Sometimes.
Lagging? Often.
Chaotic? Always.
But it works. Because the video industry isn’t about perfection. It’s about duct tape, legacy decisions, and the quiet dignity of engineers who wake up every day and make this mess function.