On Thursday, November 18, 2021 at 5:27:14 PM UTC+1 Daniel Bratell wrote:

> I'm sure this can be extended, but just a couple of questions.
>
> 1. Do you have a link to the usage counter?
>
Links from Chrome Platform Status:
According to this data, Plan B usage is this 0.23% of overall WebRTC usage, 
(Plan B usage / (Plan B + Unified Plan usage)).

Unified Plan usage: 7.497188%
https://www.chromestatus.com/metrics/feature/popularity#RTCPeerConnectionConstructedWithUnifiedPlan
Plan B usage: 0.01732%
https://www.chromestatus.com/metrics/feature/popularity#RTCPeerConnectionConstructedWithPlanB

Links from UMA pages:
According to this data, Plan B usage is 0.5-0.8% of overall WebRTC usage.

The measure of "complex" SDP, i.e. the type of SDP that has compatibility 
issues between Unified Plan and Plan B, is 0.5% of overall usage according 
to UMA:
https://uma.googleplex.com/p/chrome/timeline_v2?sid=7dcca6fc2206a505d294d751929d13b5

The overall Plan B usage of the sdpSemantics attribute, regardless of SDP 
complexity, is 0.8%:
https://uma.googleplex.com/p/chrome/timeline_v2?sid=1e78b551689e230b00528fe0c621dd7e

>
> 2. What feedback have you had during the deprecation /reverse origin trial 
> so far?
>

Early in the trial I got feedback that file:// URLs needed to be able to 
use Plan B because local files cannot sign up for Deprecation Trial, so we 
made it so that local files can use Plan B during the trial.
In email conversations with affected companies, usually they communicated a 
timeline and they kept to it, providing no feedback, just migrating 
successfully without reporting issues.
In one instance a bug was found and communicated via email, and I fixed a 
couple of bugs filled on crbug before the trial, but I have gotten no 
reports since ~M93.
I was contacted by one company who was unaware of the deprecation recently, 
and extending the Deprecation Trial was the result of that exchange.

/Daniel
> On 2021-11-18 11:57, Henrik Boström wrote:
>
> *Contact emails* 
> [email protected], [email protected], [email protected]
>
> *Specification*
> WebRTC is a W3C Recommendation and multiple IETF standards:
> https://www.w3.org/2021/01/pressrelease-webrtc-rec.html.en
>
> *Summary*
> WebRTC is a set of JavaScript API used to send and receive audio, video 
> and data between endpoints. Most Video Conferencing services are built on 
> WebRTC.
>
> In order to set up a connection, the SDP protocol is used. The 
> spec-compliant and cross-browser compatible version of SDP is called 
> "Unified Plan". In contrast, "Plan B" is a non-standard version of SDP only 
> available in Chromium-based browsers using a non-standard API.
>
> "Plan B" was deprecated in M93 Canary but due to high usage, a Deprecation 
> Trial was added, allowing registered websites to make use of "Plan B" until 
> Dec 29, 2021 (a couple of days before the M97 Stable release). See previous 
> intent 
> to experiment/deprecate 
> <https://groups.google.com/u/3/a/chromium.org/g/blink-dev/c/35NFPYdumMs/m/1YqxqH0_BAAJ>
>  for 
> more details.
>
> With this request we would like to have an extended Deprecation Trial 
> until May 24, 2022 (M102 Stable Release date).
>
> *Blink component*
> Blink>WebRTC 
> <https://bugs.chromium.org/p/chromium/issues/list?q=component%3ABlink%3EWebRTC&can=2>
>
> *Search tags*
> WebRTC SDP Plan B Unified Plan 
> <https://www.chromestatus.com/features#tags:WebRTC%20SDP%20Plan%20B%20Unified%20Plan>
>  
>
> *Interoperability and Compatibility*
> Unified Plan is shipped-by-default in all major browsers. Plan B, the 
> feature which we are deprecating, it is the one that has interoperability 
> and compatibility risks. UP and PB clients can talk to each other, but in 
> "complex" setups that requires non-trivial SDP translation.
>
>
> *Goals for experimentation*
> Reduce risk of breakage. Give websites that still depend on Plan B more 
> time to migrate to Unified Plan without delaying the removal for the rest 
> of the web.
>
>
> *Reason this experiment is being extended*
> When the deprecation announcement was made, "Plan B" was used by the 
> majority of WebRTC Video Conferencing use cases. Today, "Plan B" is used by 
> less than 0.7% of WebRTC use cases. The deprecation is having the desired 
> effect.
>
> However, in order to reduce risk while usage was still high, "Plan B" was 
> only throwing an exception in the Canary release channel as of M93. We are 
> now making "Plan B" throw in Stable for M96, but this has also meant that 
> despite our communication efforts and 1 year time frame, there exists 
> services who discovered the deprecation late and need more time.
>
> By having an extended Deprecation Trial until May 24, 2022, we are 
> providing services that started migration late with enough time to migrate 
> to Unified Plan safely.
>
> *Link to entry on the Chrome Platform Status*
> https://www.chromestatus.com/feature/5823036655665152
>
> *Link to previous Intent to Experiment:*
>
> https://groups.google.com/u/3/a/chromium.org/g/blink-dev/c/35NFPYdumMs/m/1YqxqH0_BAAJ
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/9e63fc40-d23a-494b-bf1a-a9693b24c893n%40chromium.org
>  
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/9e63fc40-d23a-494b-bf1a-a9693b24c893n%40chromium.org?utm_medium=email&utm_source=footer>
> .
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/fc4afdf9-3e11-4373-9747-7052f7ae305dn%40chromium.org.

Reply via email to