Skip to main content

Last Call Review of draft-ietf-clue-datachannel-13

Request Review of draft-ietf-clue-datachannel
Requested revision No specific revision (document currently at 18)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2016-08-01
Requested 2016-07-08
Authors Christer Holmberg
I-D last updated 2016-07-28
Completed reviews Genart Last Call review of -13 by Brian E. Carpenter (diff)
Secdir Last Call review of -13 by Barry Leiba (diff)
Opsdir Last Call review of -13 by Bert Wijnen (diff)
Tsvart Telechat review of -15 by Joerg Ott (diff)
Assignment Reviewer Brian E. Carpenter
State Completed
Review review-ietf-clue-datachannel-13-genart-lc-carpenter-2016-07-28
Reviewed revision 13 (document currently at 18)
Result Ready
Completed 2016-07-28
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

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?


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