Re: [rtcweb] Use case change request: Identity in multiuser calls

Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com> Thu, 11 August 2011 11:36 UTC

Return-Path: <stefan.lk.hakansson@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 568B621F886A for <rtcweb@ietfa.amsl.com>; Thu, 11 Aug 2011 04:36:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.244
X-Spam-Level:
X-Spam-Status: No, score=-6.244 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 MeoemfpEBRqY for <rtcweb@ietfa.amsl.com>; Thu, 11 Aug 2011 04:36:51 -0700 (PDT)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 9D10B21F8783 for <rtcweb@ietf.org>; Thu, 11 Aug 2011 04:36:51 -0700 (PDT)
X-AuditID: c1b4fb39-b7bfdae000005125-88-4e43bef5904a
Received: from esessmw0247.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id 6B.3A.20773.5FEB34E4; Thu, 11 Aug 2011 13:37:25 +0200 (CEST)
Received: from ESESSCMS0362.eemea.ericsson.se ([169.254.1.110]) by esessmw0247.eemea.ericsson.se ([10.2.3.116]) with mapi; Thu, 11 Aug 2011 13:37:25 +0200
From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
To: Harald Alvestrand <harald@alvestrand.no>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Date: Thu, 11 Aug 2011 13:33:51 +0200
Thread-Topic: [rtcweb] Use case change request: Identity in multiuser calls
Thread-Index: AcxXaBa4rivuC1pITayFqQJ+e3bETQAsnS48
Message-ID: <BBF498F2D030E84AB1179E24D1AC41D616C389F1E1@ESESSCMS0362.eemea.ericsson.se>
References: <4E4292B2.8000904@alvestrand.no>
In-Reply-To: <4E4292B2.8000904@alvestrand.no>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: Re: [rtcweb] Use case change request: Identity in multiuser calls
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, 11 Aug 2011 11:36:52 -0000

Harald Alvestrand wrote:
>In draft-ietf-rtcweb-use-cases-and-requirements, I would like to extend
>one part of the scenario "4.3.3 Video conferencing system with central
>server".
>
>I would like to add one more paragraph:
>
>"All participant are authenticated by the central server, and authorized
>to connect to the central server. The participants are identified to
>each other by the central server, and the participants do not have
>access to each others' credentials such as e-mail addresses or login IDs".
I think this paragraph makes a lot of sense, and would be happy to add it. However, I’m not 100% convinced that it would add requirements that are in scope for webrtc or rtcweb.

When writing up this use case, the architecture in mind was centred around a web server that carries out the functionality of serving the web app, handling users, authenticating them, authorising them, allowing them to communicate and so on. That web server would control the central (media) server, which in turn is responsible only for establishing connections for RTC with browsers, mixing audio and selecting video between the users (browsers) selected by the web server, etc.

This would mean that user management, including determining what user identity is revealed to others, is controlled by the web server. I guess this is done already today for many services. What we will add is the possibility to communicate using audio and video without plug-ins.

Does this make sense or not?

Stefan