This specification supports {{MediaDecodingType}} values of {{file}}, {{media-source}} or {{webrtc}} as well as {{MediaEncodingType}} - values of {{record}} and {{webrtc}}. In [[webrtc]], signaling and - media paths are distinct, so that media may flow between peers without - passing through a web site. It is therefore necessary for applications - to negotiate communications parameters between peers, including the codecs - to be used to send and receive media. A WebRTC peer can send media - received by dozens or even hundreds of receivers, and applications can - rely on external services, including video conferencing servers, - transcoders or audio conferencing bridges. To enable communications at - scale, it is necessary for applications to ensure that configuration is - consistent across media senders and receivers, rather than just allowing + values of {{record}} and {{webrtc}}. +
++ In [[webrtc]], signaling and media paths are distinct, so that media can + flow between peers without passing through a web site. To improve scalability, + applications can rely on external services, including video conferencing servers, + transcoders or audio conferencing bridges. Using these services, a WebRTC peer can + send media received by dozens or even hundreds of receivers. +
++ To make it possible for participants to send and receive media at scale, + it is necessary for applications to ensure that communication parameters + (including codecs) are consistent across senders and receivers. This + requires negotiation between application peers, rather than just allowing browsers to "pick the one they like best".