IETF Logo Mail Archive

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

Michael Tuexen <Michael.Tuexen@lurchi.franken.de> Mon, 27 October 2014 14:10 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 7249C1ACD59 for <rtcweb@ietfa.amsl.com>; Mon, 27 Oct 2014 07:10:59 -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 tTiN6IjTtC65 for <rtcweb@ietfa.amsl.com>; Mon, 27 Oct 2014 07:10:55 -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 4CC3D1ACD67 for <rtcweb@ietf.org>; Mon, 27 Oct 2014 07:10:34 -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 6AE611C105103; Mon, 27 Oct 2014 15:10:31 +0100 (CET)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D4CCEEF@ESESSMB209.ericsson.se>
Date: Mon, 27 Oct 2014 15:10:30 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <EA00639E-2008-4BD2-88F2-27AAEE9DA213@lurchi.franken.de>
References: <7594FB04B1934943A5C02806D1A2204B1D4CCEEF@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/ET-9dFbH5Tyc5tIk7WUUj3lx7AY
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 14:11:01 -0000

On 27 Oct 2014, at 14:12, 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.
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

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