Issue 100: Section 2: DTLS Transport Issues

• From: Bernard Aboba <Bernard.Aboba@microsoft.com>
• Date: Wed, 25 Jun 2014 22:23:21 +0000
• To: "public-ortc@w3.org" <public-ortc@w3.org>
• Message-ID: <d57d3449c09843109bb1426604d45a55@SN2PR03MB031.namprd03.prod.outlook.com>

Github link: https://github.com/openpeer/ortc/issues/100

>From Shijun Sun: 

Section 2.2. Constructor of DtlsTransport. When a DtlsTransport is automatically constructed, the UA cannot create an internal IceTransport without a given IceOptions. So, we need RTCIceTransport on the Constructor. The RTCIceTransport should not be ‘optional’ on the constructor.

Section 2.3. DtlsTransport. When DtlsTransport is closed, calling start() will start a new session (with new key negotiations, etc.). This should be specified in the spec – for the start() method.

Section 2.3. DtlsTransport. When “error” should be fired? What we’d like to propose: If the transport is closed without either party calling stop(), the UA should fire an error event.

When invalid remote-params as input to DtlsTransport.start(), UA should throw an “Invalid Access Exception”.

Received on Wednesday, 25 June 2014 22:23:51 UTC