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.
_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art
