IETF Logo Mail Archive

[rtcweb] Amount of streams supported for data channels

Lennart Grahl <lennart.grahl@gmail.com> Wed, 11 April 2018 12:08 UTC

Return-Path: <lennart.grahl@gmail.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 EC0BA124207 for <rtcweb@ietfa.amsl.com>; Wed, 11 Apr 2018 05:08:13 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 mUP5wdYwYEki for <rtcweb@ietfa.amsl.com>; Wed, 11 Apr 2018 05:08:11 -0700 (PDT)
Received: from mail-wr0-x22e.google.com (mail-wr0-x22e.google.com [IPv6:2a00:1450:400c:c0c::22e]) (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 D7E07120724 for <rtcweb@ietf.org>; Wed, 11 Apr 2018 05:08:10 -0700 (PDT)
Received: by mail-wr0-x22e.google.com with SMTP id d19so1539254wre.1 for <rtcweb@ietf.org>; Wed, 11 Apr 2018 05:08:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:openpgp:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=ctzutNTbXl1G7R2MKiV+nO1cz7i/4y1WdYzXN5W8M9k=; b=KhT3NW29uK4c6IAjkk61DAvzogdxeueiTqxBILFWRFEimx0c+hUpXDpA65SUAh4EPS 0zktiBtUTjAYma1bIIx2WRRIiSsNhKyXtLgk3v84Esme4MruxAA9kn9zwdtatDR1Rzz7 fQ0jAm0EpOA9Ep5H2FVgDvAoqyT6wa06ZFsBtKkeMkG89ewz4l84faGF1luHgbapUDPL 89VRrtdCmPuFGVTsDGUTH7IjKBMAafs1bHDLrM/ZupFKPaltf3DNoH49ppUyGbvYDG4Z 1z/LUSU8Sz3YYG16raWlFtPogorJ7Yrj7F2KSSptn8oYq/iZfNrayKJNWr6mTuNkgOUV /jZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:openpgp:message-id:date :user-agent:mime-version:content-language:content-transfer-encoding; bh=ctzutNTbXl1G7R2MKiV+nO1cz7i/4y1WdYzXN5W8M9k=; b=WxPcqt4piT6OpFi4SwR6EZH8Qag8RTIapRA2TdpzHUK3Qe9sOtm7Nmz2Sy3YP8zGy2 AK4K/eEfXyViq73QNga4dIvFKurrOtBKsnU+n83ko1vn+Br/qM7tcMUev/oJuE2pMX3P ce7WzfuWvPNggjI1kjPBK/kql0wu9s/Nm2gIdW+3/cfYvc63Vd8oe8He+m7uFlZKC3OM DqCSmkwaC8bFR++2YlG6w+jq9A4oX/9/UgqQLDnrDRPvrkgsNrdwemK65yh6Oj4Peooz BkymWi18afbp1Y7wB9SRFaEez5oX3rxvVTC1pQx48+txeDE+afMoz/JUIT3kREnSypTj Za/w==
X-Gm-Message-State: ALQs6tAwhPgTgePyD4vDyX4PjwYGCLH9SrK+JlwXEpR9nEHJ5rejq3Gs bWzaUl8e4GDtDtEHX2yU7B5GTw==
X-Google-Smtp-Source: AIpwx48F7pUHbG27eBq2ylQuoZGBqVYibze5u6/oV7EYRJTHqNg4lJ3Y7LcAJfd22JI++OBFP0JG3w==
X-Received: by 10.223.201.12 with SMTP id m12mr3456662wrh.158.1523448488020; Wed, 11 Apr 2018 05:08:08 -0700 (PDT)
Received: from ?IPv6:2003:cd:6f24:eb00:3d14:e3e8:2cef:11e2? (p200300CD6F24EB003D14E3E82CEF11E2.dip0.t-ipconnect.de. [2003:cd:6f24:eb00:3d14:e3e8:2cef:11e2]) by smtp.gmail.com with ESMTPSA id z12sm1232091wrb.29.2018.04.11.05.08.07 for <rtcweb@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Apr 2018 05:08:07 -0700 (PDT)
To: RTCWeb IETF <rtcweb@ietf.org>
From: Lennart Grahl <lennart.grahl@gmail.com>
Openpgp: preference=signencrypt
Message-ID: <08aec6ec-62ce-a1e4-7781-06d50f5f66f5@gmail.com>
Date: Wed, 11 Apr 2018 14:08:05 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/OEsQPQVl6-aXypuP8MtYfwDDTEE>
Subject: [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 12:08:14 -0000

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

v2.23.0 | Report a Bug | By Email