- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Mon, 07 Oct 2019 22:45:59 +0000
- To: public-webrtc-logs@w3.org
@jan-ivar "Some of the questions here appear to be about ***when changes to exposed transport properties become observable***. I'd push back and ask those same questions wrt regular non-rollback negotiation methods, and look for answers there. If transports are under-specified, let's hope there's time to address that problem." [BA] This makes sense to me. Since we've worked through a number of issues relating to exposed transport properties, we should be able to figure out the implications for rollback. For example, Section 4.4.1.6 Step 8 "setting a local description" (sub-bullets 1.1.4 and 1.1.5) talks about setting the `transport` and `rtcpTransport` attributes representing `RTCDtlsTransport` objects, each with their underlying `RTCIceTransport`. -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2324#issuecomment-539236072 using your GitHub account
Received on Monday, 7 October 2019 22:46:00 UTC