IETF Logo Mail Archive

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

Eric Rescorla <ekr@rtfm.com> Tue, 28 October 2014 00:30 UTC

Return-Path: <ekr@rtfm.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 39FF51A0358 for <rtcweb@ietfa.amsl.com>; Mon, 27 Oct 2014 17:30:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 f2Zbh6_24Dur for <rtcweb@ietfa.amsl.com>; Mon, 27 Oct 2014 17:30:08 -0700 (PDT)
Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B1F81A02BE for <rtcweb@ietf.org>; Mon, 27 Oct 2014 17:30:07 -0700 (PDT)
Received: by mail-wg0-f50.google.com with SMTP id z12so4419573wgg.9 for <rtcweb@ietf.org>; Mon, 27 Oct 2014 17:30:06 -0700 (PDT)
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=78ieX0Hzaf26+DjDCOtVCjEP22B2ROOGD+sv8D+wp+I=; b=hO3ZiIluGlU1DhPJcWRhrOXdWMV7e0i0EIA7BO3o2ghUCLJxj4zMcKUvPUP3CNfT+w upgd4mWzI6KTykdszNdoMlfRjOcUXXEXIk9OYELCLykv7vUQtL7xyOxb2QEglE/To8B2 i0CXWPk7xgZHtOIjLNdKf2SnJuimnv5UF3WOoiZtJbo5BZ1YLd0ygzBsujr/tTEkaRSr vpuHwk512Eoa4jwZpM3fiCx9m/k2KwKFGhReVSvahCHyXJvwkptiTtTmH9YfBHYmzcfQ +6zoVD554LSwucclYbLA4/7+qZ6dDEWl9Y0BkABhAZgYIESnpRp1fjXQSq6wkIETIi3a mvMg==
X-Gm-Message-State: ALoCoQm/18Ry3/R6WdKbFfMNnLMn2yokUg+hCB81gtq5f0x0w4l0z27xFPXJiqUgXFj3QtHGXaxP
X-Received: by 10.194.242.4 with SMTP id wm4mr3254582wjc.61.1414456206782; Mon, 27 Oct 2014 17:30:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.49.198 with HTTP; Mon, 27 Oct 2014 17:29:26 -0700 (PDT)
In-Reply-To: <CABkgnnVi_s_2TLc6AGtg9bTDDhwACWyH1dJqgV9UN8SPFa7nyg@mail.gmail.com>
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> <CABkgnnVi_s_2TLc6AGtg9bTDDhwACWyH1dJqgV9UN8SPFa7nyg@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 27 Oct 2014 17:29:26 -0700
Message-ID: <CABcZeBP+Z_GyYRMnF1O9ouMOn7SW9b_h2bh7GVNJpQEHDy4a+Q@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary="089e01419af6c183c0050670bf17"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/wHFVy2d7vjdwxNs-fVzepXyACTU
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:30:10 -0000

On Mon, Oct 27, 2014 at 5:25 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> 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.
>

I agree with this. Let's require what we need.

-Ekr

SCTP without NDATA simply isn't fit for purpose.
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>

v2.30.2 | Report a Bug | By Email | System Status