Re: [rtcweb] Agenda requests for Atlanta meeting

Roman Shpount <roman@telurix.com> Tue, 09 October 2012 01:56 UTC

Return-Path: <roman@telurix.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 877771F041F for <rtcweb@ietfa.amsl.com>; Mon, 8 Oct 2012 18:56:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level:
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id koF18A2C5QTu for <rtcweb@ietfa.amsl.com>; Mon, 8 Oct 2012 18:56:29 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 824641F0417 for <rtcweb@ietf.org>; Mon, 8 Oct 2012 18:56:29 -0700 (PDT)
Received: by mail-vc0-f172.google.com with SMTP id fl11so6157311vcb.31 for <rtcweb@ietf.org>; Mon, 08 Oct 2012 18:56:29 -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:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=+Irm/tNDLXNKc3LzxiTxzUWLDl5FW9pBph6fBtYLoBo=; b=n88Oo8EsMGd/7OTlrAFsgjOzMuTooiPXMTJj+j2jmev4vCSrFh5fjB5jfwkI1IH2sh VgUZ43WUVvuNmea1Ft6ZQKiHFuRRMaKRPecThaxHxsbBwlXzn5hNUcKQUrMQ3qeCGKF9 LlLJSFc6j2f2pDKsv8ZSlHju+oZl93rG0P8AYKTUoD2ekMNqapojQYoKyJijLV6ari1S u0mWq5rKRL5J8QqRAHiF06K7nEfusnyDMblyz5Erk7BfupLgwGBswjlpt5uCT9hsQJcQ ozUGaaZuSgBxph3N0VXcdCJzNFuTUspjWVmJXMMLYkDcyVERc8wXJtbORWrxZlWObk9v figQ==
Received: by 10.220.208.210 with SMTP id gd18mr10764049vcb.43.1349747788986; Mon, 08 Oct 2012 18:56:28 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by mx.google.com with ESMTPS id b3sm1466874vec.11.2012.10.08.18.56.28 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 08 Oct 2012 18:56:28 -0700 (PDT)
Received: by mail-vc0-f172.google.com with SMTP id fl11so6157283vcb.31 for <rtcweb@ietf.org>; Mon, 08 Oct 2012 18:56:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.230.133 with SMTP id jm5mr10915592vcb.4.1349747787692; Mon, 08 Oct 2012 18:56:27 -0700 (PDT)
Received: by 10.58.240.84 with HTTP; Mon, 8 Oct 2012 18:56:27 -0700 (PDT)
In-Reply-To: <98BB750F-F263-44BB-9CC3-1F0816C11061@iii.ca>
References: <506B0367.4000103@ericsson.com> <C5E08FE080ACFD4DAE31E4BDBF944EB111867718@xmb-aln-x02.cisco.com> <7F2072F1E0DE894DA4B517B93C6A0585340BAD03A6@ESESSCMS0356.eemea.ericsson.se> <C5E08FE080ACFD4DAE31E4BDBF944EB11187F8FB@xmb-aln-x02.cisco.com> <CAD5OKxtDnXafE=3R-7X9vL1TaYMauYL56JFfyJoTztDMbe4DqQ@mail.gmail.com> <723C9B03-B45B-4214-9A36-7B4CEBD2FC2E@iii.ca> <CAD5OKxsEmgUJXUYaFRnkDZhoZdzZaD4rCvoUFPNVdd6L1FWDjQ@mail.gmail.com> <C5E08FE080ACFD4DAE31E4BDBF944EB11187FB09@xmb-aln-x02.cisco.com> <CAD5OKxvxC8cLuwBbVMM+dmb8eZ=1=HYu6kprhi9QkLdRLz_4jw@mail.gmail.com> <C5E08FE080ACFD4DAE31E4BDBF944EB11187FC44@xmb-aln-x02.cisco.com> <CAD5OKxsF4bSvi5SQ9OU1mcqGYeEHUMiYsLaRo_sKoMs8-_7m0A@mail.gmail.com> <98BB750F-F263-44BB-9CC3-1F0816C11061@iii.ca>
Date: Mon, 8 Oct 2012 21:56:27 -0400
Message-ID: <CAD5OKxvLQYXwGD8TtgoBus_fpvek96JYpx80zgFT1EuWz7AoEw@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Cullen Jennings <fluffy@iii.ca>
Content-Type: multipart/alternative; boundary=14dae9cdc6c16bfa2e04cb96a5b4
X-Gm-Message-State: ALoCoQmfjxrCwRhZL2nf7c9JBlTC+A9LtlmQa20xYSBtzO5heS+Y2GI8nWEs6vMfaHom/6FtGTJ0
Cc: "Cullen Jennings \(fluffy\)" <fluffy@cisco.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Agenda requests for Atlanta meeting
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: Tue, 09 Oct 2012 01:56:30 -0000

On Mon, Oct 8, 2012 at 9:41 PM, Cullen Jennings <fluffy@iii.ca> wrote:

>
> On Oct 8, 2012, at 18:31 , Roman Shpount <roman@telurix.com> wrote:
>
> > On Mon, Oct 8, 2012 at 9:26 PM, Cullen Jennings (fluffy) <
> fluffy@cisco.com> wrote:
> >
> > Well, what's the end user experience you're trying to achieve  - lets
> say we are talking about audio. Do you want to play the first one or the
> last one? If you want to bridge them into a party line, this is probably
> not how you want the SIP side to happen.
> >
> >
> > This is still serial forking. Imagine the following scenario: You are
> calling a phone number, you dial first provider who starts playing a dial
> tone then uses an UPDATE to connect you to a media server to play an
> announcement after which your call goes to voice mail (another dialog and
> another SDP). This is all fairly legal and not unusual for SIP scenarios.
> Nothing to do with party lines.
>
> Ok, serial forking with early media seems like it should work. Seems like
> the browser would make the offer, that gateway turned into SIP invite that
> then went to sequential forking proxy that send sent the invite to UA A. UA
> A returns a 180 that gets mapped to PRANSWER, the proxy then forks to UA B
> that sends a 200 on a different dialog that gets mapped to answer.


 The only issue is the there is currently no way to map an UPDATE received
in the early dialog to WebRTC API calls. I am probably OK with it not being
handled until the cloning is implemented, but this shows that PRANSWER is
not very useful even for the serial forking.
_____________
Roman Shpount