This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Created attachment 1472 [details] The attachment gives the updated state transition diagram for RTCPeerConnection. RTCPeerConnection's state transition diagram, specified in spec [1], is missing to indicate following state transitions state transitions. 1. have-remote-pranswer to have-local-offer 2. Have-local-pranswer to have-remtoe-offer The same is applicable for statemachine defined in section 3.2 of JSEP draft [2]. This state transitions are MUST to support section 5 of RFC 3262 [3] prack case. "If the UAC receives a reliable provisional response with an answer, it MAY generate an additional offer in the PRACK." Please find the attachment for the proposed state transition diagram, which includes these state. [1] http://dev.w3.org/2011/webrtc/editor/webrtc.html#state-definitions [2] http://tools.ietf.org/html/draft-ietf-rtcweb-jsep-06#page-7 [3] http://www.ietf.org/rfc/rfc3262.txt
WG agrees that such a transition should not be added. If an application needs to support PRACK, it needs to drive the state machine through multiple transitions in order to get from have-remote-pranswer to have-local-offer, and deal with the necessary consequences. The PeerConnection state machine is not a SIP state machine.