IETF Logo Mail Archive

Re: [rtcweb] UDP transport problem

Dave Taht <dave.taht@gmail.com> Thu, 13 February 2014 22:46 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 E6B9E1A044D for <rtcweb@ietfa.amsl.com>; Thu, 13 Feb 2014 14:46:55 -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 100cocqkdUt2 for <rtcweb@ietfa.amsl.com>; Thu, 13 Feb 2014 14:46:53 -0800 (PST)
Received: from mail-qa0-x22b.google.com (mail-qa0-x22b.google.com [IPv6:2607:f8b0:400d:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 34C441A0079 for <rtcweb@ietf.org>; Thu, 13 Feb 2014 14:46:53 -0800 (PST)
Received: by mail-qa0-f43.google.com with SMTP id o15so17391881qap.30 for <rtcweb@ietf.org>; Thu, 13 Feb 2014 14:46:51 -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=v/Q5eCR4sSkYc6QZdxsn9lQ664jGblOAEf7wDEwOptA=; b=kwcw4qIIX8uUtlkXVpLN77mwmry/ni8rWoAu6JDthJ+splQCxnP2GeSnSqVWVPSYfP yy4OLbNCbe0tAxPKhU9aTWFAQQ4tMv9k+/cC4b+0itDi460Mc6bdly8DNm3g/E3kzgfc dRPWVdrmurMEDG/u9eWpxv+Ki8zdThbIlAXxS9LqoLN/72JhyJxGhowAQioZKLfd7kAO oa+RcZzoIGJa/x00vZR7XNnMCJvefJ0F63gDYRAB4FTEIxm3PIR5M3G87gUsEO2phR4n q8ew5bOcNDa7OmhjhuOxr2D25IQTkIXlx4zhVxcFaVJmBpPUW22/aw1RtOyPsGb7C2Yn uipQ==
MIME-Version: 1.0
X-Received: by 10.140.89.167 with SMTP id v36mr6810000qgd.27.1392331611853; Thu, 13 Feb 2014 14:46:51 -0800 (PST)
Received: by 10.224.27.133 with HTTP; Thu, 13 Feb 2014 14:46:51 -0800 (PST)
In-Reply-To: <52FD46F4.7030804@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>
Date: Thu, 13 Feb 2014 17:46:51 -0500
Message-ID: <CAA93jw4_+xAVza-YDpPD80Fj749i=vgOSz7sAty_Zp4U2TuO6g@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/ZdBJuOC3unMmu0Jvw_QzuQMF7So
Cc: 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 22:46:56 -0000

On Thu, Feb 13, 2014 at 5:28 PM, cowwoc <cowwoc@bbs.darktech.org> wrote:
> On 13/02/2014 4:20 PM, Cb B wrote:
>>
>> DNS runs over TCP as well. But that's not the point. The question is can
>> we include native SCTP as an option in draft-ietf-rtcweb-transports? What is
>> the downside? CB
>
>
> The biggest downside, as I see it, is that 90%+ of the world runs Windows
> and that platform does not support SCTP natively (a fact that you have
> mentioned before). I am all in favor of SCTP, but I think you need to solve
> the Windows problem before this solution become meaningful.

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.

>
> Gili
>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb



-- 
Dave Täht

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

v2.23.0 | Report a Bug | By Email