Re: [rtcweb] JSEP: Why always offer actpass?

Quoth RFC5763, Section 5:

   o  The endpoint MUST use the setup attribute defined in [RFC4145
<https://tools.ietf.org/html/rfc4145>].
      The endpoint that is the offerer MUST use the setup attribute
      value of setup:actpass and be prepared to receive a client_hello
      before it receives the answer.  The answerer MUST use either a
      setup attribute value of setup:active or setup:passive.  Note that
      if the answerer uses setup:passive, then the DTLS handshake will
      not begin until the answerer is received, which adds additional
      latency. setup:active allows the answer and the DTLS handshake to
      occur in parallel.  Thus, setup:active is RECOMMENDED.  Whichever
      party is active MUST initiate a DTLS handshake by sending a

      ClientHello over each flow (host/port quartet).

However I concur that the existing roles should be maintained, e.g. the
answerer must choose active or passive appropriately. Chrome will fail upon
an attempted role change.

On Mon, Nov 24, 2014 at 7:36 AM, Stefan Håkansson LK <
stefan.lk.hakansson@ericsson.com> wrote:

> Hi,
>
> I'm looking into the JSEP draft. One thing that seems strange is that in
> every offer the role offered is "actpass", also for existing
> connections. As I read section 7.3 of
> https://www.rfc-editor.org/rfc/rfc4145.txt the established roles should
> be maintained in such situations.
>
> What is the reason for the always offering "actpass" also for
> established roles/connections?
>
> Stefan
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>