IETF Logo Mail Archive

Re: [rtcweb] UDP transport problem

"Jeremy Laurenson (jlaurens)" <jlaurens@cisco.com> Sun, 16 February 2014 14:57 UTC

Return-Path: <jlaurens@cisco.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 CC3151A03EE for <rtcweb@ietfa.amsl.com>; Sun, 16 Feb 2014 06:57:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.049
X-Spam-Level:
X-Spam-Status: No, score=-15.049 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 Mi2Xd8DjAPw4 for <rtcweb@ietfa.amsl.com>; Sun, 16 Feb 2014 06:57:30 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id D14271A03EC for <rtcweb@ietf.org>; Sun, 16 Feb 2014 06:57:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2434; q=dns/txt; s=iport; t=1392562648; x=1393772248; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=FOe+6WjFQ8d+HpOZbhQpCBMSyMsHDghjCs7KsQROGpE=; b=crsQd7c92QxEhBWPbJVlgn6suhBFs+gdy3C9bg9rVf1x5JFgJGnLKuxe 8AL47h4GGal6YnqPuCHUv5sCB7awZLN3GrBZwlRz+mH0gQcIS+tGyf2Jc 5gx9RqKq9H3UuPMJn9N42qql3rrEkAhEorvLKW+DbB1UzoY/wjaVoNEWW M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFABzRAFOtJV2d/2dsb2JhbABZgwg4vHRPgRAWAXSDfQEBAQMBAQEBNw8lCwULAgEIGB4QJwslAgQOBYd8CA3BSheOXzMHhDYEmBaSFIMr
X-IronPort-AV: E=Sophos;i="4.95,855,1384300800"; d="scan'208";a="301395319"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-9.cisco.com with ESMTP; 16 Feb 2014 14:57:27 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s1GEvRj3029081 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 16 Feb 2014 14:57:27 GMT
Received: from xmb-rcd-x03.cisco.com ([169.254.7.15]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.03.0123.003; Sun, 16 Feb 2014 08:57:27 -0600
From: "Jeremy Laurenson (jlaurens)" <jlaurens@cisco.com>
To: Tim Panton <tim@phonefromhere.com>
Thread-Topic: [rtcweb] UDP transport problem
Thread-Index: AQHPKx/ReTPUYSIEFUimiJt3/lhYxJq3+JDm
Date: Sun, 16 Feb 2014 14:57:26 +0000
Message-ID: <93FE15F7-DE61-41C6-845E-949188098013@cisco.com>
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>, <CE142A3F-F105-4E9A-AF64-C42A052F448A@phonefromhere.com>
In-Reply-To: <CE142A3F-F105-4E9A-AF64-C42A052F448A@phonefromhere.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/RHD_xHbpG5HZXtqbAkovdOX4RRk
Cc: "rtcweb@ietf.org >> 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: Sun, 16 Feb 2014 14:57:32 -0000

Why would we assume anything about the devices this stuff will run on in the future? Technology change tells me we'll all be wrong and underestimate what's next. Assume WebRTC on everything, including my smarty ring. :-)

Jeremy

> On Feb 16, 2014, at 9:03 AM, "Tim Panton" <tim@phonefromhere.com> wrote:
> 
> 
>> On 13 Feb 2014, at 23:50, 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.
>> 
>> Gili
> 
> Again, I disagree, I often use a smartphone for video, but only if I can airplay/chromecast the video to a suitable TV.
> 
> 
> T.
> 
> 
> Tim Panton - Web/VoIP consultant and implementor
> www.westhawk.co.uk
> 
> 
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email