WebRTC Next Version Use Cases Status

Hi all,

Just as a reminder of current status on our recent WebRTC review here is 
an overview of the use case status - we will continue with this on the 
next RQTF meeting tomorrow (at 9am EST). [1]

The following are the shortlist from the last review and should be 
helpful for you to note. Some of these are candidates for possible 
removal from the list of use cases as they may relate to the work of a 
different group, or indeed just need more discussion. The ones that may 
be removed as not being specific WebRTC related (but still potential 
valid use cases) are listed with **.

Here are the minutes from that RQTF call. [2]

  * *Identify Caller ** *- Maybe handled by other spec - needs flow
    chart. [3]
  * *Incoming calls *- More research needed - could be covered by other
    specs.
  * *Multiple Audio *** - More discussion needed to be sure this is NOT
    a WebRTC thing.
  * *Communications control of alternate content* ** - HTML supports
    this, the streams need to be separable. May not be a WebRTC thing or
    an application implementation.
  * *Accessible Call Set up *** Could be covered, need a second opinion.
    Can be removed as its application level issue.
  * *Text communication data channel *** - May not be WebRTC specific.

This one was missed during the last call - can be discussed tomorrow.*
*

  * *Accessible Call Set up* (MISSED)

I hope this helps, thanks.

Josh

[1] https://www.w3.org/WAI/APA/wiki/WebRTC_next_version_use_cases

[2] https://www.w3.org/2019/05/22-rqtf-minutes.html

[3] https://w3c.github.io/webrtc-identity/identity.html

-- 
Emerging Web Technology Specialist/A11y (WAI/W3C)