IETF Logo Mail Archive

[rtcweb] Meaning of SHOULD support/use interleaving

Christer Holmberg <christer.holmberg@ericsson.com> Mon, 27 October 2014 13:12 UTC

Return-Path: <christer.holmberg@ericsson.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 2A66D1A8028 for <rtcweb@ietfa.amsl.com>; Mon, 27 Oct 2014 06:12:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 eSsGgvO9uOep for <rtcweb@ietfa.amsl.com>; Mon, 27 Oct 2014 06:12:57 -0700 (PDT)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52C321AC409 for <rtcweb@ietf.org>; Mon, 27 Oct 2014 06:12:51 -0700 (PDT)
X-AuditID: c1b4fb2d-f79fc6d000001087-93-544e44d1d3da
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg23.ericsson.net (Symantec Mail Security) with SMTP id 3E.E7.04231.1D44E445; Mon, 27 Oct 2014 14:12:49 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.163]) by ESESSHC022.ericsson.se ([153.88.183.84]) with mapi id 14.03.0174.001; Mon, 27 Oct 2014 14:12:48 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: Meaning of SHOULD support/use interleaving
Thread-Index: Ac/x55WTmtr0wn1FRpKkoOi9WMJX3w==
Date: Mon, 27 Oct 2014 13:12:48 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D4CCEEF@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.19]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D4CCEEFESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrKLMWRmVeSWpSXmKPExsUyM+Jvje5FF78Qg4sN6hZr/7WzOzB6LFny kymAMYrLJiU1J7MstUjfLoErY+K8DpaC1zIVP67/YG5g3CHZxcjJISFgIvHvyCdWCFtM4sK9 9WxdjFwcQgJHGCVWLJjBCuEsYZRYMK2HqYuRg4NNwEKi+582SIOIgLrE5YcX2EFsYQFjiZPP /7BBxC0kVv+5yAhh60ksPLCdCcRmEVCV+LqznwXE5hXwlbgzrQuslxFo8fdTa8BqmAXEJW49 mc8EcZCAxJI955khbFGJl4//QR2qKNH+tIER5BxmgXyJM4/sIUYKSpyc+YRlAqPQLCSTZiFU zUJSBVGiI7Fg9yc2CFtbYtnC18ww9pkDj5mQxRcwsq9iFC1OLS7OTTcy1kstykwuLs7P08tL LdnECIyHg1t+6+5gXP3a8RCjAAejEg/vhxrfECHWxLLiytxDjNIcLErivIvOzQsWEkhPLEnN Tk0tSC2KLyrNSS0+xMjEwSnVwCjYddymQmKv3UHrDN/pGcL3ogVzXz78o7NMiaVyZrLgq7W/ X5ycmlp8pfxhysEOr8J5wSt5bgfalVrr/2CccDat1E5wff6nVTduVxjNVuQTYSgJj/vvJ31l 65fYRR851y+++fd/Q22WSZdJgv7HL6eXOE03Zwy2kk84fmHH1ncM/WnRs1maOJVYijMSDbWY i4oTAXEBjbRoAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/GPVMarMAhTGxDQnqgYVwtxEzuJs
Subject: [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: Mon, 27 Oct 2014 13:12:59 -0000

Hi,

Within the CLUE WG, we had a discussion regarding the following statement in section 6.1 of draft-ietf-rtcweb-data-channel-12.txt:

"The support for message interleaving as defined in
                [I-D.ietf-tsvwg-sctp-ndata] SHOULD be used."

First, it is a little unclear what "the support SHOULD be used" means.

Second, does it mean that any data channel protocol (e.g CLUE) SHOULD use interleaving, even if the characteristics of the protocol wouldn't require it?

Regards,

Christer

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