Re: [rtcweb] WGLC of draft-ietf-rtcweb-use-cases-and-requirements-11

["Chenxin (Xin)" <[e-mail]>]

Hi Karl, 
>-----Original Message-----
>From: [e-mail] [mailto:[e-mail]] On Behalf Of
>Karl Stahl
>Sent: Saturday, September 21, 2013 8:16 AM
>To: [e-mail];
>[e-mail]
>Subject: [rtcweb] WGLC of draft-ietf-rtcweb-use-cases-and-requirements-11
>
>While reading the draft-ietf-rtcweb-use-cases-and-requirements-11, here are
>a few "telephony related" WebRTC things I think should be clarified in the
>use cases.
>
>
>3.2.1.  Simple Video Communication Service
>3.2.1.1.  Description
>...
>The invited user might accept or reject the session.
>[Suggest adding] The invited user might accept only audio, rejecting video
>(even if a camera is enabled). A user may also select to initiate an audio
>session, without video.
>
>And in API requirements:
>   ----------------------------------------------------------------
>   A1      The Web API must provide means for the application to ask the
>browser for permission to use cameras and microphones, individually as input
>devices. (One must be able to answer with voice only - declining video.)
>   ----------------------------------------------------------------

>Same under
>6.2.  Browser Considerations
>...
>The browser is expected to provide mechanisms for users to revise and even
>completely revoke consent to use device resources such as camera and
>microphone. [Suggest adding] Specifically, a user must be given the
>opportunity to only accept audio in a video call invitation.
>
[Xin] it is a common use case to accept only audio call and reject the video and quite useful. But I am doubt that this function should be mixed with video or audio device access permission . Do I misunderstand your proposal?  I think we could just disable the video stream when signaling. So we could make video call with one and reject it with other in the same web-service. I think the audio and video device access permission is not for each call(peer connection). 

Thanks,
   Xin