Re: [rtcweb] WebRTC endpoint non-browser

Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> Mon, 08 December 2014 19:47 UTC

Return-Path: <sergio.garcia.murillo@gmail.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 BF23A1A885D for <rtcweb@ietfa.amsl.com>; Mon, 8 Dec 2014 11:47:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 sncoNw9Pd7Mm for <rtcweb@ietfa.amsl.com>; Mon, 8 Dec 2014 11:47:20 -0800 (PST)
Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D1DB1A00F1 for <rtcweb@ietf.org>; Mon, 8 Dec 2014 11:47:20 -0800 (PST)
Received: by mail-wg0-f46.google.com with SMTP id x13so4571368wgg.33 for <rtcweb@ietf.org>; Mon, 08 Dec 2014 11:47:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=lP+GlYcHn+Z52muBDpu4c7F8RpXkserhb/p9IgOFGPE=; b=VUveUII+DLwL9moS4f8J91u+W63v/6pGR0Oq50VlI89TKkoqacZO4wEBYOe/vgfHG6 3bfd8gmt37Fvc5A28yelP5ajiADRAhJ26h17hIcPLkG66GI+gIrBS5Ahjq7RKQpaV8H2 XNe+GxvDi+iZMW9EHOTc2Kuz1zwajnqMDvyGJC18qf4pXKRPBIjTeOR+MJKDusol40pN iRmIf+5lTT7MuJ/1lL4TTXPnM7ISg6pDw3t/ZVPtBuSO21wQE+p1co0ZgGSY9jD7xOMZ m5UdE3F8qSPrPB2BJDOu93iwLSN0GcoCIltd5uA2+0+oFKmp/6VLVfyhLiiIWQFIZ5+o QtAw==
X-Received: by 10.194.92.176 with SMTP id cn16mr47051695wjb.62.1418068038956; Mon, 08 Dec 2014 11:47:18 -0800 (PST)
Received: from [192.168.0.194] ([95.61.111.78]) by mx.google.com with ESMTPSA id bs2sm40625120wjc.43.2014.12.08.11.47.17 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 08 Dec 2014 11:47:18 -0800 (PST)
Message-ID: <5486004C.3090007@gmail.com>
Date: Mon, 08 Dec 2014 20:47:24 +0100
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Gaelle Martin-Cocher <gmartincocher@blackberry.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>
References: <92D0D52F3A63344CA478CF12DB0648AADF35B076@XMB111CNC.rim.net> <5485CD70.4010605@gmail.com> <92D0D52F3A63344CA478CF12DB0648AADF35B132@XMB111CNC.rim.net>
In-Reply-To: <92D0D52F3A63344CA478CF12DB0648AADF35B132@XMB111CNC.rim.net>
Content-Type: multipart/alternative; boundary="------------000009060003050609030405"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/RQF3PNOZQRrYADAWfR7sMAwGcl4
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 19:47:22 -0000

They may be webrtc endpoints, or compatible-endpoints depending if they 
implement full webrtc-rtc stuff our just a minimum subset.

Being specific, any mobile application not using a browser will be a 
webrtc endpoint. So I bet every single webrtc service will implement 
their own app, hence their own webrtc endpoint.

Best regards
Sergio

On 08/12/2014 17:24, Gaelle Martin-Cocher wrote:
>
> 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
>