Re: Media Capture and Streams Last Call review

As I recall, we also had an issue with the timing of UA interactions with
the user regarding permissions to access some device, in that we didn't
want access requests to the user to be displayed during device
interrogation, only at the point of device access. However, I recall that
Harald made the point that without this UA interaction, device
fingerprinting would be very readily accessible without the user knowing.
This may be part of the reasoning for making MediaStreamSettings only
available in the result from getUserMedia().

Does the group see this point addressed in the current spec? I don't, but
perhaps I've missed it.

How might this affect Bill's point or the proposal I sent in response?


On Wed, Apr 15, 2015 at 8:27 AM, Joe Berkovitz <joe@noteflight.com> wrote:

> Hi Group,
>
> This solicitation for feedback is a perfect moment to address once again
> the problems with audio device identification and access that we had
> discussed at the last F2F. I have not yet had a chance to look at this
> latest draft (I'm at a trade show this week), but if you are involved in
> this issue, could you please examine it as some of the content may have
> changed. Please post to the group this week if you have any additional
> observations on this subject after reading the draft, and we can discuss on
> tomorrow's conference call.
>
> ...Joe
>
> ---------- Forwarded message ----------
> From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
> Date: Wed, Apr 15, 2015 at 7:31 AM
> Subject: Media Capture and Streams Last Call review
> To: "rubys@intertwingly.net" <rubys@intertwingly.net>, "
> Paul.Cotton@microsoft.com" <Paul.Cotton@microsoft.com>, "mjs@apple.com" <
> mjs@apple.com>, "chaals@yandex-team.ru" <chaals@yandex-team.ru>, "
> art.barstow@gmail.com" <art.barstow@gmail.com>, "joe@noteflight.com" <
> joe@noteflight.com>, "matthew.paradis@bbc.co.uk" <
> matthew.paradis@bbc.co.uk>, "hillbrad@fb.com" <hillbrad@fb.com>, "
> dveditz@mozilla.com" <dveditz@mozilla.com>, "w3c@adambarth.com" <
> w3c@adambarth.com>, "Virginie.GALINDO@gemalto.com" <
> Virginie.GALINDO@gemalto.com>, "yosuke@funahashi.cc" <yosuke@funahashi.cc>,
> "giuseppep@opera.com" <giuseppep@opera.com>, "
> mark_vickers@cable.comcast.com" <mark_vickers@cable.comcast.com>, "
> runnegar@isoc.org" <runnegar@isoc.org>, "tjwhalen@google.com" <
> tjwhalen@google.com>, "daniel.appelquist@telefonica.com" <
> daniel.appelquist@telefonica.com>, "peter.linss@hp.com" <
> peter.linss@hp.com>, "janina@rednote.net" <janina@rednote.net>
> Cc: "Chairs@w3.org Chairs" <Chairs@w3.org>
>
>
> The WebRTC and Device APIs Working Groups request feedback on the Last
> Call Working Draft of Media Capture and Streams, a JavaScript API that
> enables access to cameras and microphones from Web browsers as well as
> control of the use of the data generated (e.g. rendering what a camera
> captures in a html video element):
> http://www.w3.org/TR/2015/WD-mediacapture-streams-20150414/
>
> The groups have identified the following other W3C Working Groups as
> likely sources of feedback:
>
> - HTML Working Group, especially the HTML Media Task Force, as our API
> extends the HTMLMediaElement interface and defines a new type of media
> input via MediaStream
>
> - WebApps Working Group, especially on the overall usage of Web IDL and
> the definition of error handling
> Audio Working Group, as the Web Audio API builds upon the MediaStream
> interface
>
> - WAI Protocol and Formats Working Group, especially on the impact of
> the user consent dialog and the applicability of the indicators of
> device usage in assistive tools
>
> - Web and TV Interest Group, as the manipulation of media input can be
> relevant to some of their use cases (e.g. glass to glass)
>
> - Web App Security Working Group, especially on our links between
> secured origins and persistent permissions, and our current policy with
> regard to handling access to this "powerful feature"
>
> - Web Security Interest Group, especially on our security considerations
> Privacy Interest Group, as access to camera and microphone has strong
> privacy implications
>
> - Technical Architecture Group, for an overall review of the API,
> especially the introduction of the concept of a IANA registry-based
> constraints system, the use of promises, and our handling of persistent
> permissions
>
> We naturally also welcome feedback from any other reviewers.
>
> The end of last call review for this specification is set to May 15
> 2015; should that deadline prove difficult to meet, please get in touch
> so that we can determine a new deadline for your group.
>
> As indicated in the document, comments should be sent to the
> public-media-capture@w3.org mailing list.
>
> Thanks,
>
> Frederick Hirsch, Device APIs Working Group Chair,
> Harald Alvestrand and Stefan Hakansson, WebRTC Working Group Chairs and
> Media Capture Task Force Chairs
>
>
>
> --
> .            .       .    .  . ...Joe
>
> *Joe Berkovitz*
> President
>
> *Noteflight LLC*
> Boston, Mass.
> phone: +1 978 314 6271
> www.noteflight.com
> "Your music, everywhere"
>



-- 
.            .       .    .  . ...Joe

*Joe Berkovitz*
President

*Noteflight LLC*
Boston, Mass.
phone: +1 978 314 6271
www.noteflight.com
"Your music, everywhere"