BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//CERN//INDICO//EN
BEGIN:VEVENT
SUMMARY:The evolution of HTTP based signalling for WebRTC in GStreamer
DTSTART;VALUE=DATE-TIME:20230926T140000Z
DTEND;VALUE=DATE-TIME:20230926T143000Z
DTSTAMP;VALUE=DATE-TIME:20260718T001629Z
UID:indico-contribution-249@indico.freedesktop.org
DESCRIPTION:Speakers: Taruntej Kanakamalla (asymptotic.io)\nThe adoption o
 f WebRTC in the broadcasting/streaming industry has been hindered due to l
 ack of standard signalling that can be a simple plug and play model. With 
 introduction of [WHIP](https://www.ietf.org/archive/id/draft-ietf-wish-whi
 p-09.html) and [WHEP](https://www.ietf.org/archive/id/draft-murillo-whep-0
 2.html) specifications that is changing and the acceptance of WHIP/WHEP is
  evident with all major multimedia open source software implementing them.
 \n\nGStreamer already had the client side implementations WHIP/WHEP (whips
 ink and whepsrc) as of release 1.22 written in Rust. And the server side i
 mplementations are in progress.\n\nWith WebRTCSink and WebRTCSrc written t
 o support any signalling protocol as an interface separating from the sink
 /src functionality\, it has become easy to write all the client and server
  side implementations of WHIP/WHEP on top of WebRTCSink/Src. This also hel
 ps to leverage the support of both raw and encoded streams\, the congestio
 n control mechanism and every other new improvement that will be added in 
 WebRTCSink/Src in the future.\n\nMy talk is going to be an introduction on
  WHIP/WHEP protocols and the initial version of elements implemented in GS
 treamer using Rust and how they are evolving using the Signaller based des
 ign in the GStreamer WebRTC Rust plugins.\n\nhttps://indico.freedesktop.or
 g/event/5/contributions/249/
LOCATION:Palexco Room 2
URL:https://indico.freedesktop.org/event/5/contributions/249/
END:VEVENT
END:VCALENDAR