Re: Call for Consensus (CfC) on Adoption of the Insertable Streams API specification

I support publishing the Insertable Streams API draft as WEBRTC WG deliverable. 
Having the repo in the WebRTC WG will make it easier to gather more feedback. The contribution framework will be clearer as well.

As discussed during last interim, I have some concerns related to privacy, security and the overall processing model.
I started to file some issues on Harald repo.
 Y

> On 28 May 2020, at 18:29, Bernard Aboba <Bernard.Aboba@microsoft.com> wrote:
> 
> Speaking just for myself (Chair Hat off), I support adoption of the Insertable Streams API as a WEBRTC WG deliverable. 
> 
> I have also filed two issues: 
> 
> Issue 31 <https://github.com/alvestrand/webrtc-media-streams/issues/31>: Interaction with congestion control
> Issue 32 <https://github.com/alvestrand/webrtc-media-streams/issues/32>: Applicability statement
> Issue 31 relates to the Virtual Reality Gaming  <https://w3c.github.io/webrtc-nv-use-cases/#vr*>use case, in which metadata (which could be of considerable size) is inserted so that it can be carried along with the frame. 
> 
> Issue 32 relates to the potential limitations of this API which might be described in an Applicability statement.
> From: Bernard Aboba <Bernard.Aboba@microsoft.com>
> Sent: Thursday, May 28, 2020 9:00 AM
> To: public-webrtc@w3.org <public-webrtc@w3.org>
> Subject: Call for Consensus (CfC) on Adoption of the Insertable Streams API specification
>  
> This is a Call for Consensus (CfC) to adopt "WebRTC Insertable Media Using Streams" as a WEBRTC WG deliverable. 
> 
> Note that adoption as a WEBRTC WG deliverable implies only that the specification is suitable as a starting point. 
> 
> The specification is located here: https://alvestrand.github.io/webrtc-media-streams/ <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Falvestrand.github.io%2Fwebrtc-media-streams%2F&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C55e00358db8d437896b708d803207bf4%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637262785339243950&sdata=XtoyK3HkkOQ1kmz1HXplhX7qNY7jukuFrWi%2BqSLAS40%3D&reserved=0>
> The Github repo is here: https://github.com/alvestrand/webrtc-media-streams <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Falvestrand%2Fwebrtc-media-streams&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C55e00358db8d437896b708d803207bf4%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637262785339243950&sdata=2dj26BWswIKzkydbNCf%2Fkcg%2FEJ0ha85xk76G5xCvNxA%3D&reserved=0>
> 
> The WebRTC-NV use cases document is available here: https://w3c.github.io/webrtc-nv-use-cases/ <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fwebrtc-nv-use-cases%2F&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C55e00358db8d437896b708d803207bf4%7C72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637262785339253894&sdata=uoiTa8gWGoN88YEj7y6R4yzqUkLsbWKwvIhxjJJDKn4%3D&reserved=0>
> 
> The CfC will last for one week, and will end on Friday, June 5, 2020 at 16:00 UTC. 
> 
> In response, please state one of the following: 
> I support publishing the Insertable Streams API draft as WEBRTC WG deliverable. 
> I object to adopting the current Insertable Streams API draft as a WEBRTC WG work item, due to issues filed in open bug <#number>. 
> Note that time has been reserved at the June 4, 2020 virtual interim (see previous message) for discussion of the Insertable Streams API. 
> 
> 
> Bernard, for the Chairs