IETF Logo Mail Archive

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

Michael Tuexen <Michael.Tuexen@lurchi.franken.de> Tue, 28 October 2014 15:06 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 D1B5C1A8A5F for <rtcweb@ietfa.amsl.com>; Tue, 28 Oct 2014 08:06:42 -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 g0-YSVhDNGoR for <rtcweb@ietfa.amsl.com>; Tue, 28 Oct 2014 08:06:40 -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 E22A91A8A5A for <rtcweb@ietf.org>; Tue, 28 Oct 2014 08:06:39 -0700 (PDT)
Received: from [10.225.7.42] (unknown [194.95.73.101]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id DB3821C10461D; Tue, 28 Oct 2014 16:06:36 +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: <7594FB04B1934943A5C02806D1A2204B1D4D0CE8@ESESSMB209.ericsson.se>
Date: Tue, 28 Oct 2014 16:06:36 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <CD364160-0A33-4E74-B114-04BDA33E40D3@lurchi.franken.de>
References: <7594FB04B1934943A5C02806D1A2204B1D4CCEEF@ESESSMB209.ericsson.se> <EA00639E-2008-4BD2-88F2-27AAEE9DA213@lurchi.franken.de> <7594FB04B1934943A5C02806D1A2204B1D4CD241@ESESSMB209.ericsson.se> <544E8D92.8010401@alvestrand.no> <7594FB04B1934943A5C02806D1A2204B1D4CE9DA@ESESSMB209.ericsson.se>, <5B74C903-7C9A-4D74-B5CC-D0643A377935@lurchi.franken.de> <7594FB04B1934943A5C02806D1A2204B1D4CEBAB@ESESSMB209.ericsson.se> <9A1C16CE-1423-448B-943F-33B3068156F3@lurchi.franken.de> <7594FB04B1934943A5C02806D1A2204B1D4D0CE8@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/r15U18uDgjPhv6d6ADPEB5ObVaw
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: Tue, 28 Oct 2014 15:06:43 -0000

On 28 Oct 2014, at 14:51, Christer Holmberg <christer.holmberg@ericsson.com> wrote:

> Hi,
> 
>>> I am not suggesting different flavors - I am suggesting to make the usage of interleaving optional. Other SCTP features are also optional (including reliability, ordering etc).
>> 
>> Where are these things optional? According to
>> https://tools.ietf.org/html/draft-ietf-rtcweb-data-channel-12#section-6.1
>> an implementation MUST implement PR-SCTP and the support of the FORWARD-TSN chunk will be negotiated similar to the NDATA chunk. I don't see a difference, especially not if we move to MUST support NDATA.
> 
> For example, section 6.1 says:
> 
> 	"The partial reliability extension defined in [RFC3758] MUST be supported."
> 
> However, in CLUE we say that a CLUE entity MUST NOT *use* the extension, as all CLUE messages are required to be sent reliably.
That is OK. However, support for PR-SCTP MUST be there and it will be negotiated. You just never
send a message with partial reliability. At least this is my understanding...

Best regards
Michael
> 
> Regards,
> 
> Christer
>

v2.23.0 | Report a Bug | By Email