W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > October 2019

Re: [webrtc-pc] Section 4.4.1.6: Set the RTCSessionDescription (Object visibility) (#2338)

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Thu, 24 Oct 2019 16:01:31 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-545987008-1571932890-sysbot+gh@w3.org>
According to spec, the transport objects are created even at SLD(offer). If I understand correctly, in the case of bundling, you'd at least conceptually have transport objects for each m= section until you receive SRD(answer) to find out that bundling was indeed accepted, in which case you discard all but one transport to be used for all senders and receivers.

I don't know about the various webrtc-layer transport objects how offer/answer of transports is implemented, but Chrome [only exposes transports at SRD(answer)](https://codepen.io/henbos/pen/NWWjgXw?editors=1010), so I would think that transports are not fully created until answer?

Does it make sense to update the spec to only expose transport objects at the "answer" step? @steveanton
This would probably make "rollback" easier, since you wouldn't have to deal with rolling back transports. Though I don't know, maybe conceptually you would have to roll back some sort of JSEP layer transport anyway? I don't know.


-- 
GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2338#issuecomment-545987008 using your GitHub account
Received on Thursday, 24 October 2019 16:01:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:29 UTC