design-reviews#1026: WebRTC API Proposed Amendments

#1026: WebRTC API Proposed Amendments

Visit on Github.

Opened Dec 10, 2024

こんにちは TAG-さん!

I'm requesting a TAG review of Proposed Amendments to the WebRTC API.

Explainer¹: N/A
Specification: https://www.w3.org/TR/2024/REC-webrtc-20241008/#proposed-amendments (this review focuses only on proposed amendments)
WPT Tests: https://github.com/web-platform-tests/wpt/tree/master/webrtc/ (https://www.w3.org/2024/10/webrtc-amendments-interop.html for links to tests specifically tied to the proposed amendments)
User research: N/A
Security and Privacy self-review²: https://github.com/w3c/webrtc-pc/issues/265#issuecomment-147394405 - not changed by the proposed amendments as far as we could determine
GitHub repo: https://github.com/w3c/webrtc-pc/
Primary contacts:
- Dominique Hazael-Massieux (@dontcallmedom), W3C, staff contact
Organization/project driving the specification: W3C WebRTC WG
Multi-stakeholder support³: all the proposed amendments have received at least double implementation (see implementation report

Further details:

I have reviewed the TAG's Web Platform Design Principles
Relevant time constraints or deadlines: would like to proceed with updated Rec ASAP (other wide review deadlines set to Jan 31st 2025)
The group where the work on this specification is currently being done: WebRTC WG
The group where standardization of this work is intended to be done (if different from the current group): idem
Major unresolved issues with or opposition to this specification: N/A
This work is being funded by: W3C

Discussions

Discussed Feb 17, 2025 (See Github)

Lola: I've looked at this for privacy review - in the private repo I've made one comment - an attack vector. ICE candidate default to be ALL. Before it didn't have a default... This is in alignment with the relevant RFC...

Martin: in Firefox the default is set to ALL.

Lola: so don't think it's an issue...

Martin: there's the policy the web site sets and the policy the browser sets... So I think in this case even though the web site default is everything they don't get everything... I think we're OK.

Marking as "focus: privacy - complete".

Still need a11y feedback and Jeffrey had input. Though we concluded that Jeffrey's issue was captured, we don't need to pile on, so marking API review as complete also.

Martin: they are on it....

Martin: the small changes - changing of the plumbing...

sets other review labels to complete

We hold off until we get Matthew's feedback and we can close it next week.

Discussed Feb 24, 2025 (See Github)

Lola: we agreed it's probably fine .. waiting for Matthew .. to do an a11y review ... To catch folks up .. these changes are minor for WebRTC ... brings spec into alignment with RFC... some already implemented in browsers...

Matthew: our [APA]'s RTC experts have looked at it and I think are ok with it, but I will check before the plenary ... there may have been a trade-off with privacy? I'll confirm

re-address at plenary

Comment by @matatk Feb 28, 2025 (See Github)

Hi @dontcallmedom, thank you for your review request. We have looked through it, and discussed it this week, and are happy to close this as satisfied.