Re: [rtcweb] Proposal for PeerConnection cloning

[Christer Holmberg <[e-mail]>]

Hi Richard,

Interesting proposal.

In bullet 11, you say that, if a final answer has been received (and unused resources released), resources would have to be reallocated once a clone is created.

A couple of questions:

1. Is there a need to allow cloning once a final answer has been received?

2. Once a final answer is received on a given PC, would it automatically remove all associated CPCs?

The basic question is really whether there is a need for clones once a final answer has been received. After all, there is a reason we call it "final" :)

Regards,

Christer

________________________________
From: [e-mail] [[e-mail]] On Behalf Of Ejzak, Richard P (Richard) [[e-mail]]
Sent: Sunday, May 06, 2012 9:54 PM
To: [e-mail]
Subject: [rtcweb] Proposal for PeerConnection cloning

Harald asked for a proposal for PeerConnection cloning, so here it goes:

I propose to create a new constructor “ClonePeerConnection” (CPC below) with the following semantics.


 1.  CPC will create a new PeerConnection object when successful.  The resulting PC behaves just like any other PC except as described below.
 2.  CPC will take as input a reference to an existing PeerConnection (PC) object (no configuration or IceCallback parameters).
 3.  CPC can clone any other PC (including a cloned PC).  The sequence of cloning is not important and parents have no particular status different from any generation of clone.
 4.  CPC will fail if either the local description of the parent PC is not set or the parent PC ICE is in ICE_CLOSED or ICE_GATHERING state.  The parent PC can be in the OPENING or ACTIVE state.
 5.  The CPC object will inherit the local streams, local ICE candidates, and local description of the PC.
 6.  The remote streams and remote description for the CPC object will be set to empty.
 7.  The CPC object will be set to the OPENING state to reflect that only the local description is set.
 8.  The ICE states other than CLOSED and GATHERING will be handled independently for each PC and its clones (as is true in standard forking scenarios).
 9.  The ICE state for this clone will be set to ICE_WAITING to reflect that all candidates are available but the remote configuration is not yet set.
 10. The PC and its clone(s) use a common pool of media resources.
 11. If the parent PC object has already released unused resources (final ANSWER), resources are reallocated as available to reflect the capabilities for each stream (as they would be reflected in a createOffer).
 12. The local streams might multicast toward the remote targets depending on the directionality attributes independently set for each PC and clone.
 13. The application should manage the directionality attributes for remote streams from different targets to avoid resource conflicts.

CPC will be used primarily if forking is anticipated or actually occurs.  It can also be used to clone a stable PC if desired for other reasons.  When used for SIP forking, creation of the clone can be delayed until an ANSWER actually arrives from a 2nd target as long as final ANSWER hasn’t been applied to the parent (PRANSWER is OK).  The parent always handles the first target; the first clone handles the 2nd target; etc.  The application can even try to clone for forking after the first ANSWER is applied to the parent and resources are released, as long as the local description has not changed, at the risk that some resources needed for the 2nd target are no longer available and must be renegotiated.

Comments on this proposal are welcome.

Richard