IETF Logo Mail Archive

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

Justin Uberti <juberti@google.com> Tue, 28 October 2014 00:39 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 5CFD41A0360 for <rtcweb@ietfa.amsl.com>; Mon, 27 Oct 2014 17:39:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level:
X-Spam-Status: No, score=-1.388 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 JedOsS4TdLwj for <rtcweb@ietfa.amsl.com>; Mon, 27 Oct 2014 17:39:32 -0700 (PDT)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 443E61A02BE for <rtcweb@ietf.org>; Mon, 27 Oct 2014 17:39:32 -0700 (PDT)
Received: by mail-oi0-f41.google.com with SMTP id e131so1615632oig.14 for <rtcweb@ietf.org>; Mon, 27 Oct 2014 17:39:31 -0700 (PDT)
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=6lx38xQ1sfs0cOymsPOHUp6Z433C+8EfFmYdS4Uv0rA=; b=Mx6Tp/R4hLshAv0cra7yrfI/vzhFTpNdD0TPIDIVG3zSY95hKF4lPWCfXvMbVVsosC w5wnWk5cd4u3eIz7B/e+Ww16Ckwd6H2MEg8iRxmXvb6mFGE3trzGbuxkZNNad3L0gG8G 3WyQMw8XH2yX290/XT5tun8bo4DsQEStpECzNBVoDGRLuX46qGhhx0sLJvQErYaVJpf/ dNdZIa8Z1obRjGF67KbaG5P2f6UaLdTRu9Y2pz2rBHZxi/4tKQyQXqkEymYWDZ/qcwgb DKBlNmNLcJgnlwqSBcXGtwQfJMxnAPVAJ75nC9mo4C8d6rrfGixzxfAC0Y14wEEqbb4x A3Hw==
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=6lx38xQ1sfs0cOymsPOHUp6Z433C+8EfFmYdS4Uv0rA=; b=mE+3aGyq9RsoNcWFVGmbGI06ZZOdCKwmPjcGmlTYr9jb8IyHzQP8I8sQpms7wyuNjt I2Im2j8DLoHwu2e3zRj4uoJYxAYoIi+/2OtrKcGHa6N8a/hBloIOal0xvV/tWnxffJmH Pu82x5yIVS8zlBCnJHNciyVsb6RAaEtPRH4nczzWUobXH3v75MxIPR2Y4cJ73w7xWcTV q1YXVkVF6sXwaXD1kMDcd1/Lx0xW1emnE7xuwWatLHVIr6FmvXhxX1OvGMHH4zP1g89i 3j7MLNuU5SV3mX1JmTeKDig1EtCg7IddYFIvgFoSA7fvm28GK6/7MscUgbEbco3LR1xn hm+Q==
X-Gm-Message-State: ALoCoQmdsjXsVWBa9fNjJnUIcA/R4GqZOSZGFxZ78wM3KmKtVv0/3qjzHTfYVxb57jQqRa39fFkJ
X-Received: by 10.182.224.231 with SMTP id rf7mr44452obc.77.1414456771724; Mon, 27 Oct 2014 17:39:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.248.170 with HTTP; Mon, 27 Oct 2014 17:39:11 -0700 (PDT)
In-Reply-To: <CABcZeBP+Z_GyYRMnF1O9ouMOn7SW9b_h2bh7GVNJpQEHDy4a+Q@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> <CABcZeBP+Z_GyYRMnF1O9ouMOn7SW9b_h2bh7GVNJpQEHDy4a+Q@mail.gmail.com>
From: Justin Uberti <juberti@google.com>
Date: Mon, 27 Oct 2014 17:39:11 -0700
Message-ID: <CAOJ7v-0_1XoZJ+F9LavfBeLN-0x9_ZfJ_zaS4Q_uP+gMoRipBw@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Content-Type: multipart/alternative; boundary="089e0149c8e26e0aeb050670e199"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/4ByetODUrHYktKb3IflOMfBdr4I
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:39:33 -0000

On Mon, Oct 27, 2014 at 5:29 PM, Eric Rescorla <ekr@rtfm.com> wrote:

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

+1. The fewer optional things we have, the more likely things will Just
Work.

v2.23.0 | Report a Bug | By Email