Re: [rtcweb] Mute implementations (Re: More Comments ondraft-ietf-rtcweb-use-cases-and-requirements-07)

[Harald Alvestrand <[e-mail]>]

On 06/17/2012 04:17 PM, Jim Barnett wrote:
>
> I still think that there is a significant difference between 
> files/images and live sources.  A live source provides a lot of 
> information about my environment -- what's going on, whether I have 
> shaved, etc.  The file or image source that we use for hold is 
> designed to provide _/no/_ information about my environment.  In a 
> user's mind, showing "please wait" or a  images of a waterfall is very 
> different from showing anything _/live/_ from his environment, and we 
> may want to reflect that difference in the requirements.  For example, 
> does the user have to give explicit permission to show the "Please 
> wait" source when the call is put on hold, or is that configured as a 
> default in the browser?  (The latter, I'd  think, which makes it 
> different from the front and rear cameras.)
>
>
I agree with respect to the needed permissions; this is mostly a 
language issue.

I think we will have some applications (like the shared YouTube viewer 
in hangouts) where a stored medium is the most important piece of the 
app - but I don't think that means we need special access procedures for 
it (the "file upload" dialog for getting permissions to access a file 
should be sufficient), and for resources that are already accessible to 
the Web app, like images loaded to the page - I see absolutely no reason 
to put extra requirements on it.

But as I said - Media task force.