IETF Logo Mail Archive

Re: [rtcweb] Agenda requests for Atlanta meeting

Christer Holmberg <christer.holmberg@ericsson.com> Tue, 09 October 2012 19:04 UTC

Return-Path: <christer.holmberg@ericsson.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 AA1D411E8156 for <rtcweb@ietfa.amsl.com>; Tue, 9 Oct 2012 12:04:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.83
X-Spam-Level:
X-Spam-Status: No, score=-5.83 tagged_above=-999 required=5 tests=[AWL=-0.181, BAYES_00=-2.599, HELO_EQ_SE=0.35, J_CHICKENPOX_53=0.6, RCVD_IN_DNSWL_MED=-4]
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 LimsbZeYIa-h for <rtcweb@ietfa.amsl.com>; Tue, 9 Oct 2012 12:04:14 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id B6FC911E8153 for <rtcweb@ietf.org>; Tue, 9 Oct 2012 12:04:13 -0700 (PDT)
X-AuditID: c1b4fb25-b7f046d00000644c-7e-5074752c6294
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 01.7F.25676.C2574705; Tue, 9 Oct 2012 21:04:12 +0200 (CEST)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.243]) by esessmw0184.eemea.ericsson.se ([10.2.3.53]) with mapi; Tue, 9 Oct 2012 21:04:12 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>, "Cullen Jennings (fluffy)" <fluffy@cisco.com>
Date: Tue, 09 Oct 2012 21:04:11 +0200
Thread-Topic: [rtcweb] Agenda requests for Atlanta meeting
Thread-Index: Ac2mOIZh+PFfSQJ9S52mI6WiFBgRBAAFw7qT
Message-ID: <7F2072F1E0DE894DA4B517B93C6A0585340BAFAA6B@ESESSCMS0356.eemea.ericsson.se>
References: <506B0367.4000103@ericsson.com> <C5E08FE080ACFD4DAE31E4BDBF944EB111867718@xmb-aln-x02.cisco.com> <7F2072F1E0DE894DA4B517B93C6A0585340BAD03A6@ESESSCMS0356.eemea.ericsson.se> <C5E08FE080ACFD4DAE31E4BDBF944EB11187F8F1@xmb-aln-x02.cisco.com> <7F2072F1E0DE894DA4B517B93C6A0585340BAD087E@ESESSCMS0356.eemea.ericsson.se> <C5E08FE080ACFD4DAE31E4BDBF944EB1118810C3@xmb-aln-x02.cisco.com>, <CABkgnnV8YbbPi3pZt9mBjBfSgkx4EgL=EY0YogpeRobUMQ506w@mail.gmail.com>
In-Reply-To: <CABkgnnV8YbbPi3pZt9mBjBfSgkx4EgL=EY0YogpeRobUMQ506w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrILMWRmVeSWpSXmKPExsUyM+Jvra5OaUmAwblnihYdk9ksrp35x2ix 9l87uwOzx5TfG1k9ds66y+6xZMlPpgDmKC6blNSczLLUIn27BK6MJa/mshR0sldsn3CXtYHx BGsXIyeHhICJxM3zHxkhbDGJC/fWs3UxcnEICZxilNh4+gMjhDOHUWLls8lADgcHm4CFRPc/ bRBTRCBO4u43V5BeZgF1iTuLz7GD2CwCKhLnt64Amy8sYCmxaPN+NhBbRMBKYs2t68wQtpHE sZk3wOp5BcIljv5+xgyx6iqzxKG+yWBFnAKBEgdvTwErYgQ67vupNUwQy8Qlbj2ZzwRxtIDE kj3nmSFsUYmXj/+xQtSLStxpX88IUa8jsWD3JzYIW1ti2cLXzBCLBSVOznzCMoFRbBaSsbOQ tMxC0jILScsCRpZVjMK5iZk56eVGeqlFmcnFxfl5esWpmxiB0XRwy2/VHYx3zokcYpTmYFES 57XeusdfSCA9sSQ1OzW1ILUovqg0J7X4ECMTB6dUA2ObuNPWo8femC55E6j+y+Xgg9oc/gKt TJ/rkbkTJ0wtehHvPH3JkelfNfctCFDQ/Co+lZvFcNaUzzxFOb4LQ16kfHooFvhC25BLzEj6 uiXz/Vmu/LceFH9dumpTvNZdo8LTkslvbs6UYt/iyrfkaVbVDuUisaUsAlJTihuskpg0TeJa LZdPWKnEUpyRaKjFXFScCADzZOqKdAIAAA==
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 19:04:14 -0000

Hi,

>> I have not seen any reason to relax 3264 yet but if something comes up, agree we should carefully look at the cases. I think we can just do straight up 3264.
>
>RFC 3264 doesn't describe PRANSWER.  The concept is entirely absent.
>
>   The offerer MAY immediately cease listening for media formats that
>   were listed in the initial offer, but not present in the answer.
>
> "the" answer.

I agree with Martin. 3264 O/A is always per dialog, and forking is supported by generating multiple dialogs. JSEP, OTOH, in order to support forking with a single "dialog" (peerConnection local descriptor), now defines O/A as offer+any number of pranswers + answer.

So, we would e.g. have to define what happens if a new offer is received from the remote side while the browser is in pranswer-received state (see my call flow in another reply).

Regards,

Christer

v2.23.0 | Report a Bug | By Email