Re: [Gen-art] Gen-ART Last Call review of draft-ietf-clue-datachannel-13

Alissa Cooper <alissa@cooperw.in> Tue, 09 August 2016 18:52 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D04FB12D769; Tue, 9 Aug 2016 11:52:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level:
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=zdV82wAs; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=T8I32X3J
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 CRexD73tySKQ; Tue, 9 Aug 2016 11:52:50 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7767312D189; Tue, 9 Aug 2016 11:52:50 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id BE97B20530; Tue, 9 Aug 2016 14:52:49 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Tue, 09 Aug 2016 14:52:49 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=EIZJWIa/bVaDjnVIHhbj2Bf1chg=; b=zdV82w AsqNGJwuzryFXFI5qwyAGKPNNW73sPsXGZ6rvFdHnYyLOpVpRKSHwhO/hZCgE4FC sW2DJV6nHau+M/l1EoQfzXD87EijvJSblre0ZhDQUJp08hqQeMPkjTEiiVjD/P/+ MZ26T8zk0Upmp1BkByMt16qc+i3UZsmP3bFpU=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=EIZJWIa/bVaDjnV IHhbj2Bf1chg=; b=T8I32X3JS5HH3LV/AT//1RDpD70e2yfMt6fwS4RWwRQn5c5 cSAfHpKhpsumJFIWKgkJFtqQsjywBW7eDEtskPvPtP8SzEHhJdLLczDcZOMoAVjN sBmRct9mKsyslXvumgTeWP03Vf+d2SnbLFw5jQZ9a1SMZtrdyYbsE6+PM2VU=
X-Sasl-enc: f6PuOcWG1AsNTKgJp8WXoN42DzdhnAYMLNUofA9MdR/1 1470768769
Received: from dhcp-171-68-20-114.cisco.com (dhcp-171-68-20-114.cisco.com [171.68.20.114]) by mail.messagingengine.com (Postfix) with ESMTPA id 1A769F296E; Tue, 9 Aug 2016 14:52:49 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BBC4909@ESESSMB208.ericsson.se>
Date: Tue, 9 Aug 2016 11:52:48 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <3F3AA8F5-376D-4B17-8167-54A2F17B5A04@cooperw.in>
References: <4e8a5e7c-2537-dc1b-d755-b0fed4e842d7@gmail.com> <7594FB04B1934943A5C02806D1A2204B4770FB67@ESESSMB209.ericsson.se> <c0d43bca-e666-fa9b-12f8-30bb10125482@gmail.com> <7594FB04B1934943A5C02806D1A2204B4BBB86D8@ESESSMB208.ericsson.se> <7594FB04B1934943A5C02806D1A2204B4BBC4909@ESESSMB208.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/IGtRVtaIiut4Cqd5ZXo3aw6kOF8>
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-clue-datachannel.all@ietf.org" <draft-ietf-clue-datachannel.all@ietf.org>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-clue-datachannel-13
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2016 18:52:52 -0000

> On Aug 8, 2016, at 12:29 PM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
> 
> Hi,
> 
> I've created a new version of the draft, based on Brian's comments. It's not yet submitted, but can be found at GitHub:
> 
> https://github.com/cdh4u/draft-clue-datachannel/blob/master/draft-ietf-clue-datachannel.txt
> 
> The only change is to add a reference to the club protocol draft in the Introduction section.
> 
> Alissa, please let me know when I can submit the new version :)

You can go ahead and submit.

Thanks,
Alissa

> 
> Thanks!
> 
> Regards,
> 
> Christer
> 
> 
> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg@ericsson.com] 
> Sent: 07 August 2016 20:13
> To: Brian E Carpenter <brian.e.carpenter@gmail.com>om>; draft-ietf-clue-datachannel.all@ietf.org; General Area Review Team <gen-art@ietf.org>
> Subject: RE: Gen-ART Last Call review of draft-ietf-clue-datachannel-13
> 
> Hi Brian,
> 
> ...
> 
>>>> Minor issues:
>>>> -------------
>>>> 
>>>> Mainly for my own education:
>>>> 
>>>> 3.2.6.  SCTP Multihoming
>>>> 
>>>>  SCTP multi-homing is not supported for SCTPoDTLS associations, and
>>>>  can therefore not be used for a CLUE data channel.
>>>> 
>>>> What is the advantage of SCTP if you don't get the benefit of multihoming?
>>> 
>>> There are other SCTP features that are used. The most essential is 
>>> the SCTP multi stream feature, which allows multiple data channels 
>>> using a single SCTP associations: each data channel is implemented using two unidirectional SCTP streams.
>>> 
>>> SCTP also provide different options when it comes to data transport reliability and ordering, and data channels can use different combinations.
>> 
>> OK, thanks. I have the impression that this explanation is given 
>> nowhere in the CLUE documents (and not in draft-ietf-rtcweb-transports either). I think it would be helpful if it was recorded *somewhere*.
>> It doesn't really belong in clue-datachannel.
> 
> I agree - it's not the task of CLUE to justify the decisions made by RTCWEB.
> 
> For the details of the data channel mechanism, please take a look at draft-ietf-rtcweb-data-channel.
> 
> https://tools.ietf.org/html/draft-ietf-rtcweb-data-channel
> 
> Regards,
> 
> Christer
> 
> 
> 
>> 
>> 
>>> Nits:
>>> -----
>>> 
>>> I expected a reference to draft-ietf-clue-protocol where CLUE is first mentioned in the Introduction.
>> 
>> I'll fix that.
> 
> Thanks
>    Brian