Re: [rtcweb] Relaxing SDP O/A (was RE: Agenda requests for Atlanta meeting)

Bernard Aboba <bernard_aboba@hotmail.com> Fri, 19 October 2012 02:48 UTC

Return-Path: <bernard_aboba@hotmail.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 A628021F858C for <rtcweb@ietfa.amsl.com>; Thu, 18 Oct 2012 19:48:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.082
X-Spam-Level:
X-Spam-Status: No, score=-102.082 tagged_above=-999 required=5 tests=[AWL=0.517, BAYES_00=-2.599, 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 TAG-K8DFOfHH for <rtcweb@ietfa.amsl.com>; Thu, 18 Oct 2012 19:48:08 -0700 (PDT)
Received: from blu0-omc2-s25.blu0.hotmail.com (blu0-omc2-s25.blu0.hotmail.com [65.55.111.100]) by ietfa.amsl.com (Postfix) with ESMTP id 1508E21F8589 for <rtcweb@ietf.org>; Thu, 18 Oct 2012 19:48:08 -0700 (PDT)
Received: from BLU402-EAS240 ([65.55.111.72]) by blu0-omc2-s25.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 18 Oct 2012 19:48:07 -0700
X-Originating-IP: [24.16.96.166]
X-EIP: [EW7OMHT3WVYkyVRHHxvGd4P+jYRCB6jc]
X-Originating-Email: [bernard_aboba@hotmail.com]
Message-ID: <BLU402-EAS24040FFB01B9794ABEFD2BF93750@phx.gbl>
Date: Thu, 18 Oct 2012 19:48:03 -0700
From: Bernard Aboba <bernard_aboba@hotmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-OriginalArrivalTime: 19 Oct 2012 02:48:07.0321 (UTC) FILETIME=[2B1D8890:01CDADA4]
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Relaxing SDP O/A (was RE: 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: Fri, 19 Oct 2012 02:48:08 -0000

It seems to me that some scenarios would definitely require both APIs, for example if hold or key changes or codec additions are involved.

Martin Thomson <martin.thomson@gmail.com> wrote:

On 18 October 2012 14:55, Eric Rescorla <ekr@rtfm.com> wrote:
> I assume you mean in an update scenario, since in the initial offer
> scenario, you do pc.close();
>
> In the update scenario it seems to me that with the current
> API, the natural gesture is setRemoteDescription() with the previous
> answer. But obviously the world would be better if this were written
> down.

Or maybe setLocalDescription + setRemoteDescription with the entirety
of the previous session state.
_______________________________________________
rtcweb mailing list
rtcweb@ietf.org
https://www.ietf.org/mailman/listinfo/rtcweb