Re: [rtcweb] Agenda requests for Atlanta meeting

Roman Shpount <roman@telurix.com> Tue, 09 October 2012 01:24 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 D6D661F0420 for <rtcweb@ietfa.amsl.com>; Mon, 8 Oct 2012 18:24:12 -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=[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 pJ6vkkbyaUqH for <rtcweb@ietfa.amsl.com>; Mon, 8 Oct 2012 18:24:12 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8E74E21F87E3 for <rtcweb@ietf.org>; Mon, 8 Oct 2012 18:24:08 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id ro8so4621762pbb.31 for <rtcweb@ietf.org>; Mon, 08 Oct 2012 18:24:08 -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=xkpyf4l/OeXzDfDwjAx3uvq+aMGXRxVIcuAK+hnICcw=; b=ZN5ADD9XNQ1m4NUf9ZnDfnaPhlntFnDeMkU69qSUKAYEaR9WMVSeyYGAJ9maZQOpvu o6cSxpvvuBmieDYp6XV6DCACwJn8c4carAMWAHLDTV3esVoIUJq4bIljHZkI+3OFE+BA /aaou3DpJ72jlcuL2rY1g5KB0tn/1aUk7vlyLxTjQONfKHEFlQ97kDYFDdgGlRWyQCHp RAZeeDj/jHPMr/9842GJhCT1EtMzxV/dEqZqwxdfyY1JPDl2RBYn1Y+LOt80si+0Sy43 gHEg/593wwmbLJDqvTRv2aaaVVTZ7kfgi4IQKqtwggFyQWKoklLGm+Ys1H54dwXumFFW Y+lA==
Received: by 10.68.228.98 with SMTP id sh2mr58646524pbc.95.1349745848133; Mon, 08 Oct 2012 18:24:08 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by mx.google.com with ESMTPS id ih2sm11500125pbc.65.2012.10.08.18.24.06 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 08 Oct 2012 18:24:07 -0700 (PDT)
Received: by mail-pb0-f44.google.com with SMTP id ro8so4621742pbb.31 for <rtcweb@ietf.org>; Mon, 08 Oct 2012 18:24:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.189.70 with SMTP id gg6mr58965670pbc.125.1349745846162; Mon, 08 Oct 2012 18:24:06 -0700 (PDT)
Received: by 10.68.42.8 with HTTP; Mon, 8 Oct 2012 18:24:06 -0700 (PDT)
In-Reply-To: <C5E08FE080ACFD4DAE31E4BDBF944EB11187FB09@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>
Date: Mon, 8 Oct 2012 21:24:06 -0400
Message-ID: <CAD5OKxvxC8cLuwBbVMM+dmb8eZ=1=HYu6kprhi9QkLdRLz_4jw@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Content-Type: multipart/alternative; boundary=e89a8ff1c03eb2966904cb963184
X-Gm-Message-State: ALoCoQkzOIZdpuzbRnCMYFQLrONP39qJ3xtmM2nz3K7jrlCqLU4F92xO8N4lbCsTY4vylr/zXIYo
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:24:13 -0000

On Mon, Oct 8, 2012 at 8:42 PM, Cullen Jennings (fluffy)
<fluffy@cisco.com>wrote;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