Re: [rtcweb] Amount of streams supported for data channels

Taylor Brandstetter <deadbeef@google.com> Wed, 11 April 2018 20:29 UTC

Return-Path: <deadbeef@google.com>
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 C680812D72F for <rtcweb@ietfa.amsl.com>; Wed, 11 Apr 2018 13:29:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 7qBlGAwpgQId for <rtcweb@ietfa.amsl.com>; Wed, 11 Apr 2018 13:29:22 -0700 (PDT)
Received: from mail-vk0-x235.google.com (mail-vk0-x235.google.com [IPv6:2607:f8b0:400c:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0840D1271FD for <rtcweb@ietf.org>; Wed, 11 Apr 2018 13:29:22 -0700 (PDT)
Received: by mail-vk0-x235.google.com with SMTP id n124so1898965vkd.6 for <rtcweb@ietf.org>; Wed, 11 Apr 2018 13:29:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=S+7ti+kDO4I5pn4nBWxMKnFNBHOIWQByq+ZJiqZI+h0=; b=B7Nb5Bt3TW9VD4Tw7GLnzQpdZ7uAZ8DTlnziNpkjbSkxffpMCjHcHN1LqZfQVToA7M 6ww3WUUHHOZekXb+FEfc2E0wPGVWRujLrv6Wb7kz25L40F4/qZFARWGtqpa83EBCY8yA tM2xlT90cKr+BsWW1OJ+j5al6doYjY2QxbEpws+0bstigdyGmEVyODaD71IISSguqmVC 4cjvfJ/gAzU6/yfpuQbYp4ja4cSpbJDLgVtp2UZbCjh1rxA2yojLs2UYR0iIg0T6SILw KnMlnV+tmAKj5rrcAkXyBzh8SXKariiQfnMnx91cIdN2R/eNGlYwZRHDD7bMCSjEq0m2 9SQA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=S+7ti+kDO4I5pn4nBWxMKnFNBHOIWQByq+ZJiqZI+h0=; b=daC+/RdspirgodrAqTMPBs9PnLEqD+YSDt9vrjLxw7zR9K296FpvMcKX8/C+e1Zt7Q mCWcJOR6NaauXL9BWt6+h8hsreeScIukIK7nLidappjy4D47SNfy8EXkPWZjOGdNyZTZ jDciQ5gmtLALcXEy9PYSnVeDObtBer4GhMWMsFRLeyIU7GkXZCQSPKhI7lflI3WF1TSc 7swxdgvIpfs734fGj/Z2e88+x8BcwhwYNzBwHyydR4nRrU+TuKCWU1U2Y2hUWo9dvczf byqah25V4IwGs+S3nQaM1UnpHuwcCDoTL5NhcT6ZHS6nyIdZYyE09LDoNhfRSbiAcH7Q iSww==
X-Gm-Message-State: ALQs6tBu5Qh4KBnbudYboVFoH5tX7U/O54IuDT33423YK77QGlDDk6q6 5o40eOO8z11ro/5EmQU/Kkm6RTdwUG8+UTLomW1hng==
X-Google-Smtp-Source: AIpwx4+wvQe/dDBjm4zK2ApTj9k2NLNc6wN4hp26dY/uXgDaXNmcf9V28ORpwpvlKruGVEDGh/guyfGIbkxME2XSDJ4=
X-Received: by 10.31.179.66 with SMTP id c63mr4506370vkf.95.1523478560703; Wed, 11 Apr 2018 13:29:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.189.19 with HTTP; Wed, 11 Apr 2018 13:29:19 -0700 (PDT)
In-Reply-To: <7E12AF68-A247-469D-887E-065FEBD47D66@lurchi.franken.de>
References: <08aec6ec-62ce-a1e4-7781-06d50f5f66f5@gmail.com> <CAK35n0YekgWUSd8opG3YRaYKf4PVYZp9TAtN1beeQ-JO=kzv8A@mail.gmail.com> <7E12AF68-A247-469D-887E-065FEBD47D66@lurchi.franken.de>
From: Taylor Brandstetter <deadbeef@google.com>
Date: Wed, 11 Apr 2018 13:29:19 -0700
Message-ID: <CAK35n0Z491szZ+6R8Z+qMQxd2p6m4TT9_XZrjgYwsQPho2H+Kw@mail.gmail.com>
To: Michael Tuexen <michael.tuexen@lurchi.franken.de>
Cc: Taylor Brandstetter <deadbeef=40google.com@dmarc.ietf.org>, RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="001a1143aa466fa06f0569987ee0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/wjibkLrr3p2u59ypyamYznHqS7c>
Subject: Re: [rtcweb] Amount of streams supported for data channels
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 11 Apr 2018 20:29:25 -0000

I listened to the recording, and this was the main point being discussed,
but the conclusion seemed to be "efficient implementations shouldn't use
much (or any) memory for unused streams; we shouldn't make sacrifices in
the protocol just to reduce implementation complexity."

Discussion starts at 1:42:19:
https://www.ietf.org/audio/ietf88/ietf88-regencyd-20131104-1450-pm2.mp3

On Wed, Apr 11, 2018 at 12:26 PM, Michael Tuexen <
michael.tuexen@lurchi.franken.de> wrote:

> > On 11. Apr 2018, at 20:50, Taylor Brandstetter <deadbeef=
> 40google.com@dmarc.ietf.org> wrote:
> >
> > The conclusion when this was discussed at IETF 88 was "Set it to maximum
> and be done with it." Which sounds like MUST to me....
> I think the reason for the SHOULD was that it would allow implementations
> with limited resources and
> knowing that they don't need that number of parallel data channels can use
> a lower number.
>
> Best regards
> Michael
> >
> > On Wed, Apr 11, 2018 at 5:08 AM, Lennart Grahl <lennart.grahl@gmail.com>
> wrote:
> > Hi,
> >
> > there's an ongoing W3C spec discussion regarding the minimum amount of
> > streams that need to be supported by a WebRTC data channel
> > implementation, see: https://github.com/w3c/webrtc-pc/issues/1829
> >
> > draft-ietf-rtcweb-data-channel-13, section-6.2 states:
> >
> >    The number of streams negotiated during SCTP association setup SHOULD
> >    be 65535, which is the maximum number of streams that can be
> >    negotiated during the association setup.
> >
> > Is there any reason why it needs to be a SHOULD? Could we make this a
> MUST?
> >
> > Cheers
> > Lennart
> >
> > _______________________________________________
> > rtcweb mailing list
> > rtcweb@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtcweb
> >
> > _______________________________________________
> > rtcweb mailing list
> > rtcweb@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtcweb
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>