Q&A Session 2 – Bharat Parekh
summary
RTMP third‑party encoders stay on TCP while first‑party mobile streams use Rush over QUIC; standardization via the IETF Media over QUIC working group is underway and hardware encoder migration is projected to take years. Edge load balancers implement connection ID routing so QUIC migration keeps sessions when client IPs change. A centralized flow cache runs on three hosts with periodic republishing from back ends. Global Accelerator preserves client IP via encapsulation inside a VPC and uses two static IPs from separate network zones for higher resiliency.
AI-written summary · about
chapters (14)
- 0:00Q&A
- 0:47Live stream routing stability
- 2:36QUIC connection ID routing
- 4:05Return to Sender in VPC
- 5:49Multi-region AWS availability
- 7:13Flow cache failure handling
- 8:37TCP options and IP fragmentation
- 9:40Fail open in network infra
- 11:48Client IP with Global Accelerator
- 14:45Routing info in TCP timestamp
- 16:10Global Accelerator HTTPS support
- 17:33QUIC connection ID spec
- 19:03Static IPs in Global Accelerator
- 21:50Closing remarks
