Re: [clue] WGLC comments on clue-datachannel-07 - Mark's comments

"Duckworth, Mark" <Mark.Duckworth@polycom.com> Tue, 10 February 2015 18:13 UTC

Return-Path: <Mark.Duckworth@polycom.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26BF91A1AFE for <clue@ietfa.amsl.com>; Tue, 10 Feb 2015 10:13:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, 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 d_5zP1Xa5Le9 for <clue@ietfa.amsl.com>; Tue, 10 Feb 2015 10:13:06 -0800 (PST)
Received: from mail1.bemta8.messagelabs.com (mail1.bemta8.messagelabs.com [216.82.243.195]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4AE6A1A1B15 for <clue@ietf.org>; Tue, 10 Feb 2015 10:13:04 -0800 (PST)
Received: from [216.82.241.100] by server-3.bemta-8.messagelabs.com id 43/7B-03004-F2A4AD45; Tue, 10 Feb 2015 18:13:03 +0000
X-Env-Sender: Mark.Duckworth@polycom.com
X-Msg-Ref: server-13.tower-220.messagelabs.com!1423591981!15026247!1
X-Originating-IP: [140.242.64.158]
X-StarScan-Received:
X-StarScan-Version: 6.12.5; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 14646 invoked from network); 10 Feb 2015 18:13:02 -0000
Received: from crpehubprd01.polycom.com (HELO Crpehubprd01.polycom.com) (140.242.64.158) by server-13.tower-220.messagelabs.com with AES128-SHA encrypted SMTP; 10 Feb 2015 18:13:02 -0000
Received: from CRPMBOXPRD08.polycom.com ([169.254.1.92]) by Crpehubprd01.polycom.com ([::1]) with mapi; Tue, 10 Feb 2015 10:13:16 -0800
From: "Duckworth, Mark" <Mark.Duckworth@polycom.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "clue@ietf.org" <clue@ietf.org>
Date: Tue, 10 Feb 2015 10:12:58 -0800
Thread-Topic: WGLC comments on clue-datachannel-07 - Mark's comments
Thread-Index: AdBEo5B5/RiwabFpR+i6+V35hy9nBgAYjZpQAA52uQAAA6HcbwADpUgQ
Message-ID: <5C4AC54BFF7A0842A6A11F554D6FB52F96B2A4C080@CRPMBOXPRD08.polycom.com>
References: <7594FB04B1934943A5C02806D1A2204B1D6BC829@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1D6C076C@ESESSMB209.ericsson.se>, <5C4AC54BFF7A0842A6A11F554D6FB52F96B2A4C023@CRPMBOXPRD08.polycom.com> <7594FB04B1934943A5C02806D1A2204B1D6C4914@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D6C4914@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_5C4AC54BFF7A0842A6A11F554D6FB52F96B2A4C080CRPMBOXPRD08p_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/clue/jXQqo_GXAg65W5LAQM2i-RZ5xKc>
Subject: Re: [clue] WGLC comments on clue-datachannel-07 - Mark's comments
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: CLUE - ControLling mUltiple streams for TElepresence <clue.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/clue>, <mailto:clue-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/clue/>
List-Post: <mailto:clue@ietf.org>
List-Help: <mailto:clue-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/clue>, <mailto:clue-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Feb 2015 18:13:09 -0000

Hi Christer,
You are correct, thanks for pointing that out. I found the priority attribute is defined in draft-ietf-tsvwg-sctp-prpolicies.  It is for partial reliability usage, so the CLUE data channel document can ignore it.
Mark

From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
Sent: Tuesday, February 10, 2015 11:25 AM
To: Duckworth, Mark; clue@ietf.org
Subject: RE: WGLC comments on clue-datachannel-07 - Mark's comments

Hi Mark,

I believe the priority is defined in the partial reliability draft. And, afair, the usage is implementation specific.

Regards,

Christer

Sent from my Windows Phone
________________________________
From: Duckworth, Mark<mailto:Mark.Duckworth@polycom.com>
Sent: ‎10/‎02/‎2015 16:46
To: Christer Holmberg<mailto:christer.holmberg@ericsson.com>; clue@ietf.org<mailto:clue@ietf.org>
Subject: RE: WGLC comments on clue-datachannel-07 - Mark's comments
I couldn’t find any documentation about how this priority attribute is used.  If it really is for partial reliability only, then I agree with you that the CLUE document doesn’t need to say anything more.  But I can’t find this stated anywhere in draft-ietf-rtcweb-data-channel or any other draft.  Would it be safer to just say it doesn’t apply in the CLUE data channel document?

Mark

From: Christer Holmberg [mailto:christer.holmberg@ericsson.com]
Sent: Tuesday, February 10, 2015 2:52 AM
To: Duckworth, Mark; clue@ietf.org
Subject: RE: WGLC comments on clue-datachannel-07 - Mark's comments

Hi,

Regarding the priority attribute, my understanding is that it is only applicable to partial reliability (there is no priority flag/parameter in core SCTP, as far as I know).

Assuming my understanding is correct, I don’t think we need to say anything, because we already say that partial reliability is not used.

Regards,

Christer


From: clue [mailto:clue-bounces@ietf.org] On Behalf Of Christer Holmberg
Sent: 9. helmikuuta 2015 22:05
To: Duckworth, Mark; clue@ietf.org
Subject: Re: [clue] WGLC comments on clue-datachannel-07 - Mark's comments

Hi Mark,

Thanks for your comments!

I agree with your suggestion to make it clear that the text is talking about the CLUE data channel.

Regards,

Christer

From: Duckworth, Mark [mailto:Mark.Duckworth@polycom.com]
Sent: 09 February 2015 22:02
To: Christer Holmberg; clue@ietf.org<mailto:clue@ietf.org>
Subject: WGLC comments on clue-datachannel-07

The document looks good, I have only a couple minor suggestions.

draft-ietf-rtcweb-data-channel section 6.4 says each data channel has a priority attribute.  Does this attribute apply to reliable messages, or only unreliable?  I can’t find it documented.  If it does not apply to the CLUE data channel, it would be good to say so.

3.3.2 – “A CLUE entity MUST NOT use the partial reliability and limited retransmission extensions defined in [RFC3758].”  Should this be more specific, in just limiting it for the CLUE data channel, and not limit it for any other WebRTC Data Channels that might be used for other purposes?  Maybe “A CLUE entity MUST NOT use the partial reliability and limited retransmission extensions defined in [RFC3758], for the CLUE data channel.”  Or perhaps more simply “A CLUE data channel MUST NOT use the partial reliability and limited retransmission extensions defined in [RFC3758].”

3.3.3 – “A CLUE entity MUST use the ordered delivery SCTP service, as described in section 6.6 of [RFC4960].” Same comment as above, should this be limited to just the CLUE data channel?

Regards,
Mark