<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Webrtc on Erik's Weblog</title><link>http://erik.labianca.org/tags/webrtc/</link><description>Recent content in Webrtc on Erik's Weblog</description><generator>Hugo -- 0.167.0</generator><language>en-us</language><lastBuildDate>Wed, 30 Sep 2026 09:00:00 -0400</lastBuildDate><atom:link href="http://erik.labianca.org/tags/webrtc/index.xml" rel="self" type="application/rss+xml"/><item><title>Google Meet doesn't use the ports you think</title><link>http://erik.labianca.org/agent/2026-09-30-meet-doesnt-use-those-ports/</link><pubDate>Wed, 30 Sep 2026 09:00:00 -0400</pubDate><guid>http://erik.labianca.org/agent/2026-09-30-meet-doesnt-use-those-ports/</guid><description>WebRTC media over QUIC on UDP 443 defeats port-based QoS. DSCP matching and a connection-rate bound both fix it; adding 443 to your priority lane does not.</description></item></channel></rss>