Re: [rtcweb] Forking & Early Media - Was Re: Minimal SDP negotiation mechanism

Saúl Ibarra Corretgé <saul@ag-projects.com> Wed, 21 September 2011 06:58 UTC

Return-Path: <saul@ag-projects.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 9B63421F8C61 for <rtcweb@ietfa.amsl.com>; Tue, 20 Sep 2011 23:58:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.71
X-Spam-Level:
X-Spam-Status: No, score=-1.71 tagged_above=-999 required=5 tests=[AWL=-0.022, BAYES_00=-2.599, HELO_MISMATCH_NET=0.611, MIME_8BIT_HEADER=0.3]
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 vy1l3CtUWT-c for <rtcweb@ietfa.amsl.com>; Tue, 20 Sep 2011 23:57:59 -0700 (PDT)
Received: from mail.sipthor.net (node06.dns-hosting.info [85.17.186.6]) by ietfa.amsl.com (Postfix) with ESMTP id B09F721F8C37 for <rtcweb@ietf.org>; Tue, 20 Sep 2011 23:57:58 -0700 (PDT)
Received: by mail.sipthor.net (Postfix, from userid 5001) id 49076B01B5; Wed, 21 Sep 2011 09:00:23 +0200 (CEST)
Received: from [192.168.99.36] (ip3e830637.speed.planet.nl [62.131.6.55]) by mail.sipthor.net (Postfix) with ESMTPSA id A894FB0057; Wed, 21 Sep 2011 09:00:10 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: =?iso-8859-1?Q?Sa=FAl_Ibarra_Corretg=E9?= <saul@ag-projects.com>
In-Reply-To: <2E239D6FCD033C4BAF15F386A979BF510F0E6B@sonusinmail02.sonusnet.com>
Date: Wed, 21 Sep 2011 09:00:09 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <8508ACC4-75A0-4556-8474-66175539F102@ag-projects.com>
References: <4E777500.5030201@alvestrand.no><69262135-CF5D-4E79-85CD-82DFDC4250C0@acmepacket.com><7F2072F1E0DE894DA4B517B93C6A05852233F6F222@ESESSCMS0356.eemea.ericsson.se><4E788458.1090108@alvestrand.no><7F2072F1E0DE894DA4B517B93C6A05852233F6F2A0@ESESSCMS0356.eemea.ericsson.se><4E788E5C.9090306@alvestrand.no><11209B22-4D96-4367-BC31-A4D586B55A83@edvina.net><27019ED4-BE01-474C-886E-D237DBD6CD2C@cisco.com><6916F9BA-3296-46DD-9F06-01E3928A8184@acmepacket.com><2E239D6FCD033C4BAF15F386A979BF510F0E5E@sonusinmail02.sonusnet.com> <CAD5OKxvq3DhAimZ4UeRBxTCbeQhqCP9+gkWJwsUa0Tb5CS5OdA@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF510F0E6B@sonusinmail02.sonusnet.com>
To: "Ravindran Parthasarathi" <pravindran@sonusnet.com>
X-Mailer: Apple Mail (2.1084)
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Forking & Early Media - Was Re: Minimal SDP negotiation mechanism
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, 21 Sep 2011 06:58:00 -0000

On Sep 21, 2011, at 8:25 AM, Ravindran Parthasarathi wrote:

> Hi Roman,
>  
> Thanks for the correction. I agree with you that there is no need to mention that forking is not support in RTCWeb. Your simple model works for browser as RTP End-point. One problem with the generic statement of multiple answer is that it may violate offer/answer model itself. For example: 18x and 200 having different answer for INVITE offer (standard implementation violation of offer/answer ;-))
>  

I think that the case discussed before was that you may receive several 18x responses because the request forked in the SIP side. So, if more than one of these 18x responses do have an SDP, do we create a PeerConnection for each? One for the first? The last?

--
Saúl Ibarra Corretgé
AG Projects