New spec: Do we need the createProvisionalAnswer argument on createAnswer?

void createAnswer
<http://dev.w3.org/2011/webrtc/editor/webrtc.html#widl-PeerConnection-createAnswer-void-SessionDescription-offer-SessionDescriptionCallback-successCallback-PeerConnectionErrorCallback-failureCallback-MediaConstraints-constraints-Boolean-createProvisionalAnswer-false>
(SessionDescription
<http://dev.w3.org/2011/webrtc/editor/webrtc.html#idl-def-SessionDescription>
offer,

    SessionDescriptionCallback successCallback,     optional
PeerConnectionErrorCallback failureCallback,
    optional MediaConstraints constraints,
    optional Boolean createProvisionalAnswer=false);

This parameter feels very ad-hoc, and it's not clear to me that it
affects the generation of the offer at all (except, perhaps, to set
the .type property in the SessionDescription. As has been discussed,
the application may choose to apply an ANSWER as a PRANSWER, so this
concept shouldn't affect the SDP at all.

Therefore I would recommend that it be removed, and the application
can decide if a description should be applied as a PRANSWER or ANSWER
based on the type parameter to setLocal/setRemoteDescription, or by
mutating the SessionDescription.type field, if we choose to go that
route.