Re: [rtcweb] Remote recording - RTC-Web client acting as SIPREC session recording client

["Timothy B. Terriberry" <[e-mail]>]

Matthew Kaufman wrote:
> But this is a bad idea. Providing APIs that let a browser send audio
> that is being received from the other end to a third party open several
> different cans of worms simultaneously. One is that there's now another

The currently proposed MediaStream Processing API 
(http://hg.mozilla.org/users/rocallahan_mozilla.com/specs/raw-file/tip/StreamProcessing/StreamProcessing.html) 
essentially allows exactly this (including mixing). It doesn't make any 
distinction about whether the source of a MediaStream is a local camera, 
a <video> tag, or a remote stream from a PeerConnection object. So if 
you want to prevent this kind of thing, you need to have an active 
method of doing so, because by default the API will allow it.

> Not to mention all the protocol-level implications of being an RTP
> mixer, if we're trying to stay true to that particular choice of protocols.

That's a good point, and it's important to think about what the 
implications of those are, especially for a ProcessedMediaStream. This 
is not something I, personally, have thought all the way through yet.