Re: [rtcweb] JSEP-01 Handling Early Media, using SIP, clarifications

Anne Raby <anne.raby@ericsson.com> Wed, 04 July 2012 14:13 UTC

Return-Path: <anne.raby@ericsson.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 44A0C21F87FD for <rtcweb@ietfa.amsl.com>; Wed, 4 Jul 2012 07:13:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.218
X-Spam-Level:
X-Spam-Status: No, score=-6.218 tagged_above=-999 required=5 tests=[AWL=0.082, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 CqJmlhecMv1Y for <rtcweb@ietfa.amsl.com>; Wed, 4 Jul 2012 07:13:42 -0700 (PDT)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id BB87C21F85C3 for <rtcweb@ietf.org>; Wed, 4 Jul 2012 07:13:42 -0700 (PDT)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id q64EDkQQ030580; Wed, 4 Jul 2012 09:13:47 -0500
Received: from EUSAACMS0702.eamcs.ericsson.se ([169.254.1.236]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Wed, 4 Jul 2012 10:13:44 -0400
From: Anne Raby <anne.raby@ericsson.com>
To: "Olle E. Johansson" <oej@edvina.net>, Iñaki Baz Castillo <ibc@aliax.net>
Date: Wed, 04 Jul 2012 10:13:43 -0400
Thread-Topic: [rtcweb] JSEP-01 Handling Early Media, using SIP, clarifications
Thread-Index: Ac1Z4HwgWQfOJ5sVSimomndCX+7dEQABPxxw
Message-ID: <0434463FDA60A94FA978ACA44617682DFAA298D498@EUSAACMS0702.eamcs.ericsson.se>
References: <CABcZeBNFVqSS8p+NGmz=BKxhAg5Cf6rc51fTbTTx60jLh4hitg@mail.gmail.com> <BEBF190F-58F2-40E3-B2C5-463056D92CED@iii.ca> <D7437196-E5C9-43AB-8623-68CD283758FE@ericsson.com> <0434463FDA60A94FA978ACA44617682DFAA28B688B@EUSAACMS0702.eamcs.ericsson.se> <CALiegf=HwsC=dgH2Tu3Zn0869-2qbvkTh4MqzWqqRCqyT+7e_Q@mail.gmail.com> <DFDA9E24-7C24-4157-9864-6D4080F97147@edvina.net> <CALiegf=Mke9dKdwvGaBesRV2Nv4KNxFVuDPU0cxc18eDBCDnDQ@mail.gmail.com> <AAEB0AFC-2945-4D4F-94C6-2AF5598DBB72@edvina.net>
In-Reply-To: <AAEB0AFC-2945-4D4F-94C6-2AF5598DBB72@edvina.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] JSEP-01 Handling Early Media, using SIP, clarifications
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, 04 Jul 2012 14:13:43 -0000

Thank you both for the clarifications.

/Anne
-----Original Message-----
From: Olle E. Johansson [mailto:oej@edvina.net] 
Sent: July-04-12 8:28 AM
To: Iñaki Baz Castillo
Cc: Anne Raby; rtcweb@ietf.org
Subject: Re: [rtcweb] JSEP-01 Handling Early Media, using SIP, clarifications


4 jul 2012 kl. 13:22 skrev Iñaki Baz Castillo:

> 2012/7/4 Olle E. Johansson <oej@edvina.net>:
>> Do we really need to map the PSTN call states into webrtc?
> 
> I don't suggest that. I was just explaining the SIP case in which
> different SDP are received by the UAC within the same INVITE
> transaction :)

And you where perfectly right. An OFFER can only have one ANSWER - but per early dialog in SIP. And one INVITE with an SDP offer can generate multiple early dialogs with multiple SDP answers, in PRACK or in 200 OK or somewhere else. The OFFER/ANSWER process is decoupled from the INVITE transaction, really.

/O ;-)