O slideshow foi denunciado.
Seu SlideShare está sendo baixado. ×

IETF remote participation via Meetecho @ WebRTC Meetup Stockholm

Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Próximos SlideShares
Janus/SIP @ OpenSIPS 2017
Janus/SIP @ OpenSIPS 2017
Carregando em…3
×

Confira estes a seguir

1 de 45 Anúncio

Mais Conteúdo rRelacionado

Diapositivos para si (20)

Quem viu também gostou (19)

Anúncio

Semelhante a IETF remote participation via Meetecho @ WebRTC Meetup Stockholm (20)

Anúncio

Mais recentes (20)

IETF remote participation via Meetecho @ WebRTC Meetup Stockholm

  1. 1. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Enabling remote participation in a World-Wide engineering organization: How WebRTC is used in the IETF meetings Lorenzo Miniero @elminiero WebRTC Stockholm Meetup 16th February 2017, Stockholm
  2. 2. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps You may remember me from a couple of hours ago!
  3. 3. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Outline 1 A bit of history How did remote participation work in the IETF just a few years ago? Meetecho: How We Turned an IETF Experiment into an IETF Tool 2 Using WebRTC as a tool for remote participation at the IETF Choosing a WebRTC engine: remember Janus? Capturing and streaming: the typical layout of a session Detecting issues in advance: the Self-test application 3 What it all looks like Attending remotely: attendees, presenters and the virtual queue Monitoring and controlling sessions remotely Recording sessions and making them available for replay 4 Next steps
  4. 4. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps First of all, what is the IETF? • Internet Engineering Task Force (IETF) • Standardized pretty much all the protocols you use everyday... • HTTP, SMTP, POP3, IMAP, SNMP, SIP, SDP, RTP, XMPP, ... • All work done by volunteers (which means YOU could write an RFC!) • Several different Working Groups in different Areas • Routing, Security, Transport, Applications and Real-Time, ... • Each Working Group (WG) collaborates on mailing lists • General meetings three times a year all over the world • Typically once in America, once in Europe, once in Asia • On average ~1200 local participants • Most WGs meet to present and discuss the latest documents Newcomers Tutorial (Scott Bradner) • https://www.youtube.com/watch?v=L5D5RwWfQTA
  5. 5. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps First of all, what is the IETF? • Internet Engineering Task Force (IETF) • Standardized pretty much all the protocols you use everyday... • HTTP, SMTP, POP3, IMAP, SNMP, SIP, SDP, RTP, XMPP, ... • All work done by volunteers (which means YOU could write an RFC!) • Several different Working Groups in different Areas • Routing, Security, Transport, Applications and Real-Time, ... • Each Working Group (WG) collaborates on mailing lists • General meetings three times a year all over the world • Typically once in America, once in Europe, once in Asia • On average ~1200 local participants • Most WGs meet to present and discuss the latest documents Newcomers Tutorial (Scott Bradner) • https://www.youtube.com/watch?v=L5D5RwWfQTA
  6. 6. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps First of all, what is the IETF? • Internet Engineering Task Force (IETF) • Standardized pretty much all the protocols you use everyday... • HTTP, SMTP, POP3, IMAP, SNMP, SIP, SDP, RTP, XMPP, ... • All work done by volunteers (which means YOU could write an RFC!) • Several different Working Groups in different Areas • Routing, Security, Transport, Applications and Real-Time, ... • Each Working Group (WG) collaborates on mailing lists • General meetings three times a year all over the world • Typically once in America, once in Europe, once in Asia • On average ~1200 local participants • Most WGs meet to present and discuss the latest documents Newcomers Tutorial (Scott Bradner) • https://www.youtube.com/watch?v=L5D5RwWfQTA
  7. 7. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps First of all, what is the IETF? • Internet Engineering Task Force (IETF) • Standardized pretty much all the protocols you use everyday... • HTTP, SMTP, POP3, IMAP, SNMP, SIP, SDP, RTP, XMPP, ... • All work done by volunteers (which means YOU could write an RFC!) • Several different Working Groups in different Areas • Routing, Security, Transport, Applications and Real-Time, ... • Each Working Group (WG) collaborates on mailing lists • General meetings three times a year all over the world • Typically once in America, once in Europe, once in Asia • On average ~1200 local participants • Most WGs meet to present and discuss the latest documents Newcomers Tutorial (Scott Bradner) • https://www.youtube.com/watch?v=L5D5RwWfQTA
  8. 8. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps How did IETF remote participation work just a few years ago? • A few instruments to use together for each WG session • Jabber room (instant messaging) • MP3 stream (audio) • Downloadable slides (datatracker) • Kinda worked, but also quite awkward... • Attendees needed to manually download and open slides • Dedicated “Scribe” had to track every slide change, comment, etc. • Jabber room only way to interact • MP3 stream had several seconds of delay Making it simpler: the Meetecho Experiment (“eat your own dog food!”) • Web interface that included everything • Integrated Jabber room, automated slide feed, real-time audio/video feed
  9. 9. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps How did IETF remote participation work just a few years ago? • A few instruments to use together for each WG session • Jabber room (instant messaging) • MP3 stream (audio) • Downloadable slides (datatracker) • Kinda worked, but also quite awkward... • Attendees needed to manually download and open slides • Dedicated “Scribe” had to track every slide change, comment, etc. • Jabber room only way to interact • MP3 stream had several seconds of delay Making it simpler: the Meetecho Experiment (“eat your own dog food!”) • Web interface that included everything • Integrated Jabber room, automated slide feed, real-time audio/video feed
  10. 10. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps How did IETF remote participation work just a few years ago? • A few instruments to use together for each WG session • Jabber room (instant messaging) • MP3 stream (audio) • Downloadable slides (datatracker) • Kinda worked, but also quite awkward... • Attendees needed to manually download and open slides • Dedicated “Scribe” had to track every slide change, comment, etc. • Jabber room only way to interact • MP3 stream had several seconds of delay Making it simpler: the Meetecho Experiment (“eat your own dog food!”) • Web interface that included everything • Integrated Jabber room, automated slide feed, real-time audio/video feed
  11. 11. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Experimenting with Meetecho @ IETF 80 (Prague) • Dynamic web application that wrapped the WG Jabber room • Slides pre-converted to images and “triggered by us” at slide change • Java RTP applet implemented audio/video from the room • IETF team allowed us to use resources (e.g., mixer board) • Experiment covered 7-8 RAI (now ART) working groups • Funnily enough, RTCWEB BOF was one of the first we supported! • https://www.ietf.org/jabber/logs/rtcweb/2011-03-29.txt • Got very helpful feedback (both positive and negative) • “One page to rule them all” made participation much easier • Live audio (although lower quality) and addition of video widely praised • ... although some local attendees were confused by the presence of cameras • Integrated slides allowed attendees and scribes to relax • Most did not like the Java application to replay recordings, though... • HTML5 web app to replay recordings implemented during IETF week!!
  12. 12. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Experimenting with Meetecho @ IETF 80 (Prague) • Dynamic web application that wrapped the WG Jabber room • Slides pre-converted to images and “triggered by us” at slide change • Java RTP applet implemented audio/video from the room • IETF team allowed us to use resources (e.g., mixer board) • Experiment covered 7-8 RAI (now ART) working groups • Funnily enough, RTCWEB BOF was one of the first we supported! • https://www.ietf.org/jabber/logs/rtcweb/2011-03-29.txt • Got very helpful feedback (both positive and negative) • “One page to rule them all” made participation much easier • Live audio (although lower quality) and addition of video widely praised • ... although some local attendees were confused by the presence of cameras • Integrated slides allowed attendees and scribes to relax • Most did not like the Java application to replay recordings, though... • HTML5 web app to replay recordings implemented during IETF week!!
  13. 13. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Experimenting with Meetecho @ IETF 80 (Prague) • Dynamic web application that wrapped the WG Jabber room • Slides pre-converted to images and “triggered by us” at slide change • Java RTP applet implemented audio/video from the room • IETF team allowed us to use resources (e.g., mixer board) • Experiment covered 7-8 RAI (now ART) working groups • Funnily enough, RTCWEB BOF was one of the first we supported! • https://www.ietf.org/jabber/logs/rtcweb/2011-03-29.txt • Got very helpful feedback (both positive and negative) • “One page to rule them all” made participation much easier • Live audio (although lower quality) and addition of video widely praised • ... although some local attendees were confused by the presence of cameras • Integrated slides allowed attendees and scribes to relax • Most did not like the Java application to replay recordings, though... • HTML5 web app to replay recordings implemented during IETF week!!
  14. 14. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps The beginnings: Meetecho WebLite and RTCWebLite
  15. 15. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps The beginnings: Meetecho WebLite and RTCWebLite
  16. 16. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Improving the service meeting by meeting • IETF 81 (Quebec City) • Improved UI, 12 sessions, a couple in parallel • IETF 82 (Taipei) • 28 sessions, up to three in parallel • First active remote participation • IETF 83 (Paris) • Tutorial session to discuss Meetecho scribing and moderation • IETF 84 (Vancouver) • First meeting to provide WebRTC access (for RTCWEB only) • IETF 85 (Atlanta) • WebRTC support extended to other sessions as well • First meeting to provide Opus-encoded HTML5 audio stream • IETF 86 (Orlando) • Audio backend improved (from 8kHz to 16kHz)
  17. 17. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Improving the service meeting by meeting • IETF 87 (Berlin) • Presented our Opus efforts at Technical Plenary • Tutorial recording experiments • IETF 88 (Vancouver) • First experiments with WebRTC SFU video • IETF 89 (London) • First time four sessions covered in parallel • First deployment of statistics collector • IETF 90 (Toronto) • First time six sessions covered in parallel • IETF 91 (Honolulu) • All sessions covered for the first time • Janus used as audio/video backend for the first time • First deployment of docker-based architecture • https://www.internetsociety.org/publications/ietf-journal-march- 2014/meetecho-ietf-tool
  18. 18. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Meetecho growth @ IETF
  19. 19. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Meetecho growth @ IETF
  20. 20. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Choosing a WebRTC engine: remember Janus?
  21. 21. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Handling audio: mixer board, SIP and WebRTC • Audio backend is Asterisk’s ConfBridge + Janus SIP plugin • All attendees join the bridge via Janus • Opus-encoded thanks to our asterisk-opus patch • Streaming laptop in the room acts as a participant • Gets audio from mixer board (all mics) and sends it to the bridge • Remote bridge audio passed to mixer board as input (speakers) • Another laptop gets the overall mix (local+remote) for the MP3 streaming
  22. 22. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Handling video (1): static camera and projector • Static feeds are not originated by WebRTC • Static camera, remotely controllable • Projector feed, obtained via a splitter • Both captured and streamed (RTP+VP8) by FFmpeg • Janus Streaming plugin turns unicast RTP in WebRTC broadcast • Two static mountpoints attendees can subscribe to
  23. 23. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Handling video (2): remote speakers • Remote speakers send their video via WebRTC • Publish/subscribe mechanism • Janus VideoRoom acting as SFU • Laptop in the room acts as a regular subscriber • Used to display remote participants on a 2nd screen (Virtual Queue)
  24. 24. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps The Virtual Queue • Chairs moderate the in-room mic line questions • Remote attendees typically type questions in Jabber • Scribe relays them at the mic • ... but remote speakers belong to the mic line too! • Speaking directly solves long waiting times • Virtual Queue tries to solve that • In-room mic lines work as usual • Remote speakers appear in separate queue (2nd screen) • Chair can mute/unmute them with a “Big Red Button”
  25. 25. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Chairs love the “Big Red Button”
  26. 26. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Detecting issues in advance: the Self-test application • Problems can happen with WebRTC all the time • Network constraints or OS/browser issues • Big trouble if they happen during a session, though! • Wastes precious session time, and disrupts the flow • Worked on a Self-test application, to test everything in advance • Check microphone availability/levels • Check webcam availability • Connectivity checks (with/without STUN/TURN) • Record & Play for quality assessment • Generates JSON report we can evaluate to help • Since IETF 98, available on a permanent basis • https://selftest.conf.meetecho.com
  27. 27. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Detecting issues in advance: the Self-test application • Problems can happen with WebRTC all the time • Network constraints or OS/browser issues • Big trouble if they happen during a session, though! • Wastes precious session time, and disrupts the flow • Worked on a Self-test application, to test everything in advance • Check microphone availability/levels • Check webcam availability • Connectivity checks (with/without STUN/TURN) • Record & Play for quality assessment • Generates JSON report we can evaluate to help • Since IETF 98, available on a permanent basis • https://selftest.conf.meetecho.com
  28. 28. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Detecting issues in advance: the Self-test application • Problems can happen with WebRTC all the time • Network constraints or OS/browser issues • Big trouble if they happen during a session, though! • Wastes precious session time, and disrupts the flow • Worked on a Self-test application, to test everything in advance • Check microphone availability/levels • Check webcam availability • Connectivity checks (with/without STUN/TURN) • Record & Play for quality assessment • Generates JSON report we can evaluate to help • Since IETF 98, available on a permanent basis • https://selftest.conf.meetecho.com
  29. 29. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Meetecho: IETF meeting example https://ietf.org/meeting/remote-participation.html
  30. 30. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Meetecho: IETF meeting example https://ietf.org/meeting/remote-participation.html
  31. 31. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Meetecho: IETF meeting example https://ietf.org/meeting/remote-participation.html
  32. 32. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Meetecho: IETF meeting example https://ietf.org/meeting/remote-participation.html
  33. 33. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps “Director” room @ IETF meetings Completely WebRTC-based web application • Consumes the same Video streams remote attendees do • Additional knobs (control remote camera, streams, etc.)
  34. 34. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps “Director” room @ IETF meetings
  35. 35. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Meetecho: IETF recordings https://www.youtube.com/user/ietf
  36. 36. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Interim Meetings? Why not! • Two different types, typically • Virtual Interim Meetings (everybody online) • Physical Interim Meetings (mostly local, some remotes) • Virtual Interim Meetings • Meetecho as web conferencing platform • Several tools available (audio, video, chat, screensharing, etc.) • Physical Interim Meetings • Meetecho “IETF-style” • Would need local support and custom setup (mixers, webcams, etc.) Are we going towards a completely Virtual IETF meeting too? • First discussions started for Buenos Aires (Zika virus risk) • Discussion restarted recently for entirely different reasons...
  37. 37. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Interim Meetings? Why not! • Two different types, typically • Virtual Interim Meetings (everybody online) • Physical Interim Meetings (mostly local, some remotes) • Virtual Interim Meetings • Meetecho as web conferencing platform • Several tools available (audio, video, chat, screensharing, etc.) • Physical Interim Meetings • Meetecho “IETF-style” • Would need local support and custom setup (mixers, webcams, etc.) Are we going towards a completely Virtual IETF meeting too? • First discussions started for Buenos Aires (Zika virus risk) • Discussion restarted recently for entirely different reasons...
  38. 38. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Interim Meetings? Why not! • Two different types, typically • Virtual Interim Meetings (everybody online) • Physical Interim Meetings (mostly local, some remotes) • Virtual Interim Meetings • Meetecho as web conferencing platform • Several tools available (audio, video, chat, screensharing, etc.) • Physical Interim Meetings • Meetecho “IETF-style” • Would need local support and custom setup (mixers, webcams, etc.) Are we going towards a completely Virtual IETF meeting too? • First discussions started for Buenos Aires (Zika virus risk) • Discussion restarted recently for entirely different reasons...
  39. 39. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Interim Meetings? Why not! • Two different types, typically • Virtual Interim Meetings (everybody online) • Physical Interim Meetings (mostly local, some remotes) • Virtual Interim Meetings • Meetecho as web conferencing platform • Several tools available (audio, video, chat, screensharing, etc.) • Physical Interim Meetings • Meetecho “IETF-style” • Would need local support and custom setup (mixers, webcams, etc.) Are we going towards a completely Virtual IETF meeting too? • First discussions started for Buenos Aires (Zika virus risk) • Discussion restarted recently for entirely different reasons...
  40. 40. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps What to do next? • Keep the WebRTC implementation aligned • We don’t want to wake up one day and nothing works anymore! • We’re not forgetting other browsers • Edge already supported, but only did H.264 so far... • ... although dev versions should have VP8 now? • Improve the monitoring/troubleshooting tools • Self-test application helped greatly • Event Handlers could help even more • Scale Scale Scale! Test Test Test! • Remote users will very likely increase (especially from “some” countries...) See you in Chicago for IETF 98! • https://ietf98.conf.meetecho.com/ • https://www.ietf.org/meeting/98/remote-participation.html
  41. 41. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps What to do next? • Keep the WebRTC implementation aligned • We don’t want to wake up one day and nothing works anymore! • We’re not forgetting other browsers • Edge already supported, but only did H.264 so far... • ... although dev versions should have VP8 now? • Improve the monitoring/troubleshooting tools • Self-test application helped greatly • Event Handlers could help even more • Scale Scale Scale! Test Test Test! • Remote users will very likely increase (especially from “some” countries...) See you in Chicago for IETF 98! • https://ietf98.conf.meetecho.com/ • https://www.ietf.org/meeting/98/remote-participation.html
  42. 42. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps What to do next? • Keep the WebRTC implementation aligned • We don’t want to wake up one day and nothing works anymore! • We’re not forgetting other browsers • Edge already supported, but only did H.264 so far... • ... although dev versions should have VP8 now? • Improve the monitoring/troubleshooting tools • Self-test application helped greatly • Event Handlers could help even more • Scale Scale Scale! Test Test Test! • Remote users will very likely increase (especially from “some” countries...) See you in Chicago for IETF 98! • https://ietf98.conf.meetecho.com/ • https://www.ietf.org/meeting/98/remote-participation.html
  43. 43. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps What to do next? • Keep the WebRTC implementation aligned • We don’t want to wake up one day and nothing works anymore! • We’re not forgetting other browsers • Edge already supported, but only did H.264 so far... • ... although dev versions should have VP8 now? • Improve the monitoring/troubleshooting tools • Self-test application helped greatly • Event Handlers could help even more • Scale Scale Scale! Test Test Test! • Remote users will very likely increase (especially from “some” countries...) See you in Chicago for IETF 98! • https://ietf98.conf.meetecho.com/ • https://www.ietf.org/meeting/98/remote-participation.html
  44. 44. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps What to do next? • Keep the WebRTC implementation aligned • We don’t want to wake up one day and nothing works anymore! • We’re not forgetting other browsers • Edge already supported, but only did H.264 so far... • ... although dev versions should have VP8 now? • Improve the monitoring/troubleshooting tools • Self-test application helped greatly • Event Handlers could help even more • Scale Scale Scale! Test Test Test! • Remote users will very likely increase (especially from “some” countries...) See you in Chicago for IETF 98! • https://ietf98.conf.meetecho.com/ • https://www.ietf.org/meeting/98/remote-participation.html
  45. 45. IETFWebRTC L. Miniero History Legacy ways A novel approach Remote participation Janus Architecture Troubleshooting Sessions Participation Director room Recordings Next steps Questions? @elminiero @meetecho

×