Re: [rtcweb] WebRTC endpoint non-browser

Dave Taht <dave.taht@gmail.com> Mon, 08 December 2014 19:53 UTC

Return-Path: <dave.taht@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 D0C0A1A0137 for <rtcweb@ietfa.amsl.com>; Mon, 8 Dec 2014 11:53:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level:
X-Spam-Status: No, score=-1 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, FREEMAIL_REPLY=1, SPF_PASS=-0.001] autolearn=no
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 pvw8UZ4cE_dl for <rtcweb@ietfa.amsl.com>; Mon, 8 Dec 2014 11:53:16 -0800 (PST)
Received: from mail-ob0-x234.google.com (mail-ob0-x234.google.com [IPv6:2607:f8b0:4003:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41EA81A011E for <rtcweb@ietf.org>; Mon, 8 Dec 2014 11:53:16 -0800 (PST)
Received: by mail-ob0-f180.google.com with SMTP id wp4so4191833obc.11 for <rtcweb@ietf.org>; Mon, 08 Dec 2014 11:53:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=CX9ZXQjJj6qRhupw9dKunlR2DYXxytHFOGPE5CimInE=; b=YI4fTEcmNuH0Cq+XBmwR8FK/IsMlszepPORs+S8Cg2dkH9BINwR/6eInBFojdmoD3H 2hafNuO1KojSxjWwKmwCvk5TkIQlkAVVnjgNTEZJXsfp5LhUJpwBf6sXNp5GAADRXzoo 2FUg2+gE3t5jtOOcx4kQXyMtF/lvzdxYLKmDJc0nA2vnipsxtfnIz7KYifFZH+GNZWP8 wV1F9oD005jXCPm1akXsE26jLet1TA5BdYLbYt/MwzQn++vBVqCIcGid7+5eiFRraRLu EcuE3/phUDOuQZVvWfZcXpRPuxL4Phb0B/HcGjGTUtr+Jam2AueQsPPqGjgcTxiDUPvY 5G6g==
MIME-Version: 1.0
X-Received: by 10.182.165.69 with SMTP id yw5mr20797276obb.36.1418068395476; Mon, 08 Dec 2014 11:53:15 -0800 (PST)
Received: by 10.202.227.77 with HTTP; Mon, 8 Dec 2014 11:53:15 -0800 (PST)
In-Reply-To: <54860094.6040703@gmail.com>
References: <92D0D52F3A63344CA478CF12DB0648AADF35B076@XMB111CNC.rim.net> <5485CD70.4010605@gmail.com> <92D0D52F3A63344CA478CF12DB0648AADF35B132@XMB111CNC.rim.net> <CA+ag07YavPwRhcM35KA8UQ4gFU5xFYFbdstRDKJ3-9HRCYS6DA@mail.gmail.com> <92D0D52F3A63344CA478CF12DB0648AADF35B4D8@XMB111CNC.rim.net> <54860094.6040703@gmail.com>
Date: Mon, 8 Dec 2014 11:53:15 -0800
Message-ID: <CAA93jw76KXasBxLvZ_BH1z_BB=A3zCiSRLEez1x1pLKo_+bidA@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/bFbtIh-Xa90aQFvcv7XccDubvmI
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
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:53:18 -0000

I would like emacs support.

I am not actually joking...

I typically work in emacs with an erc window open and it would be nice
to see who I am working with inside of emacs, rather than a browser.
Have no idea how to do this....

/me goes to look at resiprocate....



On Mon, Dec 8, 2014 at 11:48 AM, Sergio Garcia Murillo
<sergio.garcia.murillo@gmail.com> wrote:
> The question, is who cares?
>
> My  application will do whatever is needed for my service, implement one,
> two, three or none video codecs according to my business requirements. I
> don't really care (so won't my users) if you call it webrtc endpoint,
> webrtc-compatible endpoint or webrtc-non-compatible endpoint.
>
> So, from my point of view, we are just discussing about definitions of
> entities so we all speak same languages, any attempt to push a MTI codec is
> wishful thinking at best.
>
> Talking about reality, from my experience, most of the apps will be google's
> libwebrtc based, so they will implement whatever is provided in there. VP8
> for sure, and h264 if supported by mobile and used by libwebrtc.
>
> On a side note, with current state of specs, a Microsoft based ORTC
> implementation on IE will be a webrtc endpoint.
>
> Best regards
> Sergio
> On 08/12/2014 19:00, Gaelle Martin-Cocher wrote:
>
> Do you have any concrete examples?
>
> Does this mobile app, needs to interact with another mobile app? Again, I am
> looking for concrete example.
>
> I bet that every single webrtc service will be a webrtc compatible endpoint.
>
> I would like to have a confirmation that this is not the case and that those
> apps that you are mentioning will interact with other apps and implement
> both codecs.
>
>
>
> Best,
>
> Gaëlle
>
>
>
>
>
> From: Sergio Garcia Murillo [mailto:sergio.garcia.murillo@gmail.com]
> Sent: Monday, December 08, 2014 12:10 PM
> To: Gaelle Martin-Cocher
> Subject: RE: [rtcweb] WebRTC endpoint non-browser
>
>
>
> 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
>
> El 08/12/2014 17:24, "Gaelle Martin-Cocher" <gmartincocher@blackberry.com>
> escribió:
>
> 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
> https://www.ietf.org/mailman/listinfo/rtcweb
>



-- 
Dave Täht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks