Skip to content

Commit

Permalink
Insertable streams is worth prototyping
Browse files Browse the repository at this point in the history
Closes mozilla#330.
  • Loading branch information
martinthomson committed Oct 22, 2020
1 parent 5742832 commit 3e350ea
Showing 1 changed file with 13 additions and 0 deletions.
13 changes: 13 additions & 0 deletions activities.json
Original file line number Diff line number Diff line change
Expand Up @@ -1268,6 +1268,19 @@
"title": "Web Thing API",
"url": "https://iot.mozilla.org/wot/"
},
{
"ciuName": null,
"description": "This API defines an API surface for manipulating the bits on MediaStreamTracks being sent via an RTCPeerConnection.",
"id": "webrtc-insertable-streams",
"mdnUrl": null,
"mozBugUrl": null,
"mozPosition": "worth prototyping",
"mozPositionDetail": "This approach provides sites a way to offer a form of end-to-end protection for media, especially in those very common cases where media for group sessions is managed by a central service. The proposed API, together with the SFrame proposal, provides sites the ability to limit the information that is exposed to the central service. Mozilla would prefer to include better key management than this approach proposes, perhaps using <a href=\"https://datatracker.ietf.org/doc/html/draft-ietf-mls-architecture\">MLS</a>, which might guarantee certain security and privacy gains for users. However, we recognizes that this is not yet feasible and this API can provide security and privacy gains if carefully applied by sites.",
"mozPositionIssue": null,
"org": "W3C",
"title": "WebRTC Insertable Media using Streams",
"url": "https://w3c.github.io/webrtc-insertable-streams/"
},
{
"ciuName": "",
"description": "Use cases about providing guarantees to users about the privacy of their WebRTC videoconferencing when the servers are not trusted but the JavaScript is.",
Expand Down

0 comments on commit 3e350ea

Please sign in to comment.