Section 2: DTLS Transport Issues #100

Closed
aboba opened this Issue Jun 20, 2014 · 3 comments

Projects

None yet

1 participant

@aboba
Contributor
aboba commented Jun 20, 2014

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.

@aboba
Contributor
aboba commented Jun 20, 2014

Issues above are from Shijun Sun. Another one:

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

@aboba
Contributor
aboba commented Jun 20, 2014

Section 2.2 should say: "A RTCDtlsTransport instance is optionally constructed with an RTCIceTransport object."

change: readonly attribute RTCIceTransport transport;
to: readonly attribute RTCIceTransport? transport; //defaulted to null if constructor doesn't have it.

change: void addTransport (RTCIceTransport transport, int index = null);
to: void addTransport (RTCIceTransport transport, unsigned long? index = null);
change: void setTransport (RTCIceTransport transport);
to: void setTransport (RTCIceTransport? transport = null);

@aboba
Contributor
aboba commented Jun 27, 2014

If RTCDtlsTransport.setTransport is removed as was discussed at the June 24 ORTC CG meeting, then if RTCIceTransport is not provided within the constructor there would be no way to add it later. So it cannot be optional in the constructor. Also, the transport attribute cannot be nullable.

Should an invalid parameter to start() throw an InvalidParameter exception?

Other proposed changes seem reasonable.

@aboba aboba closed this Jun 28, 2014
@robin-raymond robin-raymond pushed a commit to robin-raymond/ortc that referenced this issue Jul 16, 2014
Robin Raymond Added section on WebRTC 1.0 compatibility issues, responding to Issue #…
…66

Added Identity support, as described in Issue #78
Reworked getStats method, as described in Issue #85
Removed ICE restart method described in Issue #93
Addressed CNAME and synchronization context issues described in Issue #94
Fixed WebIDL issues noted in Issue #97
Addressed NITs described in Issue #99
DTLS transport issues fixed as described in Issue #100
ICE transport issues fixed as described in Issue #101
ICE transport controller fixes made as described in Issue #102
Sender and Receiver object fixes made as described in Issue #103
Fixed RTCRtpEncodingParameter default issues described in Issue #104
Fixed 'Big Picture' issues descibed in Issue #105
Fixed RTCRtpParameter default issues described in Issue #106
Added a multi-stream capability, as noted in Issue #108
Removed quality scalability capabilities and parameters, as described in Issue #109
Added scalability examples as requested in Issue #110
Addressed WebRTC 1.0 Data Channel compatibility issue described in Issue #111
Removed header extensions from RTCRtpCodecParameters as described in Issue #113
Addressed RTP/RTCP non-mux issues with IdP as described in Issue #114
Added getParameter methods to RTCRtpSender and RTCRtpReceiver objects, as described in Issue #116
Added layering diagrams as requested in Issue #117
Added a typedef for payload type, as described in Issue #118
Moved onerror from the RTCIceTransport object to the RTCIceListener object as described in Issue #121
Added explanation of Voice Activity Detection (VAD), responding to Issue #129
Clarified the meaning of maxTemporalLayers and maxSpatialLayers, as noted in Issue #130
Added RFC 6051 to the list of header extensions and removed RFC 5450, as noted in Issue #131
Addressed ICE terminology issues, as described in Issue #132
Separated references into Normative and Informative, as noted in Issue #133
6f8216a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment