W3C home > Mailing lists > Public > public-webrtc@w3.org > February 2012

JSEP-01: SDP_PRANSWER and FEDEX use-case

From: Christer Holmberg <christer.holmberg@ericsson.com>
Date: Wed, 15 Feb 2012 11:47:42 +0100
To: "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <7F2072F1E0DE894DA4B517B93C6A05852C3D87E060@ESESSCMS0356.eemea.ericsson.se>


Section 6.1.4 of jsep-01 says:

        "SDP_PRANSWER indicates that a description should be parsed as an
        answer, but not a final answer, and so should not result in the
        starting of media transmission. A description used as a SDP_PRANSWER
        may be applied as a response to a SDP_OFFER, or an update to a
        previously sent SDP_PRANSWER."

Section 7.6 shows a SIP early media (FEDEX) use-case, where an SDP answer received in a SIP 18x response is provided to the browser as a SDP_PRANSWER.

Q1: Since SDP_PRANSWER is not supposed to start media transmission, how will the use-case work? As far as I know, media transmission is needed for the FEDEX use-case.

Q2: The draft doesn't really specify what SDP_PRANSWER is used for. I understand that it means that a "final" answer may be provided later, but it doesn't really say what the a browser would do with an SDP_PRANSWER - especially since it doesn't seem to enable media.

Q3: Assuming we would allow multiple SDP_ANSWER (see separate thread), is there a need for SDP_PRANSWER?


Received on Wednesday, 15 February 2012 10:48:08 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:27 UTC