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

Michael Tuexen <Michael.Tuexen@lurchi.franken.de> Mon, 27 October 2014 19:50 UTC

Return-Path: <Michael.Tuexen@lurchi.franken.de>
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 7CC131AD0BE for <rtcweb@ietfa.amsl.com>; Mon, 27 Oct 2014 12:50:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level:
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_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 MJr4C-pZSz9l for <rtcweb@ietfa.amsl.com>; Mon, 27 Oct 2014 12:50:02 -0700 (PDT)
Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2A9F1AD0D7 for <rtcweb@ietf.org>; Mon, 27 Oct 2014 12:50:01 -0700 (PDT)
Received: from [192.168.1.200] (p508F0FB4.dip0.t-ipconnect.de [80.143.15.180]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id C8D8F1C104D97; Mon, 27 Oct 2014 20:49:59 +0100 (CET)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D4CD241@ESESSMB209.ericsson.se>
Date: Mon, 27 Oct 2014 20:49:57 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D408814A-897A-4853-A84B-D4276A2A0049@lurchi.franken.de>
References: <7594FB04B1934943A5C02806D1A2204B1D4CCEEF@ESESSMB209.ericsson.se> <EA00639E-2008-4BD2-88F2-27AAEE9DA213@lurchi.franken.de> <7594FB04B1934943A5C02806D1A2204B1D4CD241@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/PXRVuUxisDIfh-PCVbqm6XpNoZ4
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: Mon, 27 Oct 2014 19:50:03 -0000

On 27 Oct 2014, at 15:19, Christer Holmberg <christer.holmberg@ericsson.com> wrote:

> 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.
>> 
>> My understanding is that SCTP implementations supporting the extension will use it.
>> This is negotiated during the setup of the SCTP association.
> 
> If it's done on SCTP level, why do we need to talk about it in the data channel draft? 
We need to specify somewhere that the extension is used and how to map the priorities
of data channels to some protocol mechanism. This is done in this document.
> 
> Is there a reason why it is important to use it for data channels? If so, does it apply to data channels in general? 
As it is written right now: yes.

Best regards
Michael
> 
> Regards,
> 
> Christer
> 
> 
> 
> Whether messages are interleaved or not depends on the stream scheduler. This is a sender side only decision. The receiver has to deal with it.
> It is not a MUST, since there are implementations now in use which don't support the extension.
> 
> Best regards
> Michael
>> 
>> 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
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
> 
>