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

Christer Holmberg <> Mon, 27 October 2014 14:19 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 430431A8757 for <>; Mon, 27 Oct 2014 07:19:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id zhMz0vTGkpO5 for <>; Mon, 27 Oct 2014 07:19:23 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 597AA1A874A for <>; Mon, 27 Oct 2014 07:19:14 -0700 (PDT)
X-AuditID: c1b4fb30-f79e66d000000ff1-8a-544e5460cad2
Received: from (Unknown_Domain []) by (Symantec Mail Security) with SMTP id 6C.77.04081.0645E445; Mon, 27 Oct 2014 15:19:12 +0100 (CET)
Received: from ([]) by ([]) with mapi id 14.03.0174.001; Mon, 27 Oct 2014 15:19:12 +0100
From: Christer Holmberg <>
To: Michael Tuexen <>
Thread-Topic: [rtcweb] Meaning of SHOULD support/use interleaving
Thread-Index: Ac/x55WTmtr0wn1FRpKkoOi9WMJX3////5gA///tr8A=
Date: Mon, 27 Oct 2014 14:19:11 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLLMWRmVeSWpSXmKPExsUyM+JvjW5CiF+Iwe+byhYXm5YwWqz9187u wOSxZMlPJo8NLTuYApiiuGxSUnMyy1KL9O0SuDLabn1kLnjLVbFt72/WBsZTHF2MnBwSAiYS +//sYoawxSQu3FvP1sXIxSEkcIRR4nvje0aQhJDAEkaJyYstuhg5ONgELCS6/2mDhEUETCUO Lp/HAmIzC6hL3Fl8jh3EFhZwkDi7cxI7RI2jRNvb80wQtpXE+wd7wUayCKhKLPzWAraXV8BX 4vv/S1B7Oxgl7jxcCtbMKeAq8f3XTrAiRqDjvp9awwSxTFzi1pP5TBBHC0gs2XMe6gFRiZeP /7FC2IoS7U8bGCHqdSQW7P7EBmFrSyxb+BpqsaDEyZlPWCYwis1CMnYWkpZZSFpmIWlZwMiy ilG0OLU4KTfdyEgvtSgzubg4P08vL7VkEyMwfg5u+W2wg/Hlc8dDjAIcjEo8vB9qfEOEWBPL iitzDzFKc7AoifMuPDcvWEggPbEkNTs1tSC1KL6oNCe1+BAjEwenVAOjwUM+/cLbL4SeyPg6 W0goVdf8T9fN+HasP25urPLBCt6lB6+eN9X/YbHM9eTs/r/ON1fOfL7qzNIiaca5MUd/z/o2 JcV/1e4Y05uLI39PYvp0osLeUd5HMTn94pI3piqbMhc5FuwSMsvjaTOS9d1oErekrDb6/GaG i4/S3unpxs3euKHkuH6xEktxRqKhFnNRcSIATGvdWoACAAA=
Cc: "" <>
Subject: Re: [rtcweb] Meaning of SHOULD support/use interleaving
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 27 Oct 2014 14:19:26 -0000


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

Is there a reason why it is important to use it for data channels? If so, does it apply to data channels in general? 



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