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

José Luis Millán <jmillan@aliax.net> Tue, 02 July 2013 16:04 UTC

Return-Path: <jmillan@aliax.net>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 4D61021F9371 for <rtcweb@ietfa.amsl.com>; Tue, 2 Jul 2013 09:04:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.076
X-Spam-Status: No, score=-2.076 tagged_above=-999 required=5 tests=[AWL=-0.600, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, J_CHICKENPOX_18=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id EMlL37CwyKwM for <rtcweb@ietfa.amsl.com>; Tue, 2 Jul 2013 09:04:02 -0700 (PDT)
Received: from mail-vb0-f48.google.com (mail-vb0-f48.google.com []) by ietfa.amsl.com (Postfix) with ESMTP id F007521F9F7C for <rtcweb@ietf.org>; Tue, 2 Jul 2013 09:04:01 -0700 (PDT)
Received: by mail-vb0-f48.google.com with SMTP id w15so4704149vbf.21 for <rtcweb@ietf.org>; Tue, 02 Jul 2013 09:04:00 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :x-gm-message-state; bh=Qw4JOEPDZEjLD1tXZjrSPW3LoiU9FX46WwqDu7kujOA=; b=V+BAxOyXIOMilz4CICubhR+m1FUzchDrso15oD92DlzOVk9hkc8ygiLbg7T4bnJjh5 iZzqyr9/CcY5Ttb+AJ302ob9N5owfT/MN/V2oMPmQzML1qzSkw8ft0yT0H6mOuzUxHFH fxlOYLUStycupVURNnt/QHRLJjMw1zq7VN7cHdoVWqz8r1TvdePLfpWnA2v3TioMLCsn BCIs+4vUaMjdOggScuozSodNNrMpGrewGKCNfsYlKLkClmWsBRvk/elz/doIPcVH7Vag 3t7ioU5OPzNtZZ4iHTjLvXh3hkJQonex2dOUeLXCFPrDKQFRtV2tAKztsKS/lsFQ4FvT JMlA==
MIME-Version: 1.0
X-Received: by with SMTP id 9mr11463601vcv.58.1372781040190; Tue, 02 Jul 2013 09:04:00 -0700 (PDT)
Received: by with HTTP; Tue, 2 Jul 2013 09:04:00 -0700 (PDT)
Date: Tue, 2 Jul 2013 18:04:00 +0200
Message-ID: <CABw3bnOp1jY6-ziR-PFG4-fRTT5zQ5ebQkmp5PhzeS1ew=h98g@mail.gmail.com>
From: =?UTF-8?B?Sm9zw6kgTHVpcyBNaWxsw6Fu?= <jmillan@aliax.net>
To: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c3e45241576e04e0897e0b
X-Gm-Message-State: ALoCoQkgQLrTpWQBOVuADu8zn3mtM9ZpaNs8rr3B7RLoI9ZXqgrw3H5SLwXhNjjfNsJNW1+UYUeX
Subject: [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:04:07 -0000


Please, let me know how this normal use case could be solved with the
current API.

Alice and Bob have accessed to a Web page offering a basic WebRTC
application   that they use to speak and see each other. They are in the
middle of a media session right now.

Alice presses the "Video" button in her web application. A SDP offer with
video description is sent to Bob:

Bob doesn't want to see her, so his web application rejects the media by
using any valid method for that:
-- a=inactive
-- m=video 0

Alice web application received a SDP answer which was consumed successfully
by the RTCPeerConnection. Alice thinks she is sharing her video, but she is

The application "Video" button is disabled since the video is already being
shared (theoretically)

The application "self-Video" HTML5 video element displays Alice's face. She
thinks that Bob is seeing her face too, but he did indeed rejected so.

I hope this common scenario can be achieved somehow with the current API. I
can't find how to do it though.

Thanks in advance

José Luis Millán