Re: [clue] Mirja Kühlewind's Discuss on draft-ietf-clue-protocol-17: (with DISCUSS and COMMENT)

"Roni Even (A)" <roni.even@huawei.com> Fri, 02 November 2018 12:52 UTC

Return-Path: <roni.even@huawei.com>
X-Original-To: clue@ietfa.amsl.com
Delivered-To: clue@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B231B124408; Fri, 2 Nov 2018 05:52:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 8IzEg3-oAzHz; Fri, 2 Nov 2018 05:52:54 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68E30123FFD; Fri, 2 Nov 2018 05:52:54 -0700 (PDT)
Received: from lhreml708-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 3D19DF813317; Fri, 2 Nov 2018 12:52:50 +0000 (GMT)
Received: from DGGEMM402-HUB.china.huawei.com (10.3.20.210) by lhreml708-cah.china.huawei.com (10.201.108.49) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 2 Nov 2018 12:52:51 +0000
Received: from DGGEMM526-MBX.china.huawei.com ([169.254.8.186]) by DGGEMM402-HUB.china.huawei.com ([10.3.20.210]) with mapi id 14.03.0415.000; Fri, 2 Nov 2018 20:52:46 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: Mirja Kühlewind <ietf@kuehlewind.net>, The IESG <iesg@ietf.org>
CC: "clue-chairs@ietf.org" <clue-chairs@ietf.org>, "clue@ietf.org" <clue@ietf.org>, "draft-ietf-clue-protocol@ietf.org" <draft-ietf-clue-protocol@ietf.org>
Thread-Topic: [clue] Mirja Kühlewind's Discuss on draft-ietf-clue-protocol-17: (with DISCUSS and COMMENT)
Thread-Index: AQHUcVBilQ2Ni2nLI0qDoEse3sOvUKU8cqUw
Date: Fri, 02 Nov 2018 12:52:45 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD13044718@dggemm526-mbx.china.huawei.com>
References: <154101430593.5389.2663125960619308709.idtracker@ietfa.amsl.com>
In-Reply-To: <154101430593.5389.2663125960619308709.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.126.174.212]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/clue/btVTnWp_CmsFbdchiKjWRNxrOaE>
Subject: Re: [clue] Mirja Kühlewind's Discuss on draft-ietf-clue-protocol-17: (with DISCUSS and COMMENT)
X-BeenThere: clue@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 02 Nov 2018 12:52:57 -0000

Hi Mirja,
Thanks for the review.
The protocol document describes the clue protocol. The establishment of the data channel is discussed in the signaling protocol  https://tools.ietf.org/html/draft-ietf-clue-signaling-14 

The introduction says

CLUE-capable endpoints are connected by means of the CLUE data
   channel, an SCTP over DTLS channel which is opened and established as
   described in [I-D.ietf-clue-signaling] and
   [I-D.ietf-clue-datachannel].  CLUE protocol messages flowing over
   such a channel are detailed in this document, both syntactically and
   semantically.

Roni Even

-----Original Message-----
From: clue [mailto:clue-bounces@ietf.org] On Behalf Of Mirja Kühlewind
Sent: Thursday, November 01, 2018 2:32 AM
To: The IESG
Cc: clue-chairs@ietf.org; clue@ietf.org; draft-ietf-clue-protocol@ietf.org
Subject: [clue] Mirja Kühlewind's Discuss on draft-ietf-clue-protocol-17: (with DISCUSS and COMMENT)

Mirja Kühlewind has entered the following ballot position for
draft-ietf-clue-protocol-17: Discuss

When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-clue-protocol/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

This document does not discuss any interactions with the transport protocol (e.g. who establishes the connection? what happens if the connections breaks; who should re-establish?). Also, I assume that SCTP is used (instead of TCP) because the idea is to use different SCTP streams for the different directions of the communication...? However, this is a complete guess, as the document does unfortunately not say nothing about the mapping of CLUE messages to SCTP sessions. In case all message are assumed to be send over the same stream instead, why is SCTP used and not TCP? Please provide more information and guidance on the use of SCTP!


----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Two minor editorial commets:

1) In the terminology section: What does MCU actually stand for?

2) sec 4:
"CLUE protocol version numbers are
   characterized by a major version number (single digit) and a minor
   version number (single digit)..."
However, later on the text says that the numbers can also consist of multiple digits...


_______________________________________________
clue mailing list
clue@ietf.org
https://www.ietf.org/mailman/listinfo/clue