Re: [rtcweb] JSEP: Relaxing SDP O/A rules?

Hi,

>We discussed earlier that PRANSWER states complicates SIP offer/answer
>mechanism as the mapping with SIP offer/answer is not well defined. For
>Example: "UPDATE with SDP from SIP UAS after sending 18x with SDP has to be
>considered as PRANSWER or OFFER or ANSWER in originating JSEP side" ?
>
>I agree with Roman that Cloning is the solution for serial forking as well.

If we support cloning (no matter whether it's a separate function call, or simply creating a new session with the same local descriptor), I agree that PRANSWER probably could be removed.

At least I have never thought of any other use of it than to support serial forking.

Regards,

Christer

-----Original Message-----
From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of
Christer Holmberg
Sent: Saturday, October 06, 2012 2:57 AM
To: Roman Shpount; Harald Alvestrand
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] JSEP: Relaxing SDP O/A rules?

Hi,

Roman is correct.

The SDP O/A doesn't consider forking, because each forked SIP leg creates a
unique early dialog, and each early dialog has its own O/A state machine.

Regards,

Christer

________________________________
From: Roman Shpount [roman@telurix.com]
Sent: Friday, October 05, 2012 8:46 PM
To: Harald Alvestrand
Cc: Christer Holmberg; rtcweb@ietf.org
Subject: Re: [rtcweb] JSEP: Relaxing SDP O/A rules?

On Fri, Oct 5, 2012 at 1:13 PM, Harald Alvestrand
<harald@alvestrand.no<mailto:harald@alvestrand.no>> wrote:
I've asked that question before, but I don't remember seeing an answer from
people who know what they're talking about:

Does serial forking, as practiced by SIP UAs, violate the SDP O/A model, or
does it not violate the SDP O/A model?

I don't understand how it, in the form that has been described as "what we
have to support", can be SDP O/A compatible, but then there are many things
about SIP that I don't understand, so I may understand it when it's
explained to me.

O/A does not describe multiple answers to a single offer. Nothing explicitly
prohibits it there but I would argue this is not part of this specification.
No standard document that I am aware of describes how serial O/A is supposed
to work. Serial forking as practiced by SIP UA does violate SIP RFC 3261
which states that each dialog can only have one answer to each offer. If
answer is sent in both provisional and final response, it should be the
same. You can, however, create multiple dialogs with the same offer. This
normally implies parallel forking, but the most common use case is with
early media, where you end up with multiple early dialogs. For instance you
call a phone number, phone network sends you SDP in early media and plays a
dial tone, then the called number does not answer, and you get connected to
a voice mail which uses a completely different SDP in final answer.
According to SIP these answers should come with different to-tags and
technically would be parts of
  two different dialogs. What makes this a bit tricky is when the phone
network and the voice mail are behind SBC (or some other sort of B2BUA) you
only see one dialog which send you multiple answers to the same offer. This
scenario is so common that it is more likely to be implemented then parallel
forking. This is why PRANSWER was suggested.

If cloning can be implemented in WebRTC it would be more standard compliant
then PRANSWER and would allow for a lot more use cases. Typical difficulty
in parallel forking implementation in SIP is due to RTP from multiple
sources coming to the same IP and port with no consent or notification to
the receiving side. This makes it very difficult to present this media to
the user. There is no way to tie media to actual dialogs since RTP can come
from different IP and ports then specified in answer SDPs. This is not an
issue with WebRTC where consent to receive media is required. I would argue
let's implement cloning and not waste any more time on PRANSWER which in my
opinion will always stay a half working hack.
_____________
Roman Shpount

_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb