Re: [rtcweb] Basic scenario 'impossible?' to achieve with the actual API

Enrico Marocco <enrico.marocco@telecomitalia.it> Tue, 02 July 2013 16:14 UTC

Return-Path: <enrico.marocco@telecomitalia.it>
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 3552121F9246 for <rtcweb@ietfa.amsl.com>; Tue, 2 Jul 2013 09:14:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.119
X-Spam-Level:
X-Spam-Status: No, score=-101.119 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 Hs3xhzTqCiDP for <rtcweb@ietfa.amsl.com>; Tue, 2 Jul 2013 09:14:00 -0700 (PDT)
Received: from GRFEDG702RM001.telecomitalia.it (grfedg702rm001.telecomitalia.it [217.169.121.21]) by ietfa.amsl.com (Postfix) with ESMTP id EBBCD11E80D1 for <rtcweb@ietf.org>; Tue, 2 Jul 2013 09:13:52 -0700 (PDT)
Received: from grfhub702rm001.griffon.local (10.19.3.9) by GRFEDG702RM001.telecomitalia.it (10.173.88.21) with Microsoft SMTP Server (TLS) id 8.3.297.1; Tue, 2 Jul 2013 18:13:50 +0200
Received: from MacLab.local (163.162.180.246) by smtp.telecomitalia.it (10.19.9.235) with Microsoft SMTP Server (TLS) id 8.3.297.1; Tue, 2 Jul 2013 18:13:49 +0200
Message-ID: <51D2FC3C.8090609@telecomitalia.it>
Date: Tue, 02 Jul 2013 18:13:48 +0200
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <CABw3bnOp1jY6-ziR-PFG4-fRTT5zQ5ebQkmp5PhzeS1ew=h98g@mail.gmail.com>
In-Reply-To: <CABw3bnOp1jY6-ziR-PFG4-fRTT5zQ5ebQkmp5PhzeS1ew=h98g@mail.gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms050206070807070301050200"
X-TI-Disclaimer: Disclaimer1
Subject: Re: [rtcweb] Basic scenario 'impossible?' to achieve with the actual API
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, 02 Jul 2013 16:14:06 -0000

On 7/2/13 6:04 PM, José Luis Millán wrote:
> Hi,
> 
> Please, let me know how this normal use case could be solved with the
> current API.

Just off the top of my head:

Audio-only call establishment:

A --{"action":"CALL","sdp":"v=0..."}-> B
B --{"action":"ACCEPT CALL","sdp":"v=0..."}-> A

Rejected audio+video upgrade proposal:

A --{"action":"UPGRADE","sdp":"v=0..."}-> B
B --{"action":"REJECT UPGRADE"}-> A

Alice rolls back and removes local video display.

I may be missing something, but doesn't look like rocket science to me...

Enrico