W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > July 2019

Re: [webrtc-pc] Permission API for receive-only media and data use cases (#2175)

From: Lennart Grahl via GitHub <sysbot+gh@w3.org>
Date: Tue, 16 Jul 2019 17:50:11 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-511918973-1563299409-sysbot+gh@w3.org>
>     * Permission name and values (permissions spec)

IIRC Youenn opened the discussion regarding the name of the permission. I have not found a better fitting name than `direct-connection` even though it obviously does not prevent a *direct connection* from being established without granting it.
What the permission actually does is switch between the *best available IP handling mode* and the *default IP handling mode*. Thus, the most fitting name I can think of is `best-available-ip-handling-mode`... which is not what I'd suggest to use. Just clarifying, it's hard to find a good name for the permission and if we want something other than `direct-connection`, I'm open for suggestions.

This is the proposed change towards the permission spec so far, PTAL: https://github.com/w3c/permissions/compare/master...lgrahl:direct-connection
Will make a PR tomorrow.

>     * Use cases and justification (webrtc-nv-use-cases)

NV Use Cases PR is here: https://github.com/w3c/webrtc-nv-use-cases/pull/14
Anything else I need to do here?

>     * API for requesting the permission (either here or an extension spec).

Harald, can you clarify again what you think should be changed regarding the API? Jan-Ivar and I tend towards keeping the static method as it seems useful in describing the application's intent more clearly.
I'm not entirely sure about the event, yet.

GitHub Notification of comment by lgrahl
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/2175#issuecomment-511918973 using your GitHub account
Received on Tuesday, 16 July 2019 17:50:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:25 UTC