IETF Logo Mail Archive

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

Iñaki Baz Castillo <ibc@aliax.net> Thu, 10 May 2012 21:13 UTC

Return-Path: <ibc@aliax.net>
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 0ADFF21F8624 for <rtcweb@ietfa.amsl.com>; Thu, 10 May 2012 14:13:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.677
X-Spam-Level:
X-Spam-Status: No, score=-2.677 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 J1Psp9BnTPAC for <rtcweb@ietfa.amsl.com>; Thu, 10 May 2012 14:13:02 -0700 (PDT)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1E2AE11E80A5 for <rtcweb@ietf.org>; Thu, 10 May 2012 14:13:01 -0700 (PDT)
Received: by wgbdr13 with SMTP id dr13so1455446wgb.13 for <rtcweb@ietf.org>; Thu, 10 May 2012 14:13:01 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=42MdfdjJBisiNRtr+1eKpbmYIeuDsPcjir/8ac5JP04=; b=ePb58q7LVK9ZLTtqFx1zpUEGjgn8A2o18TEfKrxfMtK+Ag+uUd8VB0w4dfpNV10rbC Zz/lqTWfLHR4i3RV1iz6g6LMoyiuTWxzCEovlLQQx6t+rpyQ8+YOjhTfO6mbw7a7n5Kx OW3Wi4AeKYd0RdBBeHCKePKfr6m+Jf074cHTslBpuFkbA1vpdySzmDHizVJLQcUnWZPM uhACvGAzRlXwyppUThbdERpeUHxVt+eri6tISqUbjLEo0/2SavAslifX1to4lKcIK9lY PQ+J4AX9dTm/H7WHU6F8Ki2ccaHEZsv3WpBg4/aoDkTZbgOAZeRKfhU9EY3c27nOe6v1 SoyA==
Received: by 10.180.93.38 with SMTP id cr6mr1133296wib.16.1336684381287; Thu, 10 May 2012 14:13:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.0.237 with HTTP; Thu, 10 May 2012 14:12:41 -0700 (PDT)
In-Reply-To: <F6B988EE-8847-4AC6-806C-A9B96A075BDB@iii.ca>
References: <387F9047F55E8C42850AD6B3A7A03C6C0E23B102@inba-mail01.sonusnet.com> <6F428EFD2B8C2F49A2FB1317291A76C1136029362A@USNAVSXCHMBSA1.ndc.alcatel-lucent.com> <4FA13816.6050003@alvestrand.no> <CAD5OKxsOAeTRdCgj2g4BY8maeG1n9nzCv29g8kaFPVZ4tf8C5w@mail.gmail.com> <4FA15898.1040204@alvestrand.no> <7F2072F1E0DE894DA4B517B93C6A05852C44001329@ESESSCMS0356.eemea.ericsson.se> <CAD5OKxsbTSpMPg30P4DSN6UasCx6na43tpZ5yT2ct6SLMpd9xQ@mail.gmail.com> <7F2072F1E0DE894DA4B517B93C6A05852C4400132C@ESESSCMS0356.eemea.ericsson.se> <6F428EFD2B8C2F49A2FB1317291A76C1136047B753@USNAVSXCHMBSA1.ndc.alcatel-lucent.com> <7F2072F1E0DE894DA4B517B93C6A05852C4400132F@ESESSCMS0356.eemea.ericsson.se> <CAD5OKxuy8_Ras3X-8tcY1qaLRTVJ-z-JuXQaf0NKaRwN_dU18Q@mail.gmail.com> <7F2072F1E0DE894DA4B517B93C6A05852C442AC0DA@ESESSCMS0356.eemea.ericsson.se> <CAD5OKxuv7T6YrEXEeVECKbGtRg4feoRYTgvC57yqWXTBK43ypg@mail.gmail.com> <4FA2B447.7010504@jesup.org> <4FA2E264.4040207@jesup.org> <7F2072F1E0DE894DA4B517B93C6A05852C44001338@ESESSCMS0356.eemea.ericsson.se> <CAD5OKxuq14_DfSJuFEHq_ZEubbOYt7NFTcXWpLND8ggAr37QhA@mail.gmail.com> <7F2072F1E0DE894DA4B517B93C6A05852C44001339@ESESSCMS0356.eemea.ericsson.se> <CAD5OKxvFYy-9XAE5GG0n58xX2HKRX3o5qkTZ2o6rugakaM77Ew@mail.gmail.com> <7F2072F1E0DE894DA4B517B93C6A05852C4400133A@ESESSCMS0356.eemea.ericsson.se> <CAOJ7v-1Ue=q4MAh0csiDLvRFfMGaJ4vWrDxhir-S-OjSTsymaw@mail.gmail.com> <90DEBA9A-E8D2-4662-9A41-95B361FDAF05@iii.ca> <CAD5OKxvXstf7GOcZc7qdFB6GPvZyzBP8cv+JQcDK6rzbsmA6-Q@mail.gmail.com> <F6B988EE-8847-4AC6-806C-A9B96A075BDB@iii.ca>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Thu, 10 May 2012 23:12:41 +0200
Message-ID: <CALiegfkHemssLJPURBbQ88Fgsx_QF2_ma5xz5wAgoy5EQv8ZOw@mail.gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQmLwQaWhA4gOhreYqWu5jmA7aCv6UMNiG0bVVL1W7PgzBBJRj106vKvICP33jpRrQHLO19v
Cc: Randell Jesup <randell-ietf@jesup.org>, "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: Thu, 10 May 2012 21:13:04 -0000

2012/5/10 Cullen Jennings <fluffy@iii.ca>:
> The Nortel, Cisco, Avaya, Siemens etc enterprises PBX systems I have seen that support ringing multiple phones at the same time don't seem to do this way. They manage to hide the parallel forking with a B2BUA model and make it look like sequential forking.

Hi Cullen, I strongly prefer that WebRTC use cases are based on real
standards (i.e. pure SIP proxies) instead of non-standard devices
(like B2BUA's that are defined nowhere).

At least for me, the use case in which a "call" arrives to two
different devices and both generate direct (early-media) to the origin
is a mandatory use case for WebRTC, and I don't think that we should
discard this use case by design in any way.

Regards.

-- 
Iñaki Baz Castillo
<ibc@aliax.net>

v2.20.3 | Report a Bug | By Email