Re: [rtcweb] Meaning of SHOULD support/use interleaving

Martin Thomson <martin.thomson@gmail.com> Tue, 28 October 2014 00:25 UTC

Return-Path: <martin.thomson@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 C5E071A87CE for <rtcweb@ietfa.amsl.com>; Mon, 27 Oct 2014 17:25:53 -0700 (PDT)
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 4ExlPMjEttUu for <rtcweb@ietfa.amsl.com>; Mon, 27 Oct 2014 17:25:51 -0700 (PDT)
Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 75D4A1A87C9 for <rtcweb@ietf.org>; Mon, 27 Oct 2014 17:25:51 -0700 (PDT)
Received: by mail-lb0-f176.google.com with SMTP id p9so6557490lbv.7 for <rtcweb@ietf.org>; Mon, 27 Oct 2014 17:25:49 -0700 (PDT)
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; bh=VkJOF5VwVsmV7KOF7/MWCazKzIAoGHZbcluAGgZNwh0=; b=koxOvGNrIu1gT0YWmj10A9XdAcOFJfrMGNwaj3yD4ELGh7Px3OsDXAHO3Y1n1vQn3W VobIKe421WiyJCo8iXJeVQdwZa+TZgr0f8nsTUhoOGcszL1mSUEHwK+r3j8sL4xcfHEu sNayV1IRBNJiiNzmtwttI99Mw1XPtHaEkepixRClNIUwtJOKRv7iSaYPkgGRc1xCIuro 1uIKQ8jGYyqG/5N+eKINz7xB8VawZ/8ANxpvGE+1nG0qTzTIeVl/BIYQEV1k1GbOm7yj MCcoSKcsn531wyUMcM4TZiUUfnOoLoOHmGKm3Ra6YBjZOd6D7dyGueu3+kMtjmhI4uG7 JHlw==
MIME-Version: 1.0
X-Received: by 10.152.20.72 with SMTP id l8mr20041908lae.43.1414455949825; Mon, 27 Oct 2014 17:25:49 -0700 (PDT)
Received: by 10.25.215.217 with HTTP; Mon, 27 Oct 2014 17:25:49 -0700 (PDT)
In-Reply-To: <544EC109.4030600@alvestrand.no>
References: <7594FB04B1934943A5C02806D1A2204B1D4CCEEF@ESESSMB209.ericsson.se> <EA00639E-2008-4BD2-88F2-27AAEE9DA213@lurchi.franken.de> <7594FB04B1934943A5C02806D1A2204B1D4CD241@ESESSMB209.ericsson.se> <544E8D92.8010401@alvestrand.no> <7594FB04B1934943A5C02806D1A2204B1D4CE9DA@ESESSMB209.ericsson.se> <544EA473.6040700@alvestrand.no> <7594FB04B1934943A5C02806D1A2204B1D4CEBED@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17828E5F2ED0@US70UWXCHMBA02.zam.alcatel-lucent.com> <544EC109.4030600@alvestrand.no>
Date: Mon, 27 Oct 2014 17:25:49 -0700
Message-ID: <CABkgnnVi_s_2TLc6AGtg9bTDDhwACWyH1dJqgV9UN8SPFa7nyg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/zMxQDT6zdB_6CORxmv4yv62yx9I
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Meaning of SHOULD support/use 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: Tue, 28 Oct 2014 00:25:53 -0000

On 27 October 2014 15:02, Harald Alvestrand <harald@alvestrand.no> wrote:
> You're confusing the webrtc application (what runs in the browser) with the
> webrtc implementation (the browser itself). Optional NDATA makes the browser
> *more* complex, since it has to expose API surface to let the application
> choose whether or not to offer NDATA, and it has to have code to decide
> whether or not to offer NDATA.


Yes.  I don't understand why we would want to say no to making NDATA
mandatory for browsers, other than to note that not all peers will
support NDATA.

SCTP without NDATA simply isn't fit for purpose.