IETF Logo Mail Archive

[rtcweb] WebRTC service between SPs

"Wangyahui (Yahui)" <yahui.wang@huawei.com> Fri, 28 June 2013 07:40 UTC

Return-Path: <yahui.wang@huawei.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 0701D21F9EA6 for <rtcweb@ietfa.amsl.com>; Fri, 28 Jun 2013 00:40:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.999
X-Spam-Level:
X-Spam-Status: No, score=-3.999 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, 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 ZWopcAFvxqcL for <rtcweb@ietfa.amsl.com>; Fri, 28 Jun 2013 00:39:56 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4C79D21F9E71 for <rtcweb@ietf.org>; Fri, 28 Jun 2013 00:39:56 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ASX92830; Fri, 28 Jun 2013 07:39:55 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 28 Jun 2013 08:38:54 +0100
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 28 Jun 2013 08:39:52 +0100
Received: from NKGEML507-MBX.china.huawei.com ([169.254.5.117]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.01.0323.007; Fri, 28 Jun 2013 15:39:44 +0800
From: "Wangyahui (Yahui)" <yahui.wang@huawei.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: WebRTC service between SPs
Thread-Index: Ac5z0qWy9y8UDykmSVWknFkwecyvnw==
Date: Fri, 28 Jun 2013 07:39:43 +0000
Message-ID: <034C870DB898BE43B5787C7A79107CD94BFA4E1B@nkgeml507-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.63.61]
Content-Type: multipart/alternative; boundary="_000_034C870DB898BE43B5787C7A79107CD94BFA4E1Bnkgeml507mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mailman-Approved-At: Fri, 28 Jun 2013 08:49:02 -0700
Subject: [rtcweb] WebRTC service between SPs
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, 28 Jun 2013 07:45:03 -0000

Hi all,
I have followed RTCWeb discussion for some time.
As far as I know, any website can conveniently integrate WebRTC service, particularly social networking websites. It can easily be predicted that many service providers (SPs), especially social networking SPs will release their WebRTC services in the near future. But I am wondering how the users under different SPs can communicate using WebRTC client. Each SP offers different user identity in different domain. Although some mechanisms can support to login multiple websites using a uniform account, such as Persona ID, OpenID or OAuth, they have different Idps, and not all websites apply the same mechanism.
I am not sure whether it is a problem. Thanks for your any comments.

v2.23.0 | Report a Bug | By Email