[Urgent Support]
Hi,
Is there any possibility to extend the Trial for RTCPeerConnection Plan B
SDP Semantics?
We are helping our client on the call center video solution. However, we
have a big issue regarding this trial support end on May 25th 2022. Please
advise. Thank you for your support in advance.
Web Development 在 2021年12月17日 星期五上午12:22:55 [UTC+8] 的信中寫道：
> I registered for RTCPeerConnection Plan B SDP Semantics and everything
> working fine in windows and android chrome browser.
> But in android webView it showing Origin trial "UNKNOWN
> ValidTokenNotProvided"
> Does it support in android system webview?
>
> On Friday, July 30, 2021 at 2:25:18 AM UTC+5:30 mike...@chromium.org
> wrote:
>
>> Hi Abhi,
>>
>> Assuming you're looking for the deprecation trial ("reverse origin
>> trial") for Plan B SDP semantics,
>> https://developer.chrome.com/origintrials/#/view_trial/3892235977954951169
>> should be the right link.
>>
>> (there's no visual differentiation between regular and deprecation trials
>> in the UI, but maybe that would be a nice feature to add)
>>
>> later,
>> Mike
>>
>> On 7/29/21 3:44 AM, 'Abhi Shanmu' via blink-dev wrote:
>>
>> Hi,
>>
>> I am unable to find reverse origin trial listed in this page for me to
>> register.
>> https://developer.chrome.com/origintrials/#/trials/active
>> How can I register my domains for the reverse origin trial?
>> Thanks,
>> Abhi
>> On Thursday, July 8, 2021 at 5:00:06 PM UTC+1 Yash Gogia wrote:
>>
>>> Hi,
>>>
>>> The guide that talks about origin trials, mentions that there is a
>>> built-in safeguard that automatically disables an experimental feature
>>> globally if its usage exceeds 0.5% of all Chrome page loads.
>>>
>>> Source:
>>> https://github.com/GoogleChrome/OriginTrials/blob/gh-pages/developer-guide.md#3-what-happens-if-a-large-site-such-as-a-google-service-starts-depending-on-an-experimental-feature
>>>
>>> I would like to understand if this applies to reverse origin trials as
>>> well. From chrome status, it looks like the usage is hovering around 0.2%
>>> already and I am sure many more websites would add the trial as the August
>>> date for Chrome 93 approaches. A confirmation that this automatic cutoff
>>> would not apply to the reverse origin trial would give us a lot more
>>> confidence.
>>>
>>> Thanks,
>>> Yash
>>> On Friday, 5 March 2021 at 23:18:03 UTC+5:30 Joe Medley wrote:
>>>
>>>> Thank you!
>>>>
>>>> Joe Medley | Technical Writer, Chrome DevRel | jme...@google.com |
>>>> 816-678-7195 <(816)%20678-7195>
>>>> *If an API's not documented it doesn't exist.*
>>>>
>>>>
>>>> On Fri, Mar 5, 2021 at 6:47 AM Henrik Boström <hb...@webrtc.org> wrote:
>>>>
>>>>> OK, I filed https://www.chromestatus.com/feature/5823036655665152
>>>>>
>>>>> On Tuesday, March 2, 2021 at 3:45:06 PM UTC+1 Joe Medley wrote:
>>>>>
>>>>>> To be clear, Chrome Status isn't extra. It's a tool for creating
>>>>>> intents and it tries to help you get everything needed for that. The
>>>>>> option
>>>>>> for Feature deprecation contains a stage for a reverse origin trial.
>>>>>>
>>>>>> [image: image.png]
>>>>>>
>>>>>> Joe Medley | Technical Writer, Chrome DevRel | jme...@google.com |
>>>>>> 816-678-7195 <(816)%20678-7195>
>>>>>> *If an API's not documented it doesn't exist.*
>>>>>>
>>>>>>
>>>>>> On Tue, Mar 2, 2021 at 6:40 AM Joe Medley <jme...@google.com> wrote:
>>>>>>
>>>>>>> "Should I create an entry even for the Reverse Origin Trial?"
>>>>>>>
>>>>>>> Yes, you should.
>>>>>>> Joe Medley | Technical Writer, Chrome DevRel | jme...@google.com |
>>>>>>> 816-678-7195 <(816)%20678-7195>
>>>>>>> *If an API's not documented it doesn't exist.*
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Feb 18, 2021 at 2:05 AM Henrik Boström <hb...@chromium.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> *Contact emails*
>>>>>>>> hb...@chromium.org, h...@chromium.org
>>>>>>>>
>>>>>>>> *Spec*
>>>>>>>> WebRTC is a W3C Recommendation and multiple IETF standards:
>>>>>>>> https://www.w3.org/2021/01/pressrelease-webrtc-rec.html.en
>>>>>>>> https://www.w3.org/TR/webrtc/
>>>>>>>> https://tools.ietf.org/html/rfc8829
>>>>>>>>
>>>>>>>> The Session Description Protocol (SDP) used by WebRTC currently has
>>>>>>>> two implementations:
>>>>>>>>
>>>>>>>> - "Unified Plan", the spec-compliant SDP format implemented by
>>>>>>>> all browsers.
>>>>>>>> - "Plan B", the non-standard SDP format that does not have a
>>>>>>>> spec, is deprecated but not yet removed and is only implemented in
>>>>>>>> Chromium-based browsers. JavaScript applications have access to it
>>>>>>>> by using
>>>>>>>> a non-standard API.
>>>>>>>>
>>>>>>>> *Summary*
>>>>>>>> We want to remove the non-standard SDP format, "Plan B", from
>>>>>>>> Chromium. Removal dates have already been announced, but in order to
>>>>>>>> aid
>>>>>>>> applications from migrating from Plan B to Unified Plan and to ensure
>>>>>>>> we
>>>>>>>> can keep the deadlines we have set, a Reverse Origin Trial is desired
>>>>>>>> to
>>>>>>>> give applications that opt-in more time to migrate.
>>>>>>>>
>>>>>>>> Deadlines and rationale for Reverse Origin Trial were provided in
>>>>>>>> the intent to deprecate
>>>>>>>> <https://groups.google.com/u/3/a/chromium.org/g/blink-dev/c/IY2amIigFFs>.
>>>>>>>>
>>>>>>>> The target dates are:
>>>>>>>>
>>>>>>>> -
>>>>>>>>
>>>>>>>> M89 (Stable in February, 2021): Deprecation warning is added in
>>>>>>>> the developer console.
>>>>>>>> -
>>>>>>>>
>>>>>>>> M93 (Stable in August, 2021): Plan B is removed, with the
>>>>>>>> option to extend this deadline by opting-in to a Reverse Origin
>>>>>>>> Trial.
>>>>>>>> -
>>>>>>>>
>>>>>>>> M96 (Stable in January, 2022): The extended deadline ends
>>>>>>>> and Plan B is removed for everybody.
>>>>>>>>
>>>>>>>> I would like to make the Reverse Origin Trial available as of M90
>>>>>>>> or M91 (when this CL
>>>>>>>> <https://chromium-review.googlesource.com/c/chromium/src/+/2671784>
>>>>>>>> lands).
>>>>>>>>
>>>>>>>> *Goals for experimentation*
>>>>>>>> Unblock Plan B removal.
>>>>>>>>
>>>>>>>> *Experiment timeline*
>>>>>>>> M90-M96.
>>>>>>>>
>>>>>>>> *Any risk when the experiment finishes?*
>>>>>>>> If Plan B is removed while still in use, some applications would
>>>>>>>> experience incompatibility issues when attempting to set up audio or
>>>>>>>> video
>>>>>>>> channels, especially in multi-participant conferencing setups. 1:1
>>>>>>>> calling
>>>>>>>> will still work for some applications.
>>>>>>>>
>>>>>>>> *Ongoing technical constraints*
>>>>>>>> N/A. There were some Unified Plan bugs and performance issues
>>>>>>>> discovered that have been addressed in M90.
>>>>>>>>
>>>>>>>> *Debuggability*
>>>>>>>> When using Plan B you will get a deprecation warning in the JS
>>>>>>>> console. It will look different depending on if you have opted in to
>>>>>>>> the
>>>>>>>> Reverse Origin Trial.
>>>>>>>>
>>>>>>>> *Will this feature be supported on all five Blink platforms
>>>>>>>> supported by Origin Trials (Windows, Mac, Linux, Chrome OS, and
>>>>>>>> Android)?*
>>>>>>>> Yes.
>>>>>>>>
>>>>>>>> *Link to entry on the feature dashboard
>>>>>>>> <https://www.chromestatus.com/features>*
>>>>>>>> N/A, Unified Plan was shipped several years ago. Should I create an
>>>>>>>> entry even for the Reverse Origin Trial?
>>>>>>>>
>>>>>>>> --
>>>>>>>> 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 blink-dev+...@chromium.org.
>>>>>>>> To view this discussion on the web visit
>>>>>>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/2abac3cf-72ee-43c6-b248-c60e625ee881n%40chromium.org
>>>>>>>>
>>>>>>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/2abac3cf-72ee-43c6-b248-c60e625ee881n%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 blink-dev+...@chromium.org.
>>
>> To view this discussion on the web visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/02d760be-eea7-45f5-943e-bfc04a16bb56n%40chromium.org
>>
>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/02d760be-eea7-45f5-943e-bfc04a16bb56n%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 blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/96946666-39cf-4d8b-9927-0be2413a4637n%40chromium.org.
