IETF Logo Mail Archive

Re: [rtcweb] RTCWEB Data Channel: message interleaving

Justin Uberti <juberti@google.com> Fri, 07 February 2014 06:40 UTC

Return-Path: <juberti@google.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 64F4D1A05B3 for <rtcweb@ietfa.amsl.com>; Thu, 6 Feb 2014 22:40:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.913
X-Spam-Level:
X-Spam-Status: No, score=-1.913 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.535, 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 J_GWv0RsOv8C for <rtcweb@ietfa.amsl.com>; Thu, 6 Feb 2014 22:40:57 -0800 (PST)
Received: from mail-vb0-x234.google.com (mail-vb0-x234.google.com [IPv6:2607:f8b0:400c:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id 02EC91A05B0 for <rtcweb@ietf.org>; Thu, 6 Feb 2014 22:40:56 -0800 (PST)
Received: by mail-vb0-f52.google.com with SMTP id p14so2325486vbm.11 for <rtcweb@ietf.org>; Thu, 06 Feb 2014 22:40:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=YUbH8pIRepQhZtEKGtFoUq53ooyF4iLtfO7AMmktZZY=; b=P4UhAK16guX8r/zCehvNZFHECVOeUwDgnJkRNoMmdsyI/9Nagdh1+Z663Fo8kNe7WJ 5LrmIu8G9RK0+aLpJqxRg+Ey76mB5tISu6TudamFLWGHO998OkUwzanQ1bJlx/AhDeXi JUjh02dxyVYmpZVHV3Qj9PJ4OKjgBGgM0wOFSbLfOAiKNaT+4lhul9GYw2TnS1IAS9H9 QTkx0krXOzISuB3NhMDJuV4vbDsPGJO2UQwBNGn9r5Tps/AaMnzm0DoROT/Ms4jLviYw ysXMSn1cBJhPSwldrBe1fmyNwa0LW2d90Uj6+F2zDb8P/UHJRTXfxqH3dPryaedk3987 dWCQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=YUbH8pIRepQhZtEKGtFoUq53ooyF4iLtfO7AMmktZZY=; b=AWDc2m74rn8URAAVo402cifjyXF7+Gw7Nk26Xj5QMJHFDuTT4oE5FlVu+yPuSm0nsI D8qCwNcd7ZZmG4bpZYAJ7k+C/pymiLldPD5k/psrFNPXDH43t4nrk4GEhWGcovnwS8aF 7nd4fRCFGqzN3zHEIf3raR0pKaydAqMtrjQmFkCb37Eyv1VjuM+CtrLNpyAIRgT43Kky JwPISsxionZOCMrfaJIaYv9uUXwa60cQGc2a3jpzPErd1OSBsCrPny4rBOX1ktEkFpIX 8QpqBmkA4fZb8aBGIbobYZgJYSvRRTMjpao/ga88wQLeXI5/iFNwqQasalzKww7noTY8 vgxw==
X-Gm-Message-State: ALoCoQkyZXuSKWD0OjWn/InvsmjXCS5auhbJa/fhXqZsFcrQ0ZqiVK0TaoT0KbFkJpXRCS5HAMGv7FrgL5JOtKnaq5S+4YtXIkaX6jPoUA5URcN7omGeDcQcZNuIGnjTYxHILKTeMDcbMafsJf3WYYyd/sxU9mL0foUKFLDaQpxV8+EQEfxgMdEBP8oOjNmDNPf8ExhnR8Ke
X-Received: by 10.52.232.168 with SMTP id tp8mr144693vdc.38.1391755255425; Thu, 06 Feb 2014 22:40:55 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.89.170 with HTTP; Thu, 6 Feb 2014 22:40:35 -0800 (PST)
In-Reply-To: <E1FE4C082A89A246A11D7F32A95A17826DFD1A8F@US70UWXCHMBA02.zam.alcatel-lucent.com>
References: <7594FB04B1934943A5C02806D1A2204B1D15BD1A@ESESSMB209.ericsson.se> <CAJrXDUGJO1C-47PmU7nwgRaZu19XTvsgwyq=6m=-vsL6LYqqLA@mail.gmail.com> <E1FE4C082A89A246A11D7F32A95A17826DFCD56D@US70UWXCHMBA02.zam.alcatel-lucent.com> <CAJrXDUGtf4U_jhX1hmbPTtXQidR=oHL0cCrKCaZhnLsQd8NvLw@mail.gmail.com> <A9D7F81A-C0E6-44DF-AFC4-4AAB1E78DA19@lurchi.franken.de> <E1FE4C082A89A246A11D7F32A95A17826DFCD683@US70UWXCHMBA02.zam.alcatel-lucent.com> <CFF06852-E7C6-4A9D-A15B-D79F45D24834@lurchi.franken.de> <52F2B457.8040305@alum.mit.edu> <E1FE4C082A89A246A11D7F32A95A17826DFCD8A3@US70UWXCHMBA02.zam.alcatel-lucent.com> <52F2C347.7000304@alum.mit.edu> <E1FE4C082A89A246A11D7F32A95A17826DFCDB0B@US70UWXCHMBA02.zam.alcatel-lucent.com> <D0E5C5FC-43FA-4BEF-941F-367573D9CBDA@lurchi.franken.de> <7594FB04B1934943A5C02806D1A2204B1D15EDA7@ESESSMB209.ericsson.se> <6A0518D4-D15D-4970-A56C-87FEDA60F978@lurchi.franken.de> <52F3B6E5.9040001@alum.mit.edu> <E1FE4C082A89A246A11D7F32A95A17826DFD1A8F@US70UWXCHMBA02.zam.alcatel-lucent.com>
From: Justin Uberti <juberti@google.com>
Date: Thu, 06 Feb 2014 22:40:35 -0800
Message-ID: <CAOJ7v-27Z2XpHSObmU-Y3ovQupgovza+O2ZR2B--mS4ADjWDNg@mail.gmail.com>
To: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
Content-Type: multipart/alternative; boundary="089e01183a009d495704f1cb45e0"
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] RTCWEB Data Channel: message interleaving
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: Fri, 07 Feb 2014 06:40:59 -0000

The browser will enforce the message limit to ensure predictable behavior.


On Thu, Feb 6, 2014 at 12:15 PM, Makaraju, Maridi Raju (Raju) <
Raju.Makaraju@alcatel-lucent.com> wrote:

> > > * If NDATA is not supported by both peers, a message size limit
> applies to
> > avoid monopolisation.
> >
> > I assume that in the RFC this will just be a MUST NOT. Will that apply
> > to the SCTP implementation? Or to the SCTP user?
> >
> > (In a practical sense, will this be implemented in the SCTP stack, in
> > the DataChannel "stack", in the browser, or in javascript?)
>
> [Raju] It has to be done exclusively by the application (Javascript for
> browser or some other language for native apps).
> This is because per recent comments the browser/data-channel level
> fragmentation/reassembly, based on PPID, will be removed from data channel
> core spec.
>
> -Raju
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>

v2.23.0 | Report a Bug | By Email