Re: [rtcweb] #13: Transport of DATA_CHANNEL_OPEN

Michael Tuexen <Michael.Tuexen@lurchi.franken.de> Sat, 20 April 2013 19:38 UTC

Return-Path: <Michael.Tuexen@lurchi.franken.de>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCFB021F8E96 for <rtcweb@ietfa.amsl.com>; Sat, 20 Apr 2013 12:38:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NDKQU5d2leig for <rtcweb@ietfa.amsl.com>; Sat, 20 Apr 2013 12:38:28 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) by ietfa.amsl.com (Postfix) with ESMTP id C1E9021F8E36 for <rtcweb@ietf.org>; Sat, 20 Apr 2013 12:38:27 -0700 (PDT)
Received: from [192.168.1.102] (p54818039.dip0.t-ipconnect.de [84.129.128.57]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id CFC941C0B4617; Sat, 20 Apr 2013 21:38:26 +0200 (CEST)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset="us-ascii"
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <5171734E.3050300@jesup.org>
Date: Sat, 20 Apr 2013 21:38:26 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D3E402DD-23F3-4309-BB1C-2FF1C89506C6@lurchi.franken.de>
References: <066.3120a55540cacaa74ee5fda0b5273a48@trac.tools.ietf.org> <516CE3EC.2050804@jesup.org> <CABkgnnVaTOLa-hs7AtEgaTk7eq00bEkCY+_8L96Y8pooqybBxA@mail.gmail.com> <CAJrXDUFgxLT3-1HehKbg5byzifFi4Obe3XW9G4sbWRbnU+Hi1A@mail.gmail.com> <CABkgnnXr85LZyJiSF+ok2KMS_xQnS0CE4VBq4PvEhBBscn2QZQ@mail.gmail.com> <516F1AF9.2080301@alvestrand.no> <CABkgnnVtUjk4jSDVioxQnrt-b69Hx0nZLefs7tpEzETSmLXeNA@mail.gmail.com> <516F9A5A.6080402@alvestrand.no> <CABkgnnWrAMnm5fTWCNA1jqC_8Js0a6ewfSkvni4xg0E6rXdCtA@mail.gmail.com> <5170247F.4090908@alvestrand.no> <CABkgnnXU4HeJT-QwDcJ5NTvr72gZXxXi5zHFkQjJS__UXqzvtQ@mail.gmail.com> <206CB075-6754-4578-B623-866E410DACCC@lurchi.franken.de> <CABkgnnUCXUH+0a+F1LVQVrtL=Q65HGgsdT-oBBF++zSVR4OhWw@mail.gmail.com> <5171734E.3050300@jesup.org>
To: Randell Jesup <randell-ietf@jesup.org>
X-Mailer: Apple Mail (2.1283)
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] #13: Transport of DATA_CHANNEL_OPEN
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 20 Apr 2013 19:38:29 -0000

On Apr 19, 2013, at 6:39 PM, Randell Jesup wrote:

> Since we send the Open reliably, barring active attempts to game the system with a non-browser, the Open *will* eventually get through unless you have 100% (or virtually so) packet loss (and in that case, nothing useful, including an error response, is getting through anyways).  So I honestly feel it's ok to just buffer all incoming packets while waiting for the Open.
I'm not sure what you want to protect against:
1. Network conditions resulting in loss of the OPEN_REQ
2. The peer attacking you and violating the protocol spec.

If you consider 1., SCTP will get the message through or fail the SCTP association eventually.
In the BSD stack we even limit the number of retransmissions of a particular chunk. If that
number is reached, the association is failed. We used this to protect against buggy peers
or path MTU problems.

Best regards
Michael
> 
> No one is going to get a gigabyte of data in without an Open...  A non-browser could fake up a session and start sending data without ever sending an Open... but flushing the data doesn't actually help you against that sort of active DOS (they can just start again, they can spread it across thousands of channels, etc, etc), and there are FAR better DOS methods - all this would do is burn some CPU and some memory.
> 
> -- 
> Randell Jesup
> randell-ietf@jesup.org
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>