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

Paul Kyzivat <pkyzivat@alum.mit.edu> Thu, 28 July 2016 15:03 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 21B8412D648 for <gen-art@ietfa.amsl.com>; Thu, 28 Jul 2016 08:03:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level:
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no 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 FqXdn124qxIB for <gen-art@ietfa.amsl.com>; Thu, 28 Jul 2016 08:03:05 -0700 (PDT)
Received: from resqmta-ch2-04v.sys.comcast.net (resqmta-ch2-04v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:36]) (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 31E7512D669 for <gen-art@ietf.org>; Thu, 28 Jul 2016 08:03:04 -0700 (PDT)
Received: from resomta-ch2-20v.sys.comcast.net ([69.252.207.116]) by resqmta-ch2-04v.sys.comcast.net with SMTP id SmpabWuEL8PeaSmpzbu6RH; Thu, 28 Jul 2016 15:03:03 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([73.218.51.154]) by comcast with SMTP id SmpybHa2Qn5jaSmpybbxXJ; Thu, 28 Jul 2016 15:03:03 +0000
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, draft-ietf-clue-datachannel.all@ietf.org, General Area Review Team <gen-art@ietf.org>
References: <4e8a5e7c-2537-dc1b-d755-b0fed4e842d7@gmail.com>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <19b36f76-6196-feab-c190-b12892e3ee85@alum.mit.edu>
Date: Thu, 28 Jul 2016 11:03:02 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <4e8a5e7c-2537-dc1b-d755-b0fed4e842d7@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfFTRI2Au0piHO5a92/C1QGbjxHwr0AHRhu+B5oa8CIXRErHWVlRaN1NwvIPCOJbKgccZJIB4XNKWvPM0EN9k9CQbApDIjpPnrdMcFCL/ios7O513H5gR BZkOXiRXWI753fsR6KrZvvre8UOq82vkxZcEV6pl5+TwLK7BnOu2FpRQ4N/iwhbu9Ce9+WoR8fZDq7VHV95BkShTkGxGgggaXj/C3u1I3FXnx7xTCnfjP9sJ ByGxRPpQX4wlt5kbBBu8jCFB1UxrlrIcSWFfwrA80ayBWJ9AVx6iKzxaTPZ54Bc+
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Nu7RdUAyh78KusuzMwuej7UHO1E>
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: Thu, 28 Jul 2016 15:03:07 -0000

On 7/27/16 7:39 PM, Brian E Carpenter wrote:
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>
> For more information, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Document: draft-ietf-clue-datachannel-13.txt
> Reviewer: Brian Carpenter
> Review Date: 2016-07-28
> IETF LC End Date: 2016-08-01
> IESG Telechat date:
>
> Summary: Ready
> --------
>
> 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?

CLUE's needs are modest in regards to transporting the clue messaging. 
(E.g., TCP would be sufficient.) We chose data channels because that 
provides the possibility of straightforward interoperation with Webrtc. 
It also makes possible the use of the m-line bundle mechanism.

	Thanks,
	Paul

> Nits:
> -----
>
> I expected a reference to draft-ietf-clue-protocol where CLUE is first mentioned
> in the Introduction.
>