Re: [rtcweb] How to determine TLS roles?

[Eric Rescorla <[e-mail]>]

On Mon, Feb 10, 2014 at 12:54 PM, Christer Holmberg <
[e-mail]> wrote:

> Hi,
>
> >>This is defined in RFC 5763 S 5:
> >>http://tools.ietf.org/html/rfc5763#section-5
> >>
> >>Which points to:
> >>http://tools.ietf.org/html/rfc4145
> > Ok. So, a few questions to for clarification:
> >
> > Q1: This means that the JS App must set the setup attrbute value before
> passing an SDP to the browser?
> >
> > No. The browser does it.
> >
> >> Q2: If SDP O/A is not used on the wire, there needs to be another
> mechanism for the peers to negotiate/indicate who is "active" and who is
> "passive"?
> >
> > I don't see how this is our problem.
>
> Ok, let me rephrase: we use SDP O/A in the API between the JS App and the
> browser, and the RFCs you pointed to above say that the SDP setup attribute
> is used to negotiate the roles.
>
> So, can the JS App, using the setup attribute, control the DTLS role in
> the browser


That ties into the general question of which a-lines can be modified in
the JS app. It's no more decided than those questions.



> >> Q3: If you have mulitple m- lines, all using the same DTLS association,
> the setup attribute value must be identical in all m- lines?
> >
> > You mean because they are bundled? This should follow the same rules we
> generally use for things that are bundled.
>
> We haven't specified the rules for the setup attribute yet, but I assume
> it will have to be identical for each m- line within a BUNDLE group.
>

OK.


> And, in case the m- lines are NOT bundled, there will be separate DTLS
> associations, with separate roles, right?
>

Yes.

-Ekr



> Regards,
>
> Christer
>