Re: [rtcweb] SDP_PRANSWER followed by SDP_OFFER scenario in JSEP

"Ravindran, Parthasarathi" <pravindran@sonusnet.com> Wed, 02 May 2012 13:01 UTC

Return-Path: <pravindran@sonusnet.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 356F621F847C for <rtcweb@ietfa.amsl.com>; Wed, 2 May 2012 06:01:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.516
X-Spam-Level:
X-Spam-Status: No, score=-6.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tng1lxmRW8b2 for <rtcweb@ietfa.amsl.com>; Wed, 2 May 2012 06:01:47 -0700 (PDT)
Received: from na3sys010aog112.obsmtp.com (na3sys010aog112.obsmtp.com [74.125.245.92]) by ietfa.amsl.com (Postfix) with ESMTP id 4A03821F8491 for <rtcweb@ietf.org>; Wed, 2 May 2012 06:01:47 -0700 (PDT)
Received: from USMA-EX-HUB2.sonusnet.com ([69.147.176.212]) (using TLSv1) by na3sys010aob112.postini.com ([74.125.244.12]) with SMTP ID DSNKT6EwOlfiEaDWBkUhHsFDgPJt725KHFEy@postini.com; Wed, 02 May 2012 06:01:47 PDT
Received: from INBA-HUB01.sonusnet.com (10.70.51.86) by USMA-EX-HUB2.sonusnet.com (66.203.90.17) with Microsoft SMTP Server (TLS) id 14.2.247.3; Wed, 2 May 2012 09:01:52 -0400
Received: from INBA-MAIL02.sonusnet.com ([fe80::f8d4:7090:f632:bbbc]) by inba-hub01.sonusnet.com ([fe80::5cbc:2823:f6cc:9ce7%11]) with mapi id 14.01.0355.002; Wed, 2 May 2012 18:31:41 +0530
From: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
To: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, Justin Uberti <juberti@google.com>, Cullen Jennings <fluffy@iii.ca>
Thread-Topic: [rtcweb] SDP_PRANSWER followed by SDP_OFFER scenario in JSEP
Thread-Index: Ac0mnx+EQrlVrvWDRey+KwUxgcHWewAThDfgAF2QivA=
Date: Wed, 2 May 2012 13:01:41 +0000
Message-ID: <387F9047F55E8C42850AD6B3A7A03C6C148945AF@inba-mail02.sonusnet.com>
References: <387F9047F55E8C42850AD6B3A7A03C6C0E23B102@inba-mail01.sonusnet.com> <E1CBF4C7095A3D4CAAAEAD09FBB8E08C06EED670@xmb-sjc-234.amer.cisco.com>
In-Reply-To: <E1CBF4C7095A3D4CAAAEAD09FBB8E08C06EED670@xmb-sjc-234.amer.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.70.54.41]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] SDP_PRANSWER followed by SDP_OFFER scenario in JSEP
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2012 13:01:48 -0000

Hi Charles,

UPDATE is allowed in the early dialog and I haven't shown in the callflow for simplicity as I mentioned in PS of below mail as " PS: For simplicity, PRACK message exchange is not chosen in SIP side."

Thanks
Partha

>-----Original Message-----
>From: Charles Eckel (eckelcu) [mailto:eckelcu@cisco.com]
>Sent: Monday, April 30, 2012 9:53 PM
>To: Ravindran, Parthasarathi; Justin Uberti; Cullen Jennings
>Cc: rtcweb@ietf.org
>Subject: RE: [rtcweb] SDP_PRANSWER followed by SDP_OFFER scenario in
>JSEP
>
>Hi Partha,
>
>I believe such a flow illegal, per RFC 3311:
>
>      o  If the UPDATE is being sent before the completion of the INVITE
>         transaction, and the initial INVITE contained an offer, the
>         UPDATE cannot be sent with an offer unless the callee has
>         generated an answer in a reliable provisional response, has
>         received a PRACK for that reliable provisional response, has
>         not received any requests (PRACK or UPDATE) with offers that it
>         has not answered, and has not sent any UPDATE requests
>         containing offers that have not been answered.
>
>Cheers,
>Charles
>
>> -----Original Message-----
>> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
>> Behalf Of Ravindran, Parthasarathi
>> Sent: Monday, April 30, 2012 12:02 AM
>> To: Justin Uberti; Cullen Jennings
>> Cc: rtcweb@ietf.org
>> Subject: [rtcweb] SDP_PRANSWER followed by SDP_OFFER scenario in JSEP
>>
>> Justin/Cullen,
>>
>> Could you please explain in case for an SDP_OFFER(1), the remote
>entity
>> replies with SDP_PRANSWER followed by new SDP_OFFER (2) what is the
>> expected behavior. The exact callflow is as follows:
>>
>>
>> Browser1-------------------------Browser2(SIP-JSEP gateway)
>>     |        SDP_OFFER(1)            |  INV with offer1
>>     |------------------------------->|--->
>>     |       SDP_PRANSWER(1)          |  183 with answer1
>>     |<-------------------------------|<---
>>     |       SDP_OFFER(2)             |   UPDATE with offer2
>>     |<-------------------------------|<---
>>     |       SDP_ANSWER(2?)           |
>>     |--------------------->?
>>
>> The reason for this O/A callflow is due to UPDATE method (RFC 3311)
>> mapping in Browser 2 (SIP-JSEP gateway).
>>
>> Thanks
>> Partha
>>
>> PS: For simplicity, PRACK message exchange is not chosen in SIP side.
>>
>>
>>
>>
>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb