This document derives requirements related to webrtc from the use case document, published in IETF, for web real-time communication. For now, exactly the same reqs as listed in that document are repeated here. On a longer term it would probably make sense to split that document up in a use-case part to be common for IETF and W3C and into requirement parts. The requirements related to webrtc should be published in this document.
| Requirement # | Name | Description |
|---|---|---|
| P1 | TBD | The User Agent MUST ensure user consent is given before allowing the application access to device resources such as camera and microphone. |
| P2 | TBD | The User Agent MUST provide an intuitive way for the user to revoce consent to use application access to device resources such as camera and microphone. |
| P3 | TBD | The User Agent MUST make obvious to the user that device resources such as camera and microphone are in use. |
| Requirement # | Name | Description |
|---|---|---|
| A1 | TBD | The web application MUST be able to query the user about the usage of cameras and microphones as input devices. |
| A2 | TBD | The web application MUST be able to control how streams generated by input devices are used. |
| A3 | TBD | The web application MUST be able to control the local rendering of streams (locally generated streams and streams received from a peer). |
| A4 | TBD | The web application MUST be able to initiate sending of stream/stream components to a peer. |
| A5 | TBD | The web application MUST be able to control the media format (codec) to be used for the streams sent to a peer. NOTE: The level of control depends on whether the codec negotiation is handled by the User Agent or the web application. |
| A6 | TBD | After a media stream has been established, the web application MUST be able to modify the media format for streams sent to a peer. |
| A7 | TBD | The web application MUST be made aware of whether the establishment of a stream with a peer was successful or not. |
| A8 | TBD | The web application MUST be able to pause/unpause the sending of a stream to a peer. |
| A9 | TBD | The web application MUST be able to mute/unmute a stream received from a peer. |
| A10 | TBD | The web application MUST be able to cease the sending of a stream to a peer. |
| A11 | TBD | The web application MUST be able to cease processing and rendering of a stream received from a peer. |
| A12 | TBD | The web application MUST be informed when a stream from a peer is no longer received. |
| A13 | TBD | The web application MUST be informed when high loss rates occur. |
| A14 | TBD | It MUST be possible for the web application to control panning, mixing and other processing for individual streams. |
| A15 | TBD | The web application MUST be able to identity the context of a stream. |
| A16 | TBD | It MUST be possible for the web application to send and receive datagrams to/from peer |
TBA.