RTCDtlsTransport: Effect of calling start() after start()?

[aboba]

From Shijun Sun:
What is the behavior if calling RTCDtlsTransport.start(param_2) after a valid start(param_1) call?

I see two options:

1. start new session
2. throw exception

[pthatcherg]

Calling IceTransport.start does a restart. We could do the same for
DtlsTransport. However, I don't see a use case, and it would be more work
for the implementation. So, can we do #2 until we think of a use case?

On Thu, Aug 21, 2014 at 10:03 AM, aboba notifications@github.com wrote:

From Shijun Sun:
What is the behavior if calling RTCDtlsTransport.start(param_2) after a
valid start(param_1) call?

I see two options:

1. start new session
2. throw exception

—
Reply to this email directly or view it on GitHub
#146.

[aboba]

I also do not see a use case, so approach #2 (Exception) seems fine to me.

[aboba]

Proposed resolution is to add the following sentence to the definition of start in Section 2.3.2:

"If start() is called after a previous start() call, throw an InvalidState exception."

[martinthomson]

Or you could just be idempotent. If already started, report success.

[aboba]

The issue is with calling RTCDtlsTransport.start(newRemoteParameters).- a situation in which a new negotiation would be required (since the remote parameters have changed). For that case, returning without actually restarting negotiation with the requested remote parameters is probably not a good idea.