Re: [rtcweb] Agenda requests for Atlanta meeting

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Tue, 09 October 2012 01:26 UTC

Return-Path: <fluffy@cisco.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 7DD8C11E80DF for <rtcweb@ietfa.amsl.com>; Mon, 8 Oct 2012 18:26:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.485
X-Spam-Level:
X-Spam-Status: No, score=-110.485 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 o-9Np30xLamr for <rtcweb@ietfa.amsl.com>; Mon, 8 Oct 2012 18:26:51 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 9C07411E80F0 for <rtcweb@ietf.org>; Mon, 8 Oct 2012 18:26:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1657; q=dns/txt; s=iport; t=1349746011; x=1350955611; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=YaY36D7fs71kC0UundiABtwUlrUs1K7HuzI1Mw3mBXs=; b=O0p6bqPYT5TEpR9ZIcRQb3hzBiQK9Wfgxo97OizwPh5J/+sTjeWdaFTi R+LsauAnNOywR+zQuUUh44fSy0IRJhzdl0LvSmeT9fewxhL7anofHDxjN /UoY1vM6Qg5h3EzfIAVEcKrRMZcK+md6uiuw5CVOPe8uotCYL1Uy+u3Tt I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAIl8c1CtJXHB/2dsb2JhbABFvzKBCIIgAQEBAwESAWYQAgEIGAokMiUCBA4FCBqHXQaaYY9WkDKLR4UzYAOII5wNgWmCbYIX
X-IronPort-AV: E=Sophos;i="4.80,556,1344211200"; d="scan'208";a="129543553"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-2.cisco.com with ESMTP; 09 Oct 2012 01:26:51 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id q991QpEb010379 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 9 Oct 2012 01:26:51 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.217]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.02.0318.001; Mon, 8 Oct 2012 20:26:50 -0500
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Roman Shpount <roman@telurix.com>
Thread-Topic: [rtcweb] Agenda requests for Atlanta meeting
Thread-Index: AQHNpaetkG2ADNG+3EO5+NGGgdEEepewWX6AgAAC9ICAAAN2gIAAFs4AgAALWACAAAD2AA==
Date: Tue, 9 Oct 2012 01:26:50 +0000
Message-ID: <C5E08FE080ACFD4DAE31E4BDBF944EB11187FC44@xmb-aln-x02.cisco.com>
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>
In-Reply-To: <CAD5OKxvxC8cLuwBbVMM+dmb8eZ=1=HYu6kprhi9QkLdRLz_4jw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.86.152]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19252.004
x-tm-as-result: No--38.416600-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <550F2861923FC947B18371ABFB342B3B@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "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:26:52 -0000

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. 



On Oct 8, 2012, at 18:24 , Roman Shpount <roman@telurix.com>
 wrote:

> 
> 
> On Mon, Oct 8, 2012 at 8:42 PM, Cullen Jennings (fluffy) <fluffy@cisco.com> wrote:
> 
> Check out text from RFC 3311 that says
> 
>       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.
> 
> So the 183 would be need to be sent reliably at which case I would expect the gateways to map it to a final offer in RTCWeb not a provisional one. At that point when the update comes along with an offer, it just mapped to RTCweb offer.
> 
> 
> And what happens with the next 183 or 200 OK sent reliably in a different dialog? When we are dealing with serial forking we are dealing with different sequential dialogs created by the same offer, aren't we? Otherwise this is not really standard compliant. 
> _____________
> Roman Shpount
> 
>