Re: [rtcweb] UDP transport problem

Dave Taht <dave.taht@gmail.com> Thu, 13 February 2014 23:54 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 DF6FE1A033A for <rtcweb@ietfa.amsl.com>; Thu, 13 Feb 2014 15:54:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 7qLmHAFTah94 for <rtcweb@ietfa.amsl.com>; Thu, 13 Feb 2014 15:54:57 -0800 (PST)
Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 9C93B1A0026 for <rtcweb@ietf.org>; Thu, 13 Feb 2014 15:54:57 -0800 (PST)
Received: by mail-qa0-f49.google.com with SMTP id w8so17027941qac.22 for <rtcweb@ietf.org>; Thu, 13 Feb 2014 15:54:56 -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=vaxfctYj5JW3EVhEDQZ1YcydBsz1hulWnF2NdBaA3Ns=; b=UWOxKShQ5oB1Bmf5SoOeT0CLk3OeEdWaDwINCNih3SZ1PTWImfuMDDefvYMGE9bJDp LQjlSUuHSRAbgNvKqlR84D+P7MBpz6w9A/RE/OZh2HgW7ynWFExVypUk5Tt/tjLuNToX TT8AOENESSyMkipHRnhfEpC5LawsmKqxvHPnGXYMtXOv51vxTfrMSnqYUUPIwyxpDPHn CDt868oFMRUlIewKYBe7o4TXxqOMAgqlfi6pvojeQbrg2yQIXhZkdy70nt4sHWKWJIHb p+cv7HaxnElzQnEwam6XQFYwwk6mc5iAjBYjoxoHeHUeMMGhh/NVWVxMDsQWKwAM83M/ Thmw==
MIME-Version: 1.0
X-Received: by 10.140.91.23 with SMTP id y23mr7237014qgd.3.1392335696247; Thu, 13 Feb 2014 15:54:56 -0800 (PST)
Received: by 10.224.27.133 with HTTP; Thu, 13 Feb 2014 15:54:56 -0800 (PST)
In-Reply-To: <52FD5A4E.8060604@bbs.darktech.org>
References: <CAD6AjGRiQ1UF5n3JG9HPRQFM+TD54Xz-dpTn5u9bX+__BMfesQ@mail.gmail.com> <CABkgnnVbZp7yBvpY1ARuaBXS=TOipY=BhXzrd=h5DY-76oF9Pw@mail.gmail.com> <CAD6AjGSxS4jNRGotsE_no0XhewvDqcVZ+Kmx1aMW9qorqSKR+w@mail.gmail.com> <52FD2FA4.8040701@alvestrand.no> <CAD6AjGTbSJEV2cJj5QyLktyZPv8SJa7h-QHKVtdUXnF3K6xwHA@mail.gmail.com> <52FD46F4.7030804@bbs.darktech.org> <CAA93jw4_+xAVza-YDpPD80Fj749i=vgOSz7sAty_Zp4U2TuO6g@mail.gmail.com> <52FD4C82.8040300@bbs.darktech.org> <CAA93jw5gEUzQeF74o_tt5KgdqFiedXzT5G0WdARsdcRnVEe6EQ@mail.gmail.com> <52FD5A4E.8060604@bbs.darktech.org>
Date: Thu, 13 Feb 2014 18:54:56 -0500
Message-ID: <CAA93jw5v_6rnwUbvjmjYyYdP9WmWM+z-wmYV+c9kSyOMbswtfA@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: cowwoc <cowwoc@bbs.darktech.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/wjgguOP8IVLthSHheCqGpQV-DyQ
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] UDP transport problem
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: Thu, 13 Feb 2014 23:55:00 -0000

On Thu, Feb 13, 2014 at 6:50 PM, cowwoc <cowwoc@bbs.darktech.org> wrote:
> On 13/02/2014 6:00 PM, Dave Taht wrote:
>>
>> On Thu, Feb 13, 2014 at 5:51 PM, cowwoc <cowwoc@bbs.darktech.org> wrote:
>>>
>>> On 13/02/2014 5:46 PM, Dave Taht wrote:
>>>>
>>>> The biggest downside, as I see it, is targeting advancements in the
>>>> state
>>>> of
>>>> the art, at windows. 98% of the world or so run non-windows based cell
>>>> phones and tablets, and in terms of total users, probably outnumber
>>>> the windows contingent at this point.
>>>>
>>>> SCTP and MPTCP are quite feasible on android and IOS.
>>>
>>>
>>> It doesn't matter how many smartphones there are. What matters is how
>>> many
>>> of them will be used to do meaningful video chat. The screen real estate
>>> on
>>> these devices is way too small.
>>
>> In my experience, everybody is using tablets and handheld devices for
>> video chat.
>> It is a natural extension of the usage of the device to extend it from
>> phone calls
>> to video calls.
>>
>> The lack of a working camera on most desktops is a hindrance, and the
>> placement
>> of cameras on most laptops is not ideal.
>
>
> All laptops and tablets come with decent cameras. I will agree that WebRTC
> on tablets will be strong, but smartphones is really pushing it. Most of the
> time I've seen people engage in video chat it was between family members;
> far less for business use. And in those cases, I've seen people jump on
> tablets and laptops instead of having to deal with a tiny, underpowered
> smartphone for video. These are just personal observations, not science, so
> please take them with a grain of salt.

I will clarify what I said above is that what I observe among the under 20s
is huge tablet and handheld use for videoconferencing. For business use
I see primarily things like dedicated hardware, webex and to a smaller
extent hangouts,
and facetime.


> Gili



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html