Re: [rtcweb] RTCWeb Forking usecase [was RE: draft-kaplan-rtcweb-sip-interworking-requirements-00]

[Hadriel Kaplan <[e-mail]>]

On Oct 28, 2011, at 6:01 PM, Randell Jesup wrote:

> As discussed, given that users will be "logged into" a service from multiple devices, and that we don't know what the application desired behavior will be, we need to support multiple ANSWER responses to a OFFER, and support allowing multiple of those answers to become active.  (For example, OFFER sent to "my Team", answered by 3 members of the team.)  As for implementation: probably by cloning the PeerConnection or a Factory (this has been discussed before and I haven't gone over the messages to see where it ended up).

Yes, but in theory we don't need to support ROAP forking to let you do that, because you don't need to do it that way.  For example you can write the JS to send a "session request" message without any ROAP/SDP, and as each "session response" comes back from each team member with a ROAP OFFER, the local JS creates a new PeerConnection and sends back to each team member a ROAP ANSWER from you.  So basically mimicking the offerless-INVITE model of SIP.

Or send a JS "session request" and get back a "session response" from each team member without any ROAP, then create each PeerConnection and send a new distinct "session request" with ROAP OFFER separately to each team member.  Kind of like a 3xx response model of SIP.

Or send a JS query to get back a list of URLs each representing a team member, and create a PeerConnection for each and send a ROAP OFFER to each URL.  Really like a 3xx response model of SIP.

-hadriel