This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Suggestion from Michael Tuexen: Replace maxRetransmitTime by maxLifeTime. Replace ... or set a time during which retransmissions are allowed (maxRetransmitTime). by ... or set a time during which transmissions and retransmissions are allowed (maxLifeTime). Replace maxRetransmitTime of type unsigned, readonly , nullable The RTCDataChannel.maxRetransmitTime attribute returns the length of the time window (in milliseconds) during which retransmissions may occur in unreliable mode, or null if unset. The attribute MUST be initialized to null by default and MUST return the value to which it was set when the RTCDataChannel was created. by maxLifeTime of type unsigned, readonly , nullable The RTCDataChannel.maxLifeTime attribute returns the length of the time window (in milliseconds) during which transmissions and retransmissions may occur in unreliable mode, or null if unset. The attribute MUST be initialized to null by default and MUST return the value to which it was set when the RTCDataChannel was created. Replace maxRetransmitTime of type unsigned short Limits the time during which the channel will retransmit data if not successfully delivered. This value may be clamped if it exceeds the maximum value supported by the user agent. by maxLifeTime of type unsigned short Limits the time during which the channel will transmit or retransmit data if not acknowledged. This value may be clamped if it exceeds the maximum value supported by the user agent.
Modification to previous suggestion: Use the name "maxPacketLifeTime" instead of "maxLifeTime".
Proposed fix: https://github.com/fluffy/webrtc-w3c/commit/049424f2b96485020256e2615d6469cd4067e5fd