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

Taylor Brandstetter <deadbeef@google.com> Wed, 11 April 2018 18:50 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 CBE54129502 for <rtcweb@ietfa.amsl.com>; Wed, 11 Apr 2018 11:50:05 -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 XQBFeu3wFSYD for <rtcweb@ietfa.amsl.com>; Wed, 11 Apr 2018 11:50:03 -0700 (PDT)
Received: from mail-ua0-x22a.google.com (mail-ua0-x22a.google.com [IPv6:2607:f8b0:400c:c08::22a]) (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 B83BD1250B8 for <rtcweb@ietf.org>; Wed, 11 Apr 2018 11:50:03 -0700 (PDT)
Received: by mail-ua0-x22a.google.com with SMTP id q38so1838621uad.5 for <rtcweb@ietf.org>; Wed, 11 Apr 2018 11:50:03 -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=PE3So798T5IVV+OKBEgnqpuUy23ud+Et8Br5L+wQ/Ec=; b=SNyAVSpfRF7ynvaM1DcMhO7U5XFiZwMH4TqEXWSZ1DWjne1hxx0t+Z6afYASQoK7e3 7zYqsNP0X+ETv5ObbZOyzOzHnN0QCekDybQa4A2kQZ9D0t9DeKr86kqaOlT3ZwoCKIZ3 VWPC2Q0R32IVT44Wo7f+ffQ4hdb3wLoFcKDnD42EyHlmU2+cwy3dz3kwDrtRkxUuDlvH SVPjiUlcDgeSroBYkRP716rS9nWAc69PwIQ+k753Ht8UtfezR8uSQJoDObbbl8XcYYbl YCC51Gd51kfr4Vc4DaSIDn0Yvvy3+Z2drzbazdtPbAH62pK8RvCVGcCICZaOx9Fa6Pls 6/iA==
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=PE3So798T5IVV+OKBEgnqpuUy23ud+Et8Br5L+wQ/Ec=; b=tEBZWtHu81v0lTV2mD5HOvau62dyJVHfldyg3UG+VZ2gctFj3rqedXtGIEQ+eB0y5q A+24ye7rfTaJXH5JaCy1uv62xzcU5LLl7kHHerlaX4x9u78AjDNrqLV9uiythDzzkG9O gn6DJiig5dXXN2twQj4SIFv8TsjOSn+ILduwJAprRoNSmdxCjMsCSIk5cAALh5hkkzMA yTMQP07VBFOJ9ibJqQtCK0+dMt1ZPwPXdunp6Ihg9hz8MCu5UIKJzMgl7bOtRiPpLbH+ mVGCqtGK5nrPMlFXrnXPMbj5b7u3TvkWmSKJep69VZFu4NatvSD8TpxctfyvZ4EZvDsc NXkA==
X-Gm-Message-State: ALQs6tCGb/t6qK6o0LRD3/oib8xtH1WOZBjHg5QE55q+Yd87SQNXJ4DN UKhiTESVAa34Es97WhlUPH/djijn58MQOYYF/Y2NbQ==
X-Google-Smtp-Source: AIpwx4+IDiuMTkP1WiJEu40ynTWDWiYfgEyuR3CizbJstYvTkhrBIiqJuwtM7QhQiDkvdn7IMkCK0YWEPulcChNLmH8=
X-Received: by 10.176.9.223 with SMTP id e31mr4082528uah.175.1523472602376; Wed, 11 Apr 2018 11:50:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.189.19 with HTTP; Wed, 11 Apr 2018 11:50:01 -0700 (PDT)
In-Reply-To: <08aec6ec-62ce-a1e4-7781-06d50f5f66f5@gmail.com>
References: <08aec6ec-62ce-a1e4-7781-06d50f5f66f5@gmail.com>
From: Taylor Brandstetter <deadbeef@google.com>
Date: Wed, 11 Apr 2018 11:50:01 -0700
Message-ID: <CAK35n0YekgWUSd8opG3YRaYKf4PVYZp9TAtN1beeQ-JO=kzv8A@mail.gmail.com>
To: Lennart Grahl <lennart.grahl@gmail.com>
Cc: RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="f403043ede144adbd90569971be9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/WWBIYPlsSMIAO7HjHkSGQWkKVVU>
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 18:50:06 -0000

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

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
>