Re: [Wish] Setup:active

[Harald Alvestrand <[e-mail]>]

FWIW, Chrome was handling this wrong (rejecting a=setup:active) until 
August 18.

https://crbug.com/webrtc/12933 - 95.0.4617.0 was the first version with 
the fix.

So we can say with some confidence that we don't have many clients 
sending "active".

On 9/9/21 9:00 PM, Juliusz Chroboczek wrote:

> Hi,
>
> In Section 4.2, I see the following mysterious passage:
>
>     Unlike [RFC5763] a WHIP client MAY use a setup attribute value of
>     setup:active in the SDP offer, in which case the WHIP endpoint MUST
>     use a setup attribute value of setup:passive in the SDP answer.
>
> After checking 5763, my understanding is that the offerer may choose to
> open the DTLS session, while in WebRTC the answerer chooses the party that
> opens the session, with the answerer being preferred.  Not a big deal, but
> requires some tweaks to WebRTC libraries for use with WHIP, and requires
> more testing.
>
> May I most humbly request an explanation of what advantages this is
> believed to provide?
>
> -- Juliusz
>