IETF Logo Mail Archive

Re: [rtcweb] WebRTC endpoint non-browser

Gaelle Martin-Cocher <gmartincocher@blackberry.com> Mon, 08 December 2014 16:24 UTC

Return-Path: <gmartincocher@blackberry.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 461E11A9162 for <rtcweb@ietfa.amsl.com>; Mon, 8 Dec 2014 08:24:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dWgrx4IlKp30 for <rtcweb@ietfa.amsl.com>; Mon, 8 Dec 2014 08:24:10 -0800 (PST)
Received: from smtp-p02.blackberry.com (smtp-p02.blackberry.com [208.65.78.89]) by ietfa.amsl.com (Postfix) with ESMTP id 2363D1A9144 for <rtcweb@ietf.org>; Mon, 8 Dec 2014 08:24:10 -0800 (PST)
Received: from xct108cnc.rim.net ([10.65.161.208]) by mhs214cnc.rim.net with ESMTP/TLS/AES128-SHA; 08 Dec 2014 11:24:09 -0500
Received: from XMB111CNC.rim.net ([fe80::fcd6:cc6c:9e0b:25bc]) by XCT108CNC.rim.net ([fe80::8dc1:9551:6ed8:c618%17]) with mapi id 14.03.0210.002; Mon, 8 Dec 2014 11:24:08 -0500
From: Gaelle Martin-Cocher <gmartincocher@blackberry.com>
To: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] WebRTC endpoint non-browser
Thread-Index: AQHQEwGptNu+m+SBGkWau1ADvjUR4ZyF3/cw
Date: Mon, 08 Dec 2014 16:24:08 +0000
Message-ID: <92D0D52F3A63344CA478CF12DB0648AADF35B132@XMB111CNC.rim.net>
References: <92D0D52F3A63344CA478CF12DB0648AADF35B076@XMB111CNC.rim.net> <5485CD70.4010605@gmail.com>
In-Reply-To: <5485CD70.4010605@gmail.com>
Accept-Language: fr-FR, en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.65.160.249]
Content-Type: multipart/alternative; boundary="_000_92D0D52F3A63344CA478CF12DB0648AADF35B132XMB111CNCrimnet_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/Vp9hyBKDOsyMe9ja7Qxke2oF4HA
Subject: Re: [rtcweb] WebRTC endpoint non-browser
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 08 Dec 2014 16:24:16 -0000

You are listing webrtc-compatible endpoints, not webrtc "non browser" endpoints.
I am not asking of generic types of services but who actually belong to the non browser endpoint category.

Thanks
Gaëlle


From: rtcweb [mailto:rtcweb-bounces@ietf.org] On Behalf Of Sergio Garcia Murillo
Sent: Monday, December 08, 2014 11:10 AM
To: rtcweb@ietf.org
Subject: Re: [rtcweb] WebRTC endpoint non-browser

Native or custom applications, audio gateways, mcus, transcoders, SBCs...

Best regards
Sergio


On 08/12/2014 17:03, Gaelle Martin-Cocher wrote:
All,

Is it possible to know who is going to develop services that belongs to the WebRTC  endpoint non-browser category?
I think it would really help if we can identify that.
Thanks,

Gaëlle













_______________________________________________

rtcweb mailing list

rtcweb@ietf.org<mailto:rtcweb@ietf.org>

https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email