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

Roman Shpount <roman@telurix.com> Thu, 03 May 2012 19:09 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 76A9621F86AD for <rtcweb@ietfa.amsl.com>; Thu, 3 May 2012 12:09:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.859
X-Spam-Level:
X-Spam-Status: No, score=-2.859 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 B0Fn2c6pe3+z for <rtcweb@ietfa.amsl.com>; Thu, 3 May 2012 12:09:36 -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 970F921F85EF for <rtcweb@ietf.org>; Thu, 3 May 2012 12:09:36 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so2931071pbc.31 for <rtcweb@ietf.org>; Thu, 03 May 2012 12:09:36 -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=2yYq1RkwPdnWm6DdWARjHdWkDanu8rPU2d3YV/pOog4=; b=AZ7FKBpqJoYLar5L6z25nmdUtINewJqaBcamUghhZbnub4Ioz1GurAgCY0NzcBZbgF kbmcBvf6YQbdECAgNSl8C+KnVJX/nV5AeGX9rCZHqoK35Ye1baDq2oSENi0Giup4qbgG tRkZXlY2WH+C8F3iWS3MDq+2KsHlN2dbB2fAUmEDzcUfjUwOMPrYSkOCKr1/k5R3Wvqi nEH7vWndPeIbR7OLIBgPkdZzQOz6w4ERaAs2rTM1VLqSJcSmc6CWcT3a0p/non1+oRGP zqg2qzHTceBCxPl7weBu0YSSXS9qNyqb13z2iBayIQVHGrOSI338ePuJeQJudIBskScE fhBw==
Received: by 10.68.227.41 with SMTP id rx9mr10945329pbc.32.1336072176294; Thu, 03 May 2012 12:09:36 -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 wp3sm5301116pbc.38.2012.05.03.12.09.35 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 03 May 2012 12:09:35 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so2931025pbc.31 for <rtcweb@ietf.org>; Thu, 03 May 2012 12:09:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.238.197 with SMTP id vm5mr8342423pbc.132.1336072174646; Thu, 03 May 2012 12:09:34 -0700 (PDT)
Received: by 10.68.134.168 with HTTP; Thu, 3 May 2012 12:09:34 -0700 (PDT)
In-Reply-To: <7F2072F1E0DE894DA4B517B93C6A05852C44001337@ESESSCMS0356.eemea.ericsson.se>
References: <387F9047F55E8C42850AD6B3A7A03C6C0E23B102@inba-mail01.sonusnet.com> <CAOJ7v-3K=NK6zCLr-E-aSHDKVv2hMqnUhZKroX0YoBTo6-nQ+Q@mail.gmail.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> <7F2072F1E0DE894DA4B517B93C6A05852C44001337@ESESSCMS0356.eemea.ericsson.se>
Date: Thu, 3 May 2012 15:09:34 -0400
Message-ID: <CAD5OKxsitMcoesXhTrrbC58p8H=0bLfg+Ez0VPV-=+hqC8=1XQ@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=047d7b3392e95d344504bf268b0a
X-Gm-Message-State: ALoCoQlqdGUJO6MvoU4MiE7DqZCMYaO5WXrBTCH+Pywv27OaKBsYKFuFP7o38BewxK5VfAQeCFXr
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, 03 May 2012 19:09:37 -0000

On Thu, May 3, 2012 at 2:51 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Sure. But, that would also mean that you would have to clone the
> PeerConnection mid-session, if the remote entity changes.
>

What I meant was that you do not need ability to update remote destination
multiple times per single offer. You should still be able to initiate
another O/A exchange on the same peer connection and change the remote
party this way.
_____________
Roman Shpount