Last Call Review of draft-ietf-clue-signaling-13
review-ietf-clue-signaling-13-opsdir-lc-vyncke-2018-10-10-00

Request Review of draft-ietf-clue-signaling
Requested rev. no specific revision (document currently at 14)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2018-10-17
Requested 2018-10-03
Other Reviews Genart Last Call review of -13 by Robert Sparks (diff)
Secdir Last Call review of -13 by Chris Lonvick (diff)
Genart Telechat review of -14 by Robert Sparks
Review State Completed
Reviewer Éric Vyncke
Review review-ietf-clue-signaling-13-opsdir-lc-vyncke-2018-10-10
Posted at https://mailarchive.ietf.org/arch/msg/ops-dir/4hFVagHKDl8YWUronoEGMwI8_Q8
Reviewed rev. 13 (document currently at 14)
Review result Has Nits
Draft last updated 2018-10-10
Review completed: 2018-10-10

Review
review-ietf-clue-signaling-13-opsdir-lc-vyncke-2018-10-10

Reviewer: Eric Vyncke
Review result: has minor nits

I have reviewed this document as part of the Operational directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written with the intent of improving the operational aspects of
the IETF drafts. Comments that are not addressed in last call may be included
in AD reviews during the IESG review.  Document editors and WG chairs should
treat these comments just like any other last call comments.

From a deployment point of view, I liked this introduction statement "Backwards-compatibility is an important consideration of the protocol: it is vital that a CLUE-capable device contacting a device that does not support CLUE is able to fall back to a fully functional non-CLUE call." And special care of co-existence during deployement appear in the document. But, I wonder how *middle boxes* would react if they are not aware of this protocol extension.

Please bear with my very light understanding of CLUE in general. As a side note, it would have been nice to expand the CLUE acronym when used the first time. In general, the document is not easy to read: too many details given immediately without a first high-level description. So, the sections 8 and 9 (examples) are really useful even if more details could have been given: for example, while the initial SDP is shown, the response SDP is not.

Nits: section 6 has a reference which does not have a URI.

Else, this document is ready to go.

-éric